How Onwinds works

From signed intent to verifiable financial result in one pass

Onwinds has one job: take a transaction request from a user, system or an AI agent and turn it into a financial fact you can trust. Every change follows the same path: a signed intent comes in, policies are applied once, the ledger commits balanced postings, evidence is attached, and projections update in real time. No side writes, no hidden batches, no mysterious spreadsheets.

Contact sales Launch app

Lifecycle clarity

From intent to committed truth in one pass

Instead of dozens of flows and ad-hoc scripts, Onwinds makes one pattern the default. Whether it is a payment, a portfolio rebalance or a treasury move, the same five steps apply.

Under the hood

The kernel parts that make this work

Signed intents, immutable events, evidence binding and real-time projections remove the grey areas from finance infrastructure.

Signed Intent API

What it is

A single “execute intent” endpoint where every request is signed, typed and traceable.

What it does

Accepts JSON payloads that match schemas for each intent type
Uses cryptographic signatures (for example JSON Web Signature) to prove who sent it
Carries snapshot identifiers so valuations can be reproduced later

Why you care

Easy to integrate from apps and agent frameworks
Every state change has a clear origin and a stable identifier

Immutable ledger with financial invariants

What it is

An append-only, hash-linked event log plus postings that enforce double-entry accounting.

What it does

Stores every event with a payload hash and a previous hash
Enforces non-negative amounts per leg and balanced debits/credits
Records economic date and commit time in Coordinated Universal Time

Why you care

Replay any period and reproduce balances bit for bit
Attempts to tamper with history are visible immediately

Evidence vault and anchoring

What it is

Write-once storage for every context item that matters, with optional anchoring for public or cross-party proof.

What it does

Stores content-addressed bundles of documents, approvals and model outputs
Links evidence hashes to ledger events
Periodically computes Merkle roots and, if configured, anchors those roots to external chains

Why you care

Audits and investigations ship with ready-made packs
You can prove nothing was silently changed, even to external parties

Snapshots for valuations

What it is

Immutable reference data snapshots for FX, market data, calendars and configuration.

What it does

Each valuation cites a snapshot identifier
Snapshots never change; new versions get new IDs
Replays reuse the same snapshots that were in effect at the time

Why you care

Reports regenerate exactly as they looked then
No “future-peeking” when replaying old decisions

Real-time projections and streams

What it is

A projection layer that turns low-level events into fast, queryable views.

What it does

Maintains balances, positions and statements with read-your-writes behaviour
Streams events so other systems can react without building their own ledgers
Supports high-throughput replays to catch projections up or bring new regions online

Why you care

Products stay responsive without dual writes
If something breaks you rebuild from events—not ad-hoc fixes

Governance and safeguards

What it is

Policies and guardrails that keep agents, people and systems within safe boundaries.

What it does

Policies decide who can act, when approvals are needed, and which limits apply
Typed reason codes explain every approval or block
Tenant isolation, security logging and observability are built-in

Why you care

You can answer the board’s questions about trust and control
Controls are enforced by the platform, not left to tribal knowledge or spreadsheets

Outcomes

One core, different wins for each team

Everyone touches the same ledger, but each role benefits differently. Here is what changes when intents, evidence and projections live in one place.

For CEOs and founders

Launch new products and markets without rebuilding your system of record
Know that every euro, dollar or token is backed by evidence you can show to regulators and partners
Separate the experimental edge from a core that does not compromise on accuracy or proof

For product leaders

Express new financial flows as intents instead of projects to “fix the core”
Build hyper-personalised journeys and embedded finance while relying on a single ledger underneath
Use deterministic outcomes and clear reason codes to keep AI-driven features predictable

For developers and architects

Integrate via a small, typed surface: execute intents, read projections, stream events, manage evidence and snapshots
Avoid dual writes, cron jobs and fragile reconciliations—zero-batch by design
Use SDKs and tooling to sign intents, run local sandboxes and replay production ranges safely

Get started

Ready to give your customers intelligent finance on a core you can trust

Give your users and agents a real-time, multi-asset ledger where balances update instantly and evidence never goes missing. Launch new products without batch jobs and pass audits with confidence.

Talk to sales Launch app

Loading the kernel surface…

How Onwinds works

From signed intent to verifiable financial result in one pass

How Onwinds works

From intent to committed truth in one pass

Step 01. Request: Single endpoint for every signed intent.

Step 02. Validate: Policies and checks applied once.

Step 03. Commit: Balanced, hash-linked ledger commits.

Step 04. Evidence: Evidence bundles stay attached.

Step 05. Sync: Events drive projections and streams.

The kernel parts that make this work

Signed Intent API

Immutable ledger with financial invariants

Evidence vault and anchoring

Snapshots for valuations

Real-time projections and streams

Governance and safeguards

One core, different wins for each team

For CEOs and founders

For product leaders

For developers and architects

Ready to give your customers intelligent finance on a core you can trust

How Onwinds works

From intent to committed truth in one pass

Step 01. Request: Single endpoint for every signed intent.

Step 02. Validate: Policies and checks applied once.

Step 03. Commit: Balanced, hash-linked ledger commits.

Step 04. Evidence: Evidence bundles stay attached.

Step 05. Sync: Events drive projections and streams.

The kernel parts that make this work

Signed Intent API

Immutable ledger with financial invariants

Evidence vault and anchoring

Snapshots for valuations

Real-time projections and streams

Governance and safeguards

One core, different wins for each team

For CEOs and founders

For product leaders

For developers and architects

Ready to give your customers intelligent finance on a core you can trust