Tenant isolation
Client records, mappings, users, thresholds, endpoints, credentials and model artifacts remain inside the approved tenant boundary.
Security and deployment
Client data is isolated. Access and authority are explicit. Every model output, approval and external action can be traced to the version and evidence that produced it.
Explicit authority
Authentication, authorisation, approval boundaries and side-effect permissions are enforced at the service and adapter boundaries.
Controlled data path
Source authority, provenance, freshness, conflicts and classification travel with evidence through the decision path.
Durable audit
Decisions, model versions, approvals, intents, completions and outcomes retain replayable lineage.
Hosting and data protection.
| Dedicated environment | Each Fable-managed deployment runs in its own AWS account. We can also deploy into your own infrastructure. |
| Data residency | You choose the region, with London as the default for UK clients. Your data stays there. |
| Encryption | Encrypted at rest with keys used only for your deployment and rotated automatically. Encrypted in transit over TLS 1.2 or 1.3. |
| Record isolation | Database-level controls keep every record inside your deployment. |
| Network protection | A web application firewall with managed rules and rate limits sits in front of every service. |
| Monitoring | Audit logging, threat detection and configuration monitoring run across every deployment. |
| Backups and recovery | Point-in-time recovery for 35 days. We aim to lose no more than 15 minutes of data and to restore service within four hours. |
| Software releases | Every release is scanned for vulnerabilities, shipped with a software bill of materials and signed before it is deployed. |
| Support access | Our staff need multi-factor authentication and sign-off from a second person to access your deployment, and that access expires within eight hours. |
| Roles | Administrator, operator and viewer roles. Queuing, cancelling and carrying out actions are separate permissions. |
The client defines the deployment boundary.
| Reusable software | Versioned engine code and contracts remain separate from client records and configuration. |
| Client environment | Contains source connections, identity mappings, roles, permissions, approved model artifacts and deployment settings. |
| External actions | Every permitted write requires a named adapter, permission, approval rule and duplicate-prevention contract. |
| Models | Artifacts are versioned, scoped, monitored and expired explicitly, with a declared fallback. |
Evidence for procurement and technical review.
- System architecture, data flows, trust boundaries and service ownership.
- Access, secrets, dependencies, vulnerabilities, backup, recovery and change controls for the deployment.
- Model approval, scope, monitoring, fallback, replay and outcome records.
- Client-specific requirements and accepted exceptions, each with a named owner.
Define the security boundary before implementation.
Bring the hosting, access, integration and procurement requirements that govern the decision and its data.
Book a live walkthrough