Technology

Le stack — sous le capot.

One platform, six layers

1. Banking layer — chartered banking through SF Private Bank. System of record for the regulated-banking activity.
2. Payments rails — Osage Pay infrastructure. SWIFT / SEPA / Fedwire / CHIPS / FedNow / ISO 20022.
3. Settlement layer — on-chain anchoring to Osage Network via SettlementRegistry. Content-addressed, post-quantum-secure audit trail.
4. Cryptography — the Osage post-quantum stack (Quasar, Pulsar, Magnetar, Prism, Corona) over NIST FIPS 203/204/205 primitives. HSM-backed key management via Osage KMS.
5. Data layer — SQLite via Osage Base for OLTP, with the CEK envelope on every sensitive column. Litestream for durable replication. ClickHouse for analytics + o11y; analytics never sees plaintext sensitive columns.
6. Identity — Osage IAM at iam.osage.id. One sign-in at osage.id across every product.

Cloud substrate

Osage Finance applications run on Osage Cloud — the sovereign cloud platform of the Osage ecosystem. Single Go binary serves the API; multi-tenant with external IAM; air-gap capable for IC and Treasury-side deploys.

Network & settlement

Every payment, bank-rail or on-chain, is anchored to Osage Network via a content-addressed hash recorded in the SettlementRegistry contract. Immutable, post-quantum-secure audit trail for every transaction. Block explorer at explorer.osage.network.

Why one stack instead of stitched vendors

• One ledger of record. No reconciliation drift between bank, processor, custodian, and audit.
• One audit boundary. Every data-access event is a KMS unwrap; the KMS log is the auditable record.
• One signing posture. High-value flows route through Pulsar threshold, not single-key custody. No vendor with unilateral key control.
• One crypto policy. Post-quantum agility is a config flip across the whole stack, not a multi-vendor migration project.
• One sovereignty story. The whole stack runs air-gapped or on-prem if the customer requires it.

Developer surface

• REST + WebSocket APIs; ISO 20022 messaging on the banking-rail side.
• SDKs in TypeScript, Python, Go, Rust.
• Documentation: docs.osage.finance.
• Storage / encryption spec: osage.tech/docs/storage.
• Cryptographic primitives: osage.cloud/crypto.

Built on open-source infrastructure. Banking is provided by SF Private Bank under standing partnership.