Platform capability · Multi-tenancy
Checks on every request, a separate database, or dedicated infrastructure
Shared platform services check the organization and the app instance on every customer request. Customer data in Authorization, Audit, Comments, Support, AI and sign-in accounts is kept in a separate database for each organization. Data and Automation use a separate database for each app instance. Where supported, a higher level of separation moves a customer’s data into a separate database or gives the customer dedicated infrastructure. Notification delivery is planned to follow.
Shared services start with customer data in shared tables, where each row is marked with its organization. Customer application data can use a separate database on a shared database server. Supported databases and components can then move to dedicated infrastructure, or the customer can use a fully isolated stack. Which level applies depends on the service and the deployment plan.
The platform’s provisioning creates and upgrades infrastructure across regions from one place, using infrastructure-as-code: databases, caches, queues, storage and service containers. Once created, each deployment runs on its own. Provisioning handles setup and lifecycle only, and customer requests do not pass through it.
An operator or an authorized customer can ask for dedicated capacity for an eligible component. The platform records the request and creates the new component. A migration for that component then tracks preparation, the data move, the switch, any rollback and completion. Database moves above the standard size limit for automatic moves run in a scheduled maintenance window.
Rows in shared services carry the organization and app instance they belong to, and the data-access layer requires both on customer queries. A separate database or separate infrastructure is an added boundary. It does not replace the check on each request.
Additions that extend the capability described above.
One record of every customer, app, plan and setting, with overrides for each customer
Every sign-in screen carries your brand
OpenTelemetry, traces, logs and dashboards
Regional placement of customer data, including the EU
One build, with each customer’s settings loaded when the app starts
A solution architect will demo the live service against your domain model.