Export code and GitHub sync

Your app is real code, and on Pro and Teams you can take a copy of it: download the whole project as a zip, or connect a GitHub repository that Vaulter keeps up to date automatically. Both live in Vault → Deployments, on the Code card.

Download as a zip

Click Export on the Code card and you get a zip of the full project: every page, component, and configuration file, in the same production-ready shape that publishing ships. Open it in any editor, archive it, hand it to a developer; it is a complete, standard React and TypeScript codebase.

GitHub sync

Better than a one-time download is a repository that stays current:

1. Connect GitHub

   On the Code card, choose a repository name and click connect. GitHub's own authorization window opens; approve it, and Vaulter creates the repository under your account and links it to the project. You need an admin role on the project to connect.

2. Publish as normal

   From then on, every publish also pushes a commit to the repository: the exact code that went live, one commit per publish, on the repository's default branch. Your GitHub history becomes a faithful release history of your app.

3. Open the repository any time

   The card links straight to the repo. Browse the code, diff releases, clone it locally, wire up your own tooling on top; it is your repository, on your GitHub account.

The direction of sync

Sync is one way: Vaulter to GitHub. Vaulter is the source of truth, and the repository is a continuously updated export. Commits you push to the repository yourself are not pulled back into Vaulter, and the next publish will overwrite conflicting changes on the synced branch. If you want to hand-edit code, do it in Vaulter's code editor, where the agent and the build pipeline can see it.

This is deliberate: it makes sync impossible to break. There are no merge conflicts, no divergence, and no state where your live app and your builder disagree about what the code is.

Disconnecting

Disconnect from the same card. Vaulter stops pushing; the repository is yours and is not deleted, keeping everything already exported. Reconnecting later resumes pushes to whichever repository you choose.

Frequently asked

Which plans have this?

Code export and GitHub sync are Pro and Teams features, gated on the workspace plan. On other plans the card shows locked.

Is the exported code usable outside Vaulter?

Yes; it is a standard modern web app. Note that platform services (the built-in database, auth portal, connectors) are part of Vaulter's runtime, so running the app fully independently means providing your own equivalents. As an escape hatch and an audit trail, the export is complete. See Known limitations.

Can Vaulter import a repository?

No. Sync is export-only, and there is no repository import. New apps start from a prompt or a template.

Does the sync include my secrets or data?

No. The Vault's secrets and your database contents are never part of the code, so they are never in the zip or the repository.