The Platform
The only data layer built for RWA ownership compliance
How OpenAssets normalizes, reconciles, and delivers institutional-grade ownership records.
How It Works
Four layers, one coherent ownership record
Multi-source ingestion
Connect to any custodian data feed: CSV exports, SWIFT messages, FIX protocol feeds, API endpoints, and proprietary custodian formats. OpenAssets parses and accepts them all without custom coding.
Normalization engine
Incoming ownership records are mapped to a single canonical schema. Asset identifiers, counterparty fields, and position quantities are standardized regardless of how each source formatted them.
Reconciliation logic
Position records from different sources are automatically matched against each other. Discrepancies are flagged with the two conflicting values, the source of each, and the time the divergence appeared.
Compliance output layer
Reconciled records are structured for regulatory reporting. Export packages pre-formatted for SEC 17a-4, GLBA data subject requests, and CFTC reporting are generated from the same canonical record.
The Data Model
Three-tier pipeline from raw feed to compliant record
Every ownership record moves through three distinct processing tiers. The model is designed so each tier produces a fully auditable output that serves as input to the next.
- 1. Ingestion tier: raw ownership data arrives from multiple custodian feeds. Formats parsed, schemas detected, timestamps normalized to UTC.
- 2. Normalization core: a single canonical ownership schema applies across all sources. Cross-source discrepancies are computed and surfaced as exceptions.
- 3. Output tier: compliance reports, dashboard data, and API responses all read from the same reconciled canonical record. No downstream transformation required.
Integrations
Connects to the feeds you already have
No middleware required. OpenAssets reads the formats your custodians already send.
Security and Data Handling
Institutional-grade security, not enterprise theater
We describe what we actually do, not certifications we plan to pursue.
Encryption at rest and in transit
All data stored with AES-256 encryption. All data in transit over TLS 1.3. Encryption keys are customer-scoped and rotated on a defined schedule.
Role-based access control
Every user action is scoped by role. Back-office staff see what their role allows. Compliance officers have read access to audit logs. Admin users control provisioning. No horizontal access by default.
Immutable audit trail
Every ownership event, reconciliation action, and exception resolution is written to an append-only log. No record can be edited or deleted after it is committed. Log entries carry timestamp, user ID, and action context.
Data residency options
Reconcile-tier and Institutional customers can specify data residency region. Ownership records remain in the agreed region and do not traverse to other infrastructure without explicit consent.
See the platform in context
Request a walkthrough and we will walk through how it handles your specific feed formats and asset classes.