Technology
Built for institutional use, with clear boundaries and verifiable behavior.
This platform is designed as a capital intelligence and classification layer, not a black-box accounting system. The architecture favors transparency, composability, and operational control — so enterprise users can understand where data lives, how it is secured, and what the system does — and does not — enforce.
Architecture Principles
Contract-centric data model
All capital is modeled from legally binding instruments (contracts). Classifications, attributions, and views are layered on top, preserving historical integrity and auditability.
Separation of truth and presentation
Economic facts (contracts and attributions) are stored independently of organizational views (portfolios, reports). This prevents reclassification from mutating history and supports parallel reporting frameworks.
Deterministic behavior
No implicit balancing, auto-normalization, or hidden enforcement of totals. All calculations are explicit, inspectable, and reproducible.
Data Locality & Transparency
Explicit region selection
Tenants explicitly choose their data hosting region at onboarding. Data residency is deterministic and inspectable at the tenant level.
No silent data movement
Tenant data is not replicated across regions or environments without configuration and intent.
Clear data ownership
Clients retain ownership of their data. The platform does not repurpose or monetize tenant data.
Identity, Access & SSO
Enterprise authentication
Tenant-scoped identity model
Users are represented in the platform’s own database, enabling consistent authorization even if the external identity provider is temporarily unavailable.
Fine-grained authorization
Access control is applied at the project and object level. Authorization models are portable and not locked to an external vendor’s RBAC semantics.
SSO redundancy
Authentication and authorization are decoupled so identity provider outages do not corrupt authorization state or historical data.
Availability & Reliability
Stateless application layer
Application services are horizontally scalable and replaceable without data loss.
Point-in-time recovery and hot replicas in distinct Availability Zones
Preparedness for high-sigma tail risks.
Operational isolation
Tenants are isolated at the data and execution level to prevent cross-tenant impact.
Security
Encryption
- Data encrypted at rest
- Data encrypted in transit (TLS)
Least-privilege access
Internal services operate with scoped credentials and minimal permissions.
Auditability by design
Changes are traceable over time. Historical states are preserved.
No implicit automation
System does not autonomously reclassify or reinterpret capital without explicit user action.
Integration & Extensibility
The platform integrates into existing enterprise stacks rather than attempting to replace them.
API-first design
All core functionality is accessible via documented APIs, enabling integration with:
- Core banking systems
- Fund accounting platforms
- Data warehouses
- Regulatory reporting pipelines
Composable, not prescriptive
We built our architecture to be modular. You can plug us into valid data sources regardless of their origin, and we respect the downstream systems that depend on your data.
Client-Hosted Data & Key Ownership
Optional Deployment Model
For regulated Clients with heightened data-custody requirements, Enverium supports an external data plane deployment model in which client data and cryptographic material remain fully under the client’s control, while Enverium operates the application layer.
Core Principles
- Customer owns the database. Data is stored in a client-managed AWS RDS Aurora database, within the client’s AWS account and security perimeter.
- Customer owns encryption keys. All encryption at rest is performed using client-managed AWS KMS keys. Keys are non-exportable and governed by client-defined IAM policies.
- Enverium operates a constrained application runtime, also hosted at AWS. Enverium’s application is granted least-privilege, auditable access to the client’s database solely to perform authorized application workflows.
- No shared data custody. Enverium does not control database administration, backup policies, or key management for client-hosted data.
Network & Access Controls
- Private connectivity between Enverium’s application runtime and the client’s database (e.g. VPC peering or AWS PrivateLink).
- No public internet exposure of the database.
- Authentication via IAM-based database access or mutually authenticated TLS.
- No standing administrative database privileges in production.
Logging & Auditability
Database-level logging (client)
Connection and query audit logs are generated and retained within the client environment, providing authoritative evidence of data access.
Application-level semantic logging
Enverium logs user-initiated actions (read, write, update, export) with associated context, supporting operational transparency and internal reviews.
This deployment option is designed to
- Reduce vendor data custody and key-management risk.
- Support internal bank risk assessments for tier-3 confidential data.
- Enable client-controlled retention, access review, and forensic analysis.
Availability
This model is available by arrangement for clients with regulatory or internal governance requirements that warrant client-hosted data and key ownership.
What This Platform Is — and Is Not
It is
- A capital classification and attribution system
- A transparent layer for ESG, impact, and policy alignment
- A system of record for capital intent and meaning
It is not
- A general ledger
- A fund accounting system
- A substitute for custody, NAV calculation, or statutory reporting
Designed for Change
Regulatory definitions, taxonomies, and internal policies evolve. The platform is designed to absorb change without rewriting history, allowing institutions to apply new frameworks to existing capital data.