Documentation

From folder to live app.

Prepare your build, deploy it, and make the handoff dependable.

Give your AI one request.

Open the deployment guide in the project you are building. Your AI can inspect the project, install the CLI and deploy it; you approve access in the browser.

1. Copy the deployment prompt

Use the prompt on the deployment page with the AI tool working in your project.

Open the deployment guide ↗

2. Approve access

When the CLI requests device authorization, open the link and compare the code. Do not send your password or credential in chat.

3. Verify and share

Wait for a published result, then open the HTTPS URL. Check the main page, assets and nested routes before sharing.

Next: Deploy →

Build locally. Publish the result.

Cellapp accepts static frontends. Vite, Astro, or an exported Next.js site can fit when the output does not need a running application server.

Manual CLI path

Node.js 22.12 or later is required. Install @cellapp/cli from npm if needed, then run this command from the project directory, changing dist to your actual output folder.

Terminal
cellapp deploy --project . --output dist --build "npm run build"

Agent instructions

The public runbook covers project inspection, CLI setup, browser authorization, publishing and recovery.

Read Agent instructions ↗
Next: CLI / API Reference →

Know what the command does.

The deployment example publishes a static directory. Refer to the current CLI help and project documentation for supported flags, authentication, and API contracts.

Inspect available commands

Use the installed CLI help as the source of truth for your version.

Terminal
cellapp --help

API reference

The public client repository publishes HTTP contracts for supported deployment and application data operations.

View public client contracts ↗
Next: Configuration →

Keep secrets out of the build.

Static frontend files can be read by people who load your app. Treat values embedded in the build as public.

Separate public values from secrets

Use your frontend build tool for public configuration. Keep service credentials and deployment credentials outside the compiled frontend.

Share access deliberately

If access keys are enabled for an application, distribute the key to intended viewers separately from deployment credentials.

Next: Troubleshooting →

Find the missing step.

Most static deployment problems are visible in the output folder or the browser network panel.

A blank page or missing assets

Confirm index.html exists and that asset URLs match your hosting path. Check the browser network panel for failed requests, then rebuild and deploy the output folder.

A nested URL returns 404

Generate static entries for your routes or configure a host fallback that serves your entry document. Test a direct visit and a refresh, not just client-side navigation.

The upload did not finish

Read the CLI error, confirm the directory and network connection, and retry when the underlying issue is resolved. Include the command and error text when requesting help.

Find support in the project ↗
Deploy with AI →