Backwrite architecture and branch ownership
Backwrite organizes database projects into branch environments and separates application data access from infrastructure management.
Gateway and control plane
The gateway exposes HTTP data access and developer SQL connectivity. Control services manage organizations, projects, provisioning, branch lifecycle, migrations, and backups. Deployment addresses and enabled services depend on your installation.
Branch-owned resources
The documented ProjectBranch model associates a branch with its database, storage namespace, queues, event streams, secrets, policies, and configuration. Do not treat a branch ID as a global environment or a platform release channel.
Durable lifecycle operations
Branch creation, deletion, and promotion use recorded operations with per-step progress. The branch service can resume work and compensate for failed provisioning steps. Poll an operation rather than assuming an accepted request means the branch is ready.
Promotion semantics
The documented promotion workflow moves schema, policies, and configuration artifacts. It does not merge application rows from a preview branch into production. Check the target and inspect migration consequences before promotion.
Engine and integration boundaries
PostgreSQL provides relational storage. NATS JetStream provides messaging and workqueues, and S3-compatible storage provides object namespaces. These responsibilities are distinct; deployment-specific availability must be verified.