Taking your code with you

What comes out

Installed packages and build output are left out; the export is pure source.

• All of the screen and feature code
• The files that create your tables
• A readme with how to install and run it
• Our connector tools included as source, not as a reference to us

What “not tied to us” means

The parts we did not write come from public packages anyone can install. The parts we did write are included as source. It runs without an account here.

Pushing to your own repository

Connect a repository and the code goes there as well as staying here. This is the easiest handover when a developer joins you.

Editing the code without leaving

You can open and edit the code inside the builder. That costs nothing, and what you change carries forward into the next run the AI does.

Data is a separate matter

The structure that creates the tables goes with the export. What your customers typed lives in the database, and moving that is a separate step. Structure and contents are different things, so they do not come out in one bundle.

When it is worth doing

There is no need while you are still building. These are the moments people usually take a copy.

• When a developer is taking it on
• Just before you open, to keep that state
• When you want to run it somewhere else
• When you are stepping away for a while

Common questions

Can I hand it to a developer? Yes. It is built the way web projects usually are, so a web developer can read it straight away and carry on from your repository.

Does exporting stop my app here? No. Exporting and continuing to work here are independent. The app keeps running exactly as before.

Is the built output included? No. Build output and installed packages are excluded, so whoever receives it installs once and runs it.