Skip to main content

Trust · v1 · 2026

Trust, hosting, and the honest state of the platform.

A reference page for procurement and security teams. Each row is marked with what ships today, what runs only in pilot, and what is on the planned runway to GA. If a guarantee you need is not on this page, ask us before signing anything.

Pilot postureManaged onboardingNo self-serve signupGuided pilots only

Last updated · 2026-06-15

01

Hosting and deployment

Audit 360 is a modular monolith (NestJS + Next.js, PostgreSQL, Redis, object storage). The platform is deployed per-tenant on dedicated infrastructure managed by Sigmoid Analytica.

  1. Managed single-tenant deployment

    Each pilot customer gets a dedicated database, object store, and application instance. No shared application runtime across customers in pilot phase.

    Pilot posture by design — pre-GA we are not running shared multi-tenant infrastructure.

    Pilot

  2. Multi-tenant isolation in the data model

    Every queryable entity carries a `tenantId` foreign key. Service-layer queries are tenant-scoped at the API boundary; cross-tenant reads are not exposed at any endpoint.

    Verified in Prisma schema and the API access-control layer.

    Live

  3. Cloud infrastructure-as-code (Kubernetes / Terraform)

    Production deployment automation. Today, customer deployments are provisioned by the engineering team via documented runbooks; full IaC is on the runway to GA.

    Roadmap
02

Tenant isolation and audit trail

Tenant isolation and the audit log are platform behaviour, not a configuration toggle. Both are enforced at the schema and service layers.

  1. Tenant-scoped audit log

    Every write operation is recorded with actor, timestamp, and a before/after JSON snapshot. The audit log is `tenantId`-scoped — no cross-tenant access path exists.

    Live

  2. Source → risk → plan → engagement lineage

    Every artefact carries a queryable trail back to the source documents it was built from. Lineage is a SQL query, not a manual reconstruction.

    Live

  3. Audit log retention windows (configurable per tenant)

    Today the audit log is retained for the lifetime of the deployment. Configurable retention policies are on the GA runway.

    Roadmap
03

Identity and access

Authentication is JWT-based with password credentials. SSO and MFA are on the runway to GA — pilot customers operate without them today.

  1. Role-based access control

    Roles enforce state-transition permissions across the platform (e.g., only `AUDIT_DIRECTOR` or `CAE` can approve an annual plan). Roles are checked at the service layer, not just the UI.

    Live

  2. JWT + refresh-token auth

    Access tokens with refresh-token rotation. Passwords meet a 12-character minimum and are stored as Argon2 hashes.

    Live

  3. SSO (SAML / OIDC)

    Enterprise identity integration. Required for GA — will be available before any non-pilot deployment.

    Roadmap

  4. MFA (TOTP / WebAuthn)

    Multi-factor authentication for human users. Required for GA — will be available before any non-pilot deployment.

    Roadmap
04

Data residency and sub-processors

Pilot deployments run in a customer-aligned region with a documented sub-processor list. Procurement teams: ask us for the current sub-processor disclosure before signing.

  1. Customer-aligned hosting region

    Pilot deployments are placed in the customer-relevant region (e.g., South Africa for public-sector South African customers). Region selection is part of pilot scoping.

    Pilot

  2. Sub-processor disclosure

    A current sub-processor list — covering hosting, email delivery, observability, and object storage — is available on request before a pilot contract is signed.

    On-request disclosure today; public sub-processor page is on the GA runway.

    Live

  3. Data export and termination

    On pilot termination, all customer data is exported in a documented format and the production instance is shut down. Retention windows post-termination are part of the pilot agreement.

    Pilot
05

Pilot vs GA posture

Audit 360 is in a managed-pilot phase. Pilots are scoped, signed, and onboarded with engineering involvement — not a self-serve product. GA posture will add the items marked Roadmap above.

  1. No self-serve signup

    There is no public sign-up form. Pilot scope, region, integration touchpoints, and SLAs are part of a contracted engagement.

    Live

  2. Guided onboarding

    Every pilot gets an onboarding engineer for tenant provisioning, first admin invite, organisational structure import, and configuration walk-through.

    Live

  3. Published SLAs and uptime targets

    Pilot SLAs are part of the contracted engagement today. Published uptime targets and credits are on the GA runway.

    Roadmap

Talk to us

Procurement question we did not answer? Ask us before signing.

This page covers what we can publish. For sub-processor lists, region-specific guarantees, deeper isolation diagrams, or RFP responses — write to us and we will send you a current pack.

Request the trust packBack to overview