Your first Instance In development

Who this is for: teams ready to try SaaSLayer against a real environment.

Provisioning a Customer Instance walks through a fixed sequence. The exact onboarding flow is being productized with our first customers — this page describes the shape so you know what to expect.

1. Choose modules and topology

Pick the modules the Instance needs (user service, permissions, event delivery) and a deployment mode. Cloud-prem additionally requires a one-time cross-account trust role in your AWS account.

2. The Control Plane deploys the Instance

The deployer creates each module's stacks and records every deployment's outputs (API endpoints, resource names) in the manifest registry. Updates and teardown run through the same lifecycle — no snowflake stacks.

3. Owner bootstrap

The user service seeds the owner: the first Customer Admin identity. The The permissions service seeds a namespaced admin role scoped to your Instance, so the owner can log in to the Admin Console and start inviting the rest of the team.

4. Integrate your product

From here integration is API/SDK work: authenticate End Users against the user service, call the RBAC checker on your hot paths, subscribe to events, and embed widgets where your product needs them. The Permissions quickstart is the best next step.

Want to be one of the first deployments? Talk to us.