13 FOCUSED GUIDES
Launch & operations
Prepare for quotas, schema changes, handoffs and export with evidence you can verify.
Managed hosting and a portable export solve different operational needs. Write/storage caps block writes, while the API-request cap blocks data requests including reads. The exported runtime covers compatible CRUD, auth and row policies; it does not include the hosted dashboard, MCP server, webhooks, billing, metering or managed backups.
Use the capacity calculator →Check backend readiness before an app launch
A launch review should exercise the intended workload and access boundaries, not just confirm that the homepage loads.
Read the guide →PRACTICAL FIELD GUIDEEstimate API requests from user behavior
API request volume follows application behavior, including polling and retries, rather than user count alone.
Read the guide →PRACTICAL FIELD GUIDEEstimate writes separately from API request volume
Write usage and request volume measure different work.
Read the guide →PRACTICAL FIELD GUIDEEstimate storage growth before keeping every event forever
Storage capacity depends on retained records, payload sizes and indexes.
Read the guide →PRACTICAL FIELD GUIDEDesign a useful UI for quota failures
Quota failures need a clear application state so users do not keep submitting an operation that cannot currently succeed.
Read the guide →PRACTICAL FIELD GUIDEKeep staging and production project configuration separate
Separate projects reduce accidental overlap only when URLs, keys and user sessions stay paired with the intended environment.
Read the guide →PRACTICAL FIELD GUIDERelease a schema change with client compatibility in mind
A schema change and a client deployment may not reach every user at the same time.
Read the guide →PRACTICAL FIELD GUIDERehearse an Eject export before you need it
An export becomes an operational exit path only after you have restored and tested it.
Read the guide →PRACTICAL FIELD GUIDEAn export download link expired
The database export uses a short-lived authenticated download, so an old link may stop working without indicating that the project data is gone.
Read the guide →PRACTICAL FIELD GUIDEReplace hosted API keys when moving to self-hosting
Hosted machine keys are not exported as reusable secrets.
Read the guide →PRACTICAL FIELD GUIDEKeep the self-hosted SQLite database on a persistent volume
A running container is not a durable storage plan by itself.
Read the guide →PRACTICAL FIELD GUIDEHand off a backend with more than a dashboard link
A useful handoff explains the model, access boundaries, integrations and operating limits.
Read the guide →PRACTICAL FIELD GUIDECapture useful evidence for a backend incident
A precise incident report links failed requests to project identity, caller type and time without leaking credentials.
Read the guide →