Data Isolation Strategies (Authentication Namespace & Single-Tenant Database)
For organizations that need stronger data separation than Sub-Organizations provide, Healthie offers two additional isolation strategies: Authentication Namespace Separation, which scopes login access to a dedicated namespace tied to a white-labeled domain while data stays in the shared multi-tenant database, and a Single-Tenant Database setup, which places a customer in their own dedicated Postgres instance entirely. Both require a full or semi white label, and the single-tenant option can still support multiple organizations within that dedicated instance.
Built by Core Engineering
The problem it solves
Sub-Organizations provide strong application-level data separation, but some customers, particularly those with strict compliance, contractual, or security requirements, need an even stronger guarantee that their data is isolated from other Healthie customers. This solves that by offering deeper isolation strategies, up to and including a fully dedicated database instance, beyond what a standard multi-tenant account structure provides.
What's included
- Authentication Namespace Separation, scoping login access to a customer-specific namespace
- Single-Tenant Database option, placing a customer in a fully dedicated Postgres instance
- Support for multiple organizations within a single-tenant instance
- Full or semi white-label requirement for either strategy
- Account-switching option for users who work across multiple isolated organizations
How it works
An organization with sufficiently stringent data isolation requirements works with Healthie to determine the right strategy. For Authentication Namespace Separation, the organization's white-labeled domain and mobile app become the basis for a dedicated authentication namespace, scoping login access to that customer while data remains in the shared database; some API arguments need adjusting to reflect this namespace. For a Single-Tenant Database, Healthie provisions a new, dedicated Postgres instance for the customer, who can still create multiple separate organizations within it, each billed for additional seats as needed. In both cases, if a clinician or patient works with more than one organization, they'll see an option to switch between their separate Healthie accounts when logging in from a shared, non-white-labeled domain.
For organizations that need data separation beyond what Sub-Organizations provide, Healthie offers two additional isolation strategies. Authentication Namespace Separation scopes an organization's login layer to its own namespace, tied to its white-labeled domain and mobile app, while the underlying data still lives in Healthie's shared multi-tenant database; this requires a full or semi white label and some adjustment to API arguments. A Single-Tenant Database setup goes further, placing the customer in an entirely separate Postgres instance, with all of Healthie's normal application-level separation protections still in place; a customer on this setup can still run multiple distinct organizations within their own dedicated instance. Because users across these isolation strategies still log in from the same default domain or mobile app (unless white-labeled), a person working across multiple organizations may see the option to switch between their accounts.