Deploying Your Apps

Deploy from Studio with a single keystroke. The platform handles schema sync, backend compilation, frontend publishing, and process supervision.

Deploy from Studio

Press Run (F5) in Studio. That's the entire deployment workflow.

Studio deploys to the Core instance your project is connected to. If you created your project on rootcx.com, your app is immediately live at https://<your-ref>.rootcx.com/apps/<appId>/.

What Happens on Deploy

When you hit Run, Studio executes a five-step pipeline:

1. Schema verify -- validates the manifest before applying changes.
2. Manifest sync -- the Core reads manifest.json and registers (or updates) the application, its entities, fields, permission keys, and actions.
3. Install dependencies -- runs bun install if a package.json is present in the backend.
4. Deploy backend -- the backend worker is uploaded and started under the Core's process supervisor. If a previous worker is running, it is replaced.
5. Publish frontend -- uploads the pre-built static assets to the Core, which serves them at /apps/{appId}/.

Each step logs output to the Studio console in real time. If any step fails, the error is shown immediately.

How Apps Are Served

Apps built on RootCX can run in three ways:

Deploy via API

You can also deploy without Studio using the REST API:

# Deploy backend
cd backend && tar -czf ../app.tar.gz . && cd ..
curl -X POST https://<your-ref>.rootcx.com/api/v1/apps/crm/deploy \
  -H "Authorization: Bearer $TOKEN" \
  -F "archive=@app.tar.gz"

# Deploy frontend (after building with vite)
cd dist && tar -czf ../frontend.tar.gz . && cd ..
curl -X POST https://<your-ref>.rootcx.com/api/v1/apps/crm/frontend \
  -H "Authorization: Bearer $TOKEN" \
  -F "archive=@frontend.tar.gz"

Further Reading

• Getting Started -- first launch and your first deploy.
• Backend Development -- lifecycle hooks, RPC, and error handling.
• Self-Hosting -- run the Core on your own infrastructure.
• Core reference -- architecture and configuration of the Core daemon.