Data tenancy
Atomic offers two tenancy models that differ in how data and compute resources are allocated between customers. The right model depends on your organisation's scale, regulatory requirements, and data separation policies.
Tenants are hosted in the following AWS regions:
- Australia (
ap-southeast-2) - United States (
us-east-1) - Ireland (
eu-west-1) - New Zealand (
ap-aoutheast-6)
Isolated tenancy
An isolated tenant is a dedicated instance of the Atomic platform. All services, data stores, and compute resources are provisioned exclusively for a single customer and are entirely separate from other Atomic customer instances.
Key characteristics:
- Physical data separation: all data stores contain only your organisation's data, with no shared infrastructure at the storage or compute layer.
- Independent scaling: resource scaling is based solely on your organisation's activity.
- Regulatory compliance: meets the highest standard of compliance for customers with regulatory or policy requirements that mandate physical separation of data and compute.
Additionally, Static IP addresses can be enabled as an add-on so that the Atomic SDK will connect to your dedicated instance served by static IPs, which makes it possible to zero-rate your Atomic SDK traffic for customers on your network.
Isolated tenancy is suited to enterprise customers and those in regulated industries where policy or compliance frameworks require physical separation of customer data.
Shared tenancy
A shared tenant is an instance of the Atomic platform where service resources are allocated across multiple customers. Data is logically separated at the application level.
Key characteristics:
- Logical data separation: customer data is isolated at the application layer using database-level access controls that ensure queries can only ever return data belonging to your organisation. This separation is routinely penetration tested and architected to provide secure logical independence between customers.
- Shared scaling: compute and storage resources are shared across customers. Atomic allocates each customer to a shared tenant appropriate for their needs and monitors and adjusts instances to accommodate usage spikes.
Shared tenancy is suited to customers with smaller-scale usage needs that do not have regulatory or policy requirements for physical data separation.
Comparing tenancy models
| Isolated tenancy | Shared tenancy | |
|---|---|---|
| Data separation | Physical | Logical |
| Compute resources | Dedicated | Shared |
| Static IP addresses | Yes (add-on) | No |
| Regulatory / compliance use cases | Yes | - |
Contact support if you have questions about which tenancy model applies to your organisation or to discuss tenancy requirements during your evaluation of Atomic.