Account Platform as a separate service
Architecture in progress — Account Platform is becoming its own OS process, not just a code module.
Architecture in progress — this page is a placeholder
As of this writing, only the first step of the shared migration plan has landed (merging the four products' branches into one integration line). Account Platform's own move to a separate OS process has not started. Nothing below is live yet — check back once that work closes.
What's planned
Per docs/plans/2026-09-03-three-services-separation.md,
each product becomes a real, separate OS process — its own systemd unit,
port, nginx domain block, and Postgres schema/role. Account Platform also
gains an Identity layer (users, orgs, entitlements) built as a layer above
today's team model, since agencies need one login across multiple creator
workspaces.
Cross-domain sign-on between the separated services is planned as an asymmetric-key token: Platform signs it with a private key, the other services verify it with a public key.
What's next
This page will be rewritten with real facts once Account Platform's own process split lands. Until then, see Boundaries for how the products are separated today, at the code level.