New: 14+ data connectors live. See all →

Data Architecture

Your data. Your database. Always.

BuildIQ was designed from day one around the principle that no tenant's data should ever be accessible by another — not even by accident, not even in the case of a misconfigured policy.

Zero cross-tenant data sharing, by architecture

Five isolation models

Choose the level of isolation that matches your compliance requirements and budget. You can migrate up at any time.

01

Shared Schema

Starter plan

All tenants share a single PostgreSQL schema. Row-level security policies restrict data access per tenant. This is the standard multi-tenant model used by most SaaS platforms.

Benefits

  • Lowest cost
  • Instant provisioning
  • All features available

Considerations

  • RLS policy is the only separation layer
  • Not suitable for regulated industries
Default (Professional)
02

Schema-per-Tenant

Professional plan

Each tenant gets a dedicated PostgreSQL schema within a shared database instance. Queries are physically separated at the schema level — not just by row filter.

Benefits

  • Schema-level separation
  • No RLS dependency
  • Tenant-specific migrations possible

Considerations

  • Shared DB server resources
  • Not full database isolation
Maximum Isolation
03

Dedicated Database

Enterprise plan

Each tenant gets their own dedicated PostgreSQL database instance. Maximum isolation — no shared server processes, no shared buffer pools, no shared transaction logs.

Benefits

  • Full database isolation
  • Independent backups & scaling
  • Custom configuration per tenant
  • Exceeds GDPR Article 32 requirements

Considerations

  • Higher infrastructure cost
  • Requires Enterprise plan
04

Dedicated Server

Enterprise (Premium)

Your database runs on a dedicated compute instance entirely separate from other tenants. No shared hypervisor threads for the most demanding compliance requirements.

Benefits

  • Physical compute separation
  • Meets government / classified requirements
  • Custom OS hardening
  • Private VPC available

Considerations

  • Premium pricing
  • Longer provisioning time
05

Air-Gapped / On-Premise

Enterprise (Bespoke)

BuildIQ deployed entirely within your own infrastructure — on-premise, private cloud, or government enclave. Zero traffic leaves your perimeter.

Benefits

  • Complete sovereignty
  • No internet dependency
  • Meets classified / defence requirements
  • Custom deployment pipelines

Considerations

  • Requires dedicated DevOps
  • Longer implementation timeline

Core isolation principles

These are architectural constraints, not configuration options.

No data-store sharing

We never write tenant A's data to tenant B's schema. This constraint is enforced at the application layer, not just by policy.

Service role key never exposed

Our Supabase service role key (which bypasses RLS) is never returned in API responses or accessible from the frontend.

Vault-referenced credentials

External system credentials are stored with a vault_key_path reference — the actual secret never appears in API responses.

Agent context scoping

Every AI agent run is scoped to a single tenant. Agent memory, prompts, and retrieved context are isolated per org.

Need a specific isolation model?

Talk to our team about dedicated database or on-premise deployment options.