Features
What runs on Nebula.
The seven engines and the cross-cutting modules. Code-level detail lives in the docs.
01 · The seven engines
Real moving parts.
07 entries
- 01
Extract
Reads the agreement and pulls every commitment out of the text, each grounded to its clause. The same document parsed twice produces the same commitments, both times.
- 02
Accept
Walks both parties through review. Once both sign, the agreement is locked and the wording cannot quietly change.
- 03
Enforce
Runs every fifteen minutes, around the clock. Watches every deadline. Sends reminders before things go late and escalates when they do.
- 04
Adapt
Handles changes after the agreement is locked. Variations, deadline extensions, scope shifts: each one tracked, each one signed.
- 05
Prove
Records the important state changes to two independent chains. The proof is reproducible: anyone can verify the same hash from the same data.
- 06
Verify
Lets a counterparty confirm a claim is real without a Nebula account. The check uses public chain data; Nebula cannot fake it.
- 07
Certify
Builds a reliability score for every party from anchored events alone. Self-reported claims do not contribute.
Every result can be re-derived from public chain data alone, by anyone.
02 · Cross-cutting
Everything else the work needs.
Scheduling
Critical path, recalculated.
Every commitment has a duration and dependencies. Slack, critical path, and risk update inline whenever the work moves.
Read moreEarned value
Standard EVM, kept current.
Schedule variance, cost variance, the four indices, completion estimates. Recomputed every fifteen minutes from live state.
Track record
What every party did.
Reliability built from anchored events. Either party can pull the record, anyone can verify it, no Nebula API required.
Read moreMarketplace
Suppliers and tenders, scored.
Capability fit, certification fit, region match, project value. Track records render inline so reliability is visible before the tender.
Read moreCommunications
Quick messages, formal notices.
Two channels, both audited. Notices reference the clause they invoke; acknowledgements land in the audit trail.
Industry packs
Defence, commonwealth, infrastructure.
Per-sector validators and conventions on the same engine. Classification gating, AG approval thresholds, EOTs as first-class commitments.
Read moreTwo-chain proofs
Two independent chains, in parallel.
Every state change is anchored to two independent chains, so neither can rewrite history. The result is reproducible from public data alone, with no Nebula account.
Read more
Sign up and upload a document.
Rolling Nebula across multiple teams? Talk to us about Enterprise.