Skip to content
MonstarXMonstarXMonstarX Docs

Export your app's code

In shortIn Settings → Export, click Download .zip to get the whole app as a standalone TanStack Start project, with its config, database migrations and a README with the commands to run and deploy it. Secret values, the rows in the database and uploaded files stay with MonstarX. For a copy that keeps up with every change, link a GitHub repository instead.

Your app’s code is yours. Export downloads all of it as a zip file: a normal web project that a developer can open, run on a laptop and deploy without MonstarX. Use it for a backup, a code review, or to hand the app to a development team.

How do I download my app’s code?

Section titled “How do I download my app’s code?”

  1. Open your project and click Settings in the workspace header.

  2. Choose Export.

  3. Click Download .zip. MonstarX makes the zip and your browser saves it, named after your project (for example lotus-flow-yoga.zip).

What is in the zip?

Section titled “What is in the zip?”
  • Every file of the app, including the files MonstarX manages for accounts, the database, email, storage and AI, and a MONSTARX.md that explains them.
  • The project setup: package.json, the Vite and TypeScript config and wrangler.jsonc (Cloudflare’s settings file), ready for npm install.
  • The database migrations — the instructions that create every table, including the tables for accounts.
  • .dev.vars.example with the names of the app’s secrets, and a README with the commands to run it and deploy it.

What is not in the zip?

Section titled “What is not in the zip?”

The values of secrets, the rows in the app’s database and the files people uploaded are not in the zip: they stay with MonstarX.

That keeps your keys and your users’ data safe. Your app’s data stays in its database, where you can see it under BackendDatabase and in the Admin tab.

How do I run the exported app?

Section titled “How do I run the exported app?”

The README in the zip has the exact commands. In short, a developer with Node.js installed runs:

Terminal window
npm install
cp .dev.vars.example .dev.vars   # then fill in the secrets
npm run db:migrate:local         # creates the tables in a local database
npm run dev                      # runs the app on their computer

To put it online on their own Cloudflare account, the README walks through wrangler login, creating the database, applying the migrations, adding the secrets and npm run deploy.

If your app keeps its data in Supabase or Railway Postgres, the README is written for that setup instead. An imported app exports as it is, with its own setup.

Zip or GitHub?

Section titled “Zip or GitHub?”

A zip is a copy of this moment. A linked GitHub repository follows every change instead, both ways: what MonstarX builds is pushed there, and what your developers commit there comes back into the project. If you want a copy that stays up to date, click Connect GitHub on the same page. See GitHub.

Frequently asked questions

Section titled “Frequently asked questions”
Do I own the code MonstarX writes?

Yes. Export downloads all of it, and you can run and change it without MonstarX.

Does the export include my users and data?

No. Secret values, database rows and uploaded files stay with MonstarX. The zip has the tables' structure (the migrations), not their contents.

Who can export a project?

Only its owner. People a project is shared with cannot download it.

What framework is the code?

A TanStack Start app — React and TypeScript, with server functions and Tailwind CSS — set up to run on Cloudflare Workers.

Will the exported app still send email and use AI?

The files for email, storage and AI are included. Outside MonstarX they need their settings filled in, or your own providers — MONSTARX.md and the README explain how.

Section titled “Related”
GitHubA copy of your code that keeps up with every change.
Publish to other hostsLet MonstarX deploy to your own cloud instead.
Project settingsThe rest of the Settings window.