Build an app you can run yourself

Choose the behavior, then the design

A directory might need search, filters and detail pages. A client portal might need accounts, related records and forms. A subscription product might add checkout and entitlements. Describe these flows in your Build brief so the agent can plan and verify the working application.

Built-in application components

• Lead capture and forms: declared fields, validation, stored submissions and review screens.
• Directories and structured collections: searchable catalogs and lists of projects, people, products or other content.
• Records: related entities, CRUD operations, accounts and access-policy variants.
• Content: static blog posts, RSS, metadata and sitemaps. Structured collections do not imply a full content-management editor.
• Commerce: Stripe checkout, webhook handling and entitlements, with operator-supplied prices and credentials.
• Integrations and operations: authenticated webhooks, first-party analytics and feature flags.

Components have supported combinations: forms and analytics need a data-backed app, for example. The agent can also build custom interfaces and behavior in the workspace. A live payment, email or other external service requires your configuration; a demonstration does not create those accounts for you.

Export a Docker Compose bundle

1. Finish the build and inspect its preview and verification results.
2. Open the project's Self-host panel and check its assessment.
3. Download the self-host bundle for a supported web app.
4. Read SELFHOST.md and configure the environment variables listed in .env.example.
5. Run docker compose up -d --build from the extracted project directory.

The bundle includes the source, compose.yaml, Dockerfiles, .dockerignore, .env.example, SELFHOST.md and release.json. Multi-service bundles may put Dockerfiles under selfhost/. Declared persistent storage uses named volumes; supported migration steps run before the application starts.

Read the export status

Ready to self-host means runtime verification has passed. Bundle available means a candidate bundle exists but has not passed that check. Needs review lists blockers. Downloading source alone does not establish that an application is ready for deployment.

Runtime support includes static sites, Node, Python and projects with their own container setup. Some AppKit exports currently use Wrangler's development runtime with local, persistent D1 inside the container. Read the generated instructions for the actual runtime and deployment limits of your project.

Service keys are supplied at deployment; the generated environment template contains variable names, not saved credentials. The default published port is loopback-bound. Set up your own domain, HTTPS and remote access when deploying on a server.

Back to Build capabilities