FAQ

The quick answers. For anything deeper, the linked pages go further.

Do I need to know how to code?

No. You build by describing what you want in plain language. If you do code, you can open and edit the code directly — see Editing your app — but it's never required.

Is it a real app or just a mockup?

A real, running application — actual pages, a real database and working navigation. Vorx even clicks through each build in a headless browser before showing it to you. That's what lets you keep changing it and ship it to a live URL.

Do I own what I build?

Yes. The app and its data are yours. Connect a repository under Settings → GitHub to take the codebase, and export any table to CSV.

Can several people work on one project?

Yes — projects are shared across a workspace with realtime editing and comments, and sharing settings control who can change what.

What does a build cost?

Credits, charged on the real model spend for that run and rounded up to a whole credit, with a minimum of one. Each reply shows what it used. Undo and rollback are free. See Plans and credit usage.

What happens if I run out of credits?

New builds pause until you add credits, upgrade, or your next grant arrives. Your app and data are untouched, and a published app keeps serving. See Usage and limits.

Can I undo a change?

Always. Every change is a checkpoint you can roll back to, and rolling back costs nothing.

Note that checkpoints cover your app's code, not its data — rows created since aren't rewound.

Does rolling back change what my users see?

No. Your working copy and your published app are separate; nothing reaches users until you publish again.

Can I use my own domain?

Yes — connect a custom domain from the Publish dialog, with automatic HTTPS.

Why doesn't Google sign-in work in the preview?

It needs a real published URL to return to. Publish first, then test on your live site — see Social login.

Is my project public once I publish?

Your app is public at its URL. Your project, chat and code stay private to your team.

Next steps

• Troubleshooting — when something's broken
• Glossary — the vocabulary
• Welcome — the tour