Skip to main content
If you can’t find your question here, the glossary defines terms used across the docs, and Support covers response times and what’s in scope.

About the product

Is Vibely open source?

The Vibely engine and templates are open source on GitHub. The hosted product at vibely.sh is the same engine plus auth, billing, infrastructure, and operational support.

Do I own the code Vibely writes?

Yes. Every line is yours. Sync to GitHub at any time and run the project without Vibely in the loop. No proprietary runtime, no special build step, nothing that ties you to Vibely once you’ve exported.

Can I self-host Vibely?

Yes. The engine is open source and self-hostable. You’ll need a sandbox provider, an LLM provider, and a Postgres instance. The hosted product is the easier path for most teams.

What can Vibely build?

Three product surfaces, five design surfaces:
  • Web App Mode — full-stack web (Vite + React + Tailwind + TanStack + Supabase by default)
  • Mobile App Mode — iOS + Android via Expo + React Native
  • Design Mode — web screens, app screens, slides, animations, and animated decks. Click Make it real on any design to turn it into a working project.
See Web, Mobile, Design.

Models and AI

Which AI models does Vibely use?

Kimi K2.6, Google Gemini, and Anthropic Claude. By default Vibely auto-routes to the best model for the task — reasoning models for coding, long-context for big inputs, precision models for refactors. You can pin a specific model per turn or per project from the model picker in the chat composer.

Does auto-routing cost more or less than picking one model?

It usually costs less. The router picks small, fast models for small turns and only uses heavyweight reasoning models when the task needs them. Pinning a single heavyweight model for everything is the most expensive option.

Can I bring my own model API key?

Not on the hosted product today. Self-hosters can wire any provider they want. See self-hosting.

Data and privacy

Where is my data stored?

User content lives in Vibely’s managed Postgres and storage. Sandboxes run in isolated cloud containers. Vibely is SOC 2 Type II compliant; details are in the trust centre at trust.vibely.app.

Is my code ever used to train models?

No. Vibely doesn’t train models on customer code. Models are accessed via provider APIs (Kimi, Gemini, Claude) under their respective enterprise terms — provider policies vary; consult their docs for current commitments.

Can I use my own database?

Yes. Connect a Supabase project under workspace settings and new projects use it instead of the shared default. Useful for production apps where you want full control over your data and infrastructure.

What happens to my data if I cancel?

  • Workspace and projects stay accessible until your billing period ends.
  • After the period ends, projects go read-only for 30 days, then are deleted.
  • Published custom domains return 404 within an hour of cancellation.
  • Exported GitHub repos are yours and unaffected.
You can export everything to GitHub before cancelling — that’s the recommended path.

Billing

What does Vibely cost?

See live pricing at vibely.sh/pricing. The headline plans are Free (trying it out), Pro (individuals and small teams), and Business (teams collaborating).

What’s a credit?

A credit is the unit of usage on Vibely. Credits cover model calls, sandbox compute, storage, and connector calls. See Plans and credits.

What happens when I run out of credits?

Builds pause until you top up. Existing projects stay running and accessible — only new agent turns are blocked. Published apps keep serving traffic; storage stays intact.

Can I refund unused credits?

Top-up credits are non-refundable but don’t expire as long as your plan is active. Monthly plan credits roll over for one billing cycle and then expire.

Can I set spending limits?

Yes — workspace admins can set spend caps in Workspace → Billing → Spend cap. When the cap is hit, the agent stops and notifies you.

Workflow

Can I keep editing the code in my own editor?

Yes. Sync to GitHub and edit there with whatever IDE you prefer — VS Code, JetBrains, or anything else. Vibely picks your changes back up the next time you prompt. See Project settings → GitHub.

Can a team work on the same project at the same time?

Yes — invite collaborators with per-project Admin / Editor / Viewer access, independent of their workspace role. See Project settings → Collaborators.

Things people often worry about

”What if I get locked in?”

You can’t be. Every line of code is yours, you can export to GitHub at any time, and once it’s in GitHub it runs anywhere — Vercel, Netlify, your own server. Even if Vibely disappeared tomorrow, your projects keep working.

”Is the generated code production-grade?”

Realistically: it depends on your prompts. With clear prompts and good iteration habits, the code matches what a competent senior engineer would write. With vague prompts and no review, you get the same thing you’d get from a junior who didn’t ask enough questions. Review the diffs.

”What if the AI does something I didn’t ask for?”

Every turn is a reviewable change — you see the files written, can roll back, and have version history. The agent is also asked to clarify before guessing if you give it the right custom instructions. See Prompting → Use the if-you-can’t-ask prompt.

”What about accessibility, security, compliance?”

Defaults are reasonable: WCAG-AA contrast in Design Mode, secret-detection on file writes, OAuth-first connectors. Production-grade compliance is your responsibility — Vibely produces code you can audit and ship, but it doesn’t promise the code is compliant by default.

Next

Glossary

Terms used across the docs.

Support policy

Response times, status page, security disclosures.

Plans and credits

What you pay for and how to keep it predictable.

Changelog

Recent product changes.