Getting started
Core concepts
The handful of words that show up everywhere in Vaulter: projects, preview vs published, the vault, builders vs end users, and backends.
A few words show up all over Vaulter. Knowing what they mean makes the rest of these guides easier to follow.
Project
A project is one app you are building. Everything about it lives together: its pages, its data, its design, and its settings. Your dashboard lists all of your projects, and each one opens into the build workspace.
Workspace
Projects live in a workspace. You have a personal workspace of your own, and on the Teams plan you can share a workspace with up to five people, with a shared token pool and roles (owner, admin, editor, viewer). Your plan and billing attach to the workspace.
Preview vs published
There are two versions of your app, and it helps to keep them straight.
- The preview is the version you build against. It rebuilds automatically as you work, and only you and your collaborators see it.
- The published app is the version your visitors see, live on the web at your app's own address. It only changes when you publish.
You can keep changing the preview freely without affecting the published app. See Preview vs published.
Builder vs end user
- You are the builder. You sign in to Vaulter to create and change apps.
- An end user is someone who uses an app you published. They sign in to your app through the hosted portal and get their own account inside your app, separate from your Vaulter account.
The agent
The agent is the AI that builds and changes your app. You talk to it in the chat. It reads and writes your app's code, works with your data, and repairs many problems on its own. See How the agent works.
Tokens
Vaulter meters usage in tokens, the unit of AI work. Every plan includes a monthly token allowance, and your usage page shows how much of the pool you have used. Bigger requests and deeper models use more tokens. See Plans and pricing.
The Vault
The Vault is the settings hub inside the build workspace: Database, Auth, Connectors, Domains, Analytics, SEO, Deployments, Storage, and Team all live there. When the agent needs an API key from you, it asks you to set it in the Vault so secrets stay out of your code. See The Vault and secrets.
Backend
Your app's backend is where its data lives. Apps are born on a Vaulter-managed backend that needs no setup and enforces per-user privacy automatically. If you would rather run your own, you can bring your own Supabase.