Deployment Models and Scope
SynckHub uses three separate concepts:
- Deployment: how services are wired and operated
- Edition: self-host capability boundary
- Plan: SaaS entitlement tier
Do not mix them.
Practical deployment targets
local: single-machine developer stackdev: shared, production-like environmentselfhosted-prod: production deployment for one organization
What a real production deployment must cover
At minimum, production self-hosting means:
- TLS-terminated public edge with stable hostnames
- durable Postgres and blob storage
- Common to SynckHub control-plane wiring
- pinned release images
- backup and restore discipline
- a maintenance-window deploy process
- explicit handling for every optional integration you enable
For self-hosted production:
- no insecure auth bypasses
- TLS edge is mandatory
- stable Postgres and blob persistence are mandatory
Edition expectation for self-host
Self-host distributions are edition-gated. The documented boundary is Personal, Business, Enterprise.
Important implementation note:
- license enforcement for self-host is planned and not fully implemented across all code paths yet
Design your rollout around current server behavior and explicit entitlements, not marketing assumptions.
Scope warning
Do not promise features operationally just because code exists somewhere in the tree. Only enable what you can route, secure, back up, and support.