The Lodestar Crucible
One sealed enclave that many parties plug into. Issuers, data owners, and counterparties each bring data in. None can read another's raw inputs, and Lodestar reads none of them. The protocol runs inside; only attested, policy-approved outputs return.
One enclave, every party
A rail that belongs to no one who plugs into it.
Private-market participants have conflicting interests, so a shared computation has to be neutral. The Crucible lets each party contribute data to the same sealed enclave without exposing it to the others — or to Lodestar.
Who plugs in
Different parties. Same neutral enclave.
Issuers
Connect Stripe, QuickBooks, Plaid, Gusto, and Carta directly into the enclave. The result becomes their Lodestar Verified Value.
Data owners
Bring reference or market data into the same neutral enclave. It informs the computation without being exposed to any other party.
Counterparties
Buyers, funds, or auditors run scenarios on materials they already control. Results are sealed to them; the official value is unaffected.
Auditors & counsel
Receive attestation logs and a signed, reproducible record — enough to rely on the output without ever touching the raw inputs.
Neutrality guarantees
Three things the rail guarantees.
The operator reads nothing
Lodestar computes on data it cannot read. Source-provider keys bind to the enclave hash, never to Lodestar's general infrastructure.
Tenants read nothing of each other
Each party is an isolated tenant. One party's raw inputs are never visible to another — only the policy-approved output crosses the boundary.
You verify before you connect
The enclave image hash is published. You confirm it matches Lodestar's code before any data flows. Big-4 third-party code review available on request.
How it works
Source in. Attested output out.
A single tenant's flow in detail: OAuth tokens bind to a verified AWS Nitro Enclave, the Lodestar Protocol runs inside, and only the attested result leaves.
Source providers
OAuth keys flow directly into the enclave.
- SStripe
- QBQuickBooks
- PPlaid
- GGusto
- CCarta
The Crucible
AWS Nitro Enclave
Protocol runtime
The Lodestar Protocol runs inside the enclave. Raw inputs never leave. Only policy-approved outputs return.
Attestation hash
a3f7b2d8c1e9...4f8a2c
Attested output
Cryptographically verifiable.
- Lodestar Verified ValueRange + base case
- Inputs hashSHA-256 of source-graded inputs
- Signed certificateBound to enclave attestation
- Outcome ledger entryImmutable, public
Default architecture.Alternative TEEs available for highest-stakes engagements: GCP Confidential Computing, Azure Confidential VMs, on-prem Intel SGX or AMD SEV.
Demo
Try a sample valuation
Adjust inputs and see how they affect the valuation range. (Illustrative — real runs happen inside the enclave.)
Inputs
Valuation Range
This is a simplified demo. Full engagements include comprehensive comparable analysis, scenario modeling, and methodology documentation.
Plug into the rail.
Whether you're an issuer connecting your systems, a data owner contributing reference data, or a counterparty running a sealed scenario — the Crucible is neutral infrastructure you compute on, not a party you have to trust blindly.