# Setup and deployment status

Updated: 2026-10-18

**Experimental setup reference · reviewed October 18, 2026.** Start with a specific workload in the [company pilot](/pilot). Source access, a local runtime, an account-owned deployment and a managed service have different readiness requirements.

## Source licensing and access

The independently authored runtime source carries an MIT license. Dependencies retain their licenses and notices. Both project repositories currently require private access. A public source release is still pending; the license does not make a private repository publicly downloadable. Ask about source access and the appropriate revision through the pilot.

## Existing local instructions

Participants with runtime source access can follow the versioned `docs/RUNTIME_PROFILE.md`, `docs/SETUP.md` and `docs/DEPLOYMENT.md` in that repository. The PostgreSQL-backed local recipe uses the repository's declared PostgreSQL fixture and workerd configuration:

```sh
pnpm install --frozen-lockfile
pnpm local:up
pnpm dev
```

Use the versioned runtime profile for prerequisites, org provisioning, authentication and shutdown. The local setup service also has an offline fixture mode; that mode demonstrates the setup protocol and does not establish reference parity or deploy resources. The website's [browser experiments](/#playground-title) run a much smaller fictional-data profile on your device.

## Account-owned deployment recipe

The runtime's `pnpm deploy:runtime` command prepares a plan for Cloudflare Workers, Hyperdrive and R2 with a reachable PostgreSQL 18 database. The command performs provider writes only when its explicit apply option is selected. Read the versioned deployment document before choosing resources or supplying credentials.

**The recipe exists; a customer-cloud runtime deployment has not been verified in the current website evidence.** The deployed marketing website and pilot application database are separate services. Their deployment does not verify a hosted org, tenant isolation, workload performance or recovery.

Cloudflare and the database provider remain dependencies. Account permissions, provider charges, location, storage, secrets, upgrades, monitoring and coordinated database/file recovery need an operator. No cost estimate, production allocation or service-level guarantee is established by the local recipe.

## Export and recovery

The local runtime implements export and restore, including optional file bodies and preservation of record IDs within a new org identity. [Read the exact current scope](/why/evidence#operations-backup-export), including exclusions and locally verified status. An application export is not a substitute for a tested database and file backup/recovery plan.

## Managed hosting and the next verification

Managed deployment, upgrades, monitoring and recovery are a service direction under development. The pilot should identify the required runtime contracts, access paths, provider resources, operating responsibilities and exit format for the selected workload.

Before treating a deployment path as ready, record the deployed revision and resource configuration, verify its authorization and representative workload, and test upgrades, export/restore, recovery and teardown. Document costs and limitations for that profile. Public source access, a broadly verified self-hosting path and commercial service terms remain separate milestones.

[Explore a pilot](/pilot) · [Read our promise to you](/why)