Deploy an application

Package your generated application with its pinned dependencies and configured factory. Choose your platform’s process manager, secret injection and durable storage. Server and worker processes each construct their own application graph.

Release sequence

1. Run credential-free tests and representative evaluations against the candidate version.
2. Back up retained state and inspect migration status with the deployment’s exact configuration.
3. Apply supported migrations as a separate one-off step.
4. Start authenticated server and worker entrypoints with shared durable stores where required.
5. Inspect readiness, run one bounded operation and verify its retained result.
6. Exercise cooperative shutdown and the chosen recovery policy before increasing traffic.

Use storage for migration preflight and pooling. Configure PostgreSQL explicitly when local SQLite is inappropriate. Mount durable paths rather than relying on an ephemeral container filesystem.

Own the platform boundary

Configure TLS, authentication, authorized data access, process restart policy and environment cleanup for your deployment. cayu worker has bounded shutdown and failure handling; it does not restart failed workers or choose abandoned-session policy.

The cayu cloud commands are an optional hosted deployment path. Their release-matched CLI flags are in the cloud reference. Availability, accounts and commercial limits depend on the hosted service; these docs’ local framework workflows are independently runnable.

For a release change, use upgrades and retain the exact tested version and migration receipt.