Dedicated database
Every client gets their own database and workspace, not a shared table with a filter applied to it.
Security & segregation
Your data, in your own database.
Every client gets their own database and workspace - not a shared table with a filter applied to it. For an explorer, the data is the balance sheet. It should not sit beside a competitor's.
Access you define
Permissions set by role and by project. A field tech, a geologist and an administrator each see exactly what they should.
Enforced at the data
Access rules are applied in the database itself, not merely hidden in the interface.
Always exportable
Clean CSV and drillhole-database-ready exports on demand, throughout the term and on exit.
Where it lives
Provisioned in the region nearest your operations - and it stays there.
If you leave
Full export on request, and your database is decommissioned on a schedule you set. Nothing is silently retained.
How segregation actually works
One tenant, one database - structurally, not by convention.
This isn't a shared table with row-level filters. Each client is its own isolated instance, from the subdomain you sign in on through to the database that answers the query.
- All data is stored in independent, cloud-hosted SQL databases - access is through your organisation's own Stratigen tenant ID at sign-in.
- Users are only ever authorised against their own organisation's database instance. A cross-tenant request is rejected before it reaches any data.
- The application interface is identical for every client. The lookups and the underlying database are tenant-specific.
- Role-based editing permissions: Admin, Geologist, Field Technician, Viewer.
Still have questions?
Ask us about your specific setup.
Data residency, retention, exit terms - if it's not answered here, we'll answer it in writing before you commit to anything.
Talk to us