Security by architecture.
The platform doesn't bolt security on after the fact. Cryptographic integrity, tenant isolation, and tamper detection are foundational properties of the protocol engine — not features added to a conventional application.
Tamper-Evident by Construction
Every protocol action is SHA-256 hashed with the previous action's hash. Modifying any historical event invalidates every subsequent hash in the chain — making tampering mathematically detectable, not just policy-prohibited.
Multi-Tenant Isolation
Protocol state, document storage, API keys, and user sessions are scoped to tenant ID at every layer. There is no shared state between institutions. Cross-tenant access is architecturally impossible, not just access-controlled.
Encryption at Rest and in Transit
All data is encrypted at rest with AES-256 via AWS-managed keys. All communication is encrypted in transit with TLS 1.2+. Documents are stored in S3 with server-side encryption. Protocol state is stored in DynamoDB with encryption enabled.
Least Privilege by Default
Four roles (admin, location admin, reviewer, operator) with granular permission groups. Actions are permission-gated at the protocol level, not just the UI level. The protocol rejects unauthorized actions before they enter the chain.
The hash chain is the security model.
Traditional audit logs are append-only by convention. The AVMS.AI protocol chain is append-only by cryptographic construction. Each action's hash incorporates the previous action's hash, creating a Merkle-like structure where any modification — insertion, deletion, or alteration of any historical event — invalidates every hash that follows.
Chain integrity verification runs across all protocol domains (sessions, policies, vendor management, QC, actors, tenant configuration, batch, SSO, exports) and reports per-domain status. A broken chain is immediately visible in the protocol log dashboard.
Individual actions can be exported as self-contained JSON proofs that an examiner or auditor can verify independently without platform access.
Your data. Your tenant. No exceptions.
All institution data — loan records, AVM documents, protocol state, compliance evidence, vendor analytics, and user accounts — is isolated to your tenant at every layer of the stack. There is no shared database, no aggregated analytics across tenants, and no data sharing of any kind.
We do not sell your data. We do not share your data. We do not use your data to train models. We do not provide your data to third parties. Your institution's compliance evidence is yours alone.
Enterprise identity. Enforced at every layer.
Authentication is powered by AWS Cognito with required MFA on all accounts. Enterprise SSO delegates authentication to your existing identity provider — Okta, Azure AD, PingFederate, or any SAML 2.0 provider.
Role-based access control is enforced at the protocol level, not just the UI. An operator cannot dispatch an admin-only action even if the UI were bypassed — the protocol orchestrator rejects unauthorized actions before they enter the chain.
Built on AWS. Managed with care.
Compute
Serverless and containerized execution. Ephemeral compute with no persistent attack surface. Horizontal autoscaling with zero standing infrastructure.
Storage
Single-table document store with partition-level tenant isolation and optimistic concurrency control. Object storage for content-addressed documents. Both encrypted at rest with AES-256.
Identity
Managed identity pools with required multi-factor authentication. Enterprise federation via SAML 2.0 with JIT provisioning and attribute-mapped role assignment.
Network
Edge-distributed content delivery with web application firewall. API gateway with per-key rate limiting and throttle enforcement. All traffic encrypted with TLS 1.2+.
Security questions? We welcome them.
If your security team needs additional detail beyond this page, contact us for a technical security review or to discuss your institution's specific requirements.