What does a SaaS architecture look like?
Most SaaS platforms share the same core components: an application tier serving the interface and API, a database with tenant isolation, an identity layer that manages users and permissions, a billing system that tracks subscriptions, a background job runner for longer tasks, and administration tools for the provider’s staff.
The identity layer answers two separate questions: who the user is (authentication) and what their organisation is entitled to (entitlement). A user can be fully authenticated but unable to use a feature that is not included in their organisation’s plan.
Background jobs handle tasks such as sending email, generating reports, syncing with other systems and processing uploads. Running these through a queue with retries makes the platform more reliable.
Administration tools allow support staff to reproduce issues, finance teams to apply credits and engineers to investigate failed integrations, without direct database access.
Platforms differ mainly in their tenancy model and in which components are bought rather than built. Identity, billing and queues can use managed services, while entitlement rules and administration tools are usually built to reflect how the business operates.
Related service
Custom SaaS DevelopmentMulti-tenant platforms with billing, administration and access control built in.
Was this helpful?