One reconciliation control plane. Clear operating boundaries.
The Falcon Veritas architecture connects source data, matching, human decisions and audit evidence. This page explains the intended deployment and control model for an enterprise evaluation; a customer's final configuration is agreed during scoping.
From sources to governed action
Source feeds enter ingestion and data preparation, where formats are normalized and quality rules are applied. Reconciliation definitions then combine exact keys, tolerances and reviewable AI assistance. Exceptions move into a human-controlled resolution path; decisions and evidence remain attributable.
SaaS and dedicated boundaries
The shared SaaS model separates customers through tenant-scoped identity, database policies and application controls. A dedicated or customer-VPC model is a deployment option to evaluate for contractual or sovereignty needs; it must not be read as an already-live region or an unconditional plan entitlement.
| Decision | Shared SaaS | Dedicated / VPC evaluation |
|---|---|---|
| Data boundary | Tenant-scoped logical isolation | Dedicated infrastructure subject to scope |
| Operations | FVI-managed platform | Jointly agreed responsibility model |
| Residency | Pinned to the contracted home region | Region and control boundary assessed per customer |
| Keys and network | Managed service controls | Customer-specific key and network design where contracted |
Shared responsibility
Falcon Veritas owns platform code, change control and service operations within the contracted boundary. Customer administrators own their user lifecycle, role assignments, approved connections and data supplied to the service. Underlying cloud providers operate their managed infrastructure. The exact division belongs in the order form and security schedule.
Read the Security overview for control categories and current evidence limits.
Regional cells and change promotion
The intended model pins a tenant's authentication, primary database, storage and consistent reads to its contracted home cell. Availability of a particular cell is confirmed in the order form and due-diligence materials, not assumed from a marketing map. Cross-cell movement requires an approved data-transfer design.
Development, UAT and Production changes are intended to move through reviewed packages, maker–checker approval and environment-specific evidence. The current release state and any unhosted controls must be confirmed in a due-diligence review rather than inferred from this architecture.
Discuss a scoped evaluation with the Falcon Veritas team. Product outcomes and commercial commitments are agreed for each engagement.
Book a 30-min demo