The Lodestar Crucible
Source-provider keys flow into a sealed enclave. The Lodestar Protocol runs inside. Raw data never leaves; only attested, policy-approved outputs return.
How it works
Source providers in. Attested output out.
OAuth tokens are bound to a verified AWS Nitro Enclave. The Lodestar Protocol runs inside. Lodestar engineers never see the raw data — only the attested result.
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.
Inputs
Valuation Range
This is a simplified demo. Full engagements include comprehensive comparable analysis, scenario modeling, and methodology documentation.
Full Access
Request full Crucible access
The demo above is limited. Request access for the full Crucible experience.
Your Own Data
Upload your company's metrics and see how they compare.
Full Comparable Set
Access our full database of comparable transactions.
Scenario Builder
Model bull, base, and bear cases with custom assumptions.
Ready for the full experience?
Request full Crucible access to explore Lodestar with your own data.