Download your app's source code

The code the agent writes for your Onplana Maker app is yours. You can download it as a .zip at any point, on any plan, and there is no cap on how often. It is an ordinary Vite and React project, so it runs anywhere Node runs.

Downloading is a copy, not a move. Your app stays exactly as it was, the live URL keeps serving, and you can carry on building in Onplana afterwards.

Download the code

1. Open the app in Build.

2. Open the Source files panel. It lists every file in your app.

3. Click the download icon in that panel’s header, labelled Download code (.zip).

The file that lands is named after your app, for example my-app-source.zip.

What the download contains

Everything in the Source files list, which is the same set the panel shows you, so you can check what you are about to get before you click. A typical app that started from the default scaffold contains:

File	What it is
package.json	Dependencies and the dev and build scripts
vite.config.js	The Vite configuration
index.html	The page shell
src/main.jsx	The entry point
src/App.jsx	Your app itself

Plus every file the agent has written since, and any files you uploaded to the project, which are mirrored into the app at public/assets/<name>. See Use your files in a build.

It is the source, not the built site. You get the code the agent edits, not the compiled output that gets published. Running npm run build reproduces that output.

Four things are deliberately absent:

• node_modules. Standard for any source download. npm install fetches them.
• Your app secrets. See the caution below.
• Data your app collected. Form submissions and counters live in your Onplana workspace, not in the code. See Collect form submissions.
• A lockfile. package.json pins its direct dependencies to exact versions, so you get the same React and Vite the app was built against. Transitive dependencies resolve fresh at install time, as they would for any project without a committed lockfile.

Run it on your own machine

You need Node 18 or newer.

1. Unzip the download and open the folder in a terminal.

2. Install the dependencies:

   npm install

3. Start the dev server:

   npm run dev

   Your app opens at http://localhost:5173.

4. To produce the files you would upload to any static host:

   npm run build

   The result lands in dist/.

Because the output is plain static files, any static host will serve it. If you would rather keep Onplana hosting it on an address you own, see Serve your app on your own domain.

Your secrets do not come with the code

Caution

App secrets are never in the download. They are held in Onplana’s backend and are not readable by your app’s code, which is exactly what stops them reaching your published page. A downloaded copy therefore has no keys in it.

If you take the app somewhere else, supply those values yourself in whatever the new host uses for configuration. Any code the agent wrote that reads a secret will expect one to be present.

This is worth understanding rather than working around, so read How your published app and its data are kept safe before pasting a key into a file to make a local run work. A key hardcoded in your source is readable by anyone who visits the published app, and Onplana blocks a publish outright when it finds a live payment key.

Who can download

Downloading the source needs full control of the app: its creator, a colleague you gave full control to, or an Owner or Admin in the workspace.

Someone with read-only access cannot download the code. They can open the app and use it, which is the point of read-only sharing, but the editable source is not part of that. See Share an app with your teammates for the difference between the two levels.