Deployment modes In development

Who this is for: teams deciding where SaaSLayer modules should run.

Every Customer gets an Instance: the set of SaaSLayer service stacks deployed for them. Where that Instance lives is a topology choice.

Hosted, shared account

SaaSLayer operates the Instance in SaaSLayer-managed AWS accounts. Fastest start, no AWS access required from the Customer. Tenant isolation is enforced at the service layer.

Hosted, dedicated account

The Instance runs in an AWS account dedicated to one Customer, still operated by SaaSLayer. Stronger blast-radius isolation and clean per-Customer cost attribution.

Cloud-prem

The Instance runs in the Customer's own AWS account, provisioned and updated by the SaaSLayer Control Plane through a scoped cross-account trust role. Data stays in the Customer's account; the Customer can audit every resource. This is the mode for teams whose compliance posture requires owning the infrastructure.

How provisioning works (all modes)

The Control Plane's deployer treats each module deployment as a managed lifecycle: create, update, destroy. Deployment outputs are recorded in a manifest registry so other modules — and your product — can discover endpoints and resources without hardcoding anything.

Cloud-prem and dedicated-account modes are actively hardening with the first customer deployments; the shared-account path is how SaaSLayer runs its own platform today.