Nebula is the operating system for any work.
What it is, what stops being your job, what runs underneath, how it handles change, and what anyone outside the platform gets from it.
What it is
An operating system for any work.
Upload the documents that define what is being delivered (contracts, statements of work, project briefs, specifications, MSAs, design documents, whatever you have). Nebula reads them, learns the work, and orchestrates the execution. Both parties read from the same record.
The same shape carries a construction milestone, a supplier SLA, a procurement deliverable, a regulatory acknowledgement, an internal team sign-off. Domain packs (defence, infrastructure, commonwealth compliance) layer sector-specific conventions on top of the same core.
What stops being your job
Five things off your desk.
Enforcement is automatic.
Reminders and escalations run on the platform.
Both parties on one record. Reputation moves with delivery.
Variations and extensions adapt the record.
Every version preserved.
Slips surface here first.
What runs underneath
The work moves itself.
Once a project is on Nebula, the platform reads the document, brings both parties to agreement, drives item status against deadlines, lets the two parties co-evolve obligations as the work progresses, and anchors every trustworthy state change to a public chain. None of that requires a human to remember.
The deadline check runs every fifteen minutes. The reminder fires before something goes late. The escalation fires when something does. By the time the board asks for the audit trail, the export is ready.
A day on the platform
Ninety-six checks per project per day. Most pass silently; one fires (emerald) when something needs attention.
When work changes
Slips, revisions, disputes.
Slips lean on each other
A late milestone pushes the next one out. A missed approval blocks the deliverable that depends on it. The risks panel surfaces the exposure before the call from the client arrives.
Revisions preserve the original
When the agreement changes, the new version supersedes the old; the original is preserved in the audit trail. Every revision is signed by both parties before it takes effect.
Disputes converge
Counter-offers are bounded at three rounds, then escalate. The version in force today is always the one both parties signed.
Two chains, in parallel
Every state change writes to both. If either disagrees, the proof is rejected.
What anyone outside gets
Verifiable without an account.
Every state change worth anchoring is recorded to two independent chains in parallel: Polygon (public EVM) and Nebula’s own chain. Either side, or any third party, can verify a proof against either chain. A standalone CLI re-derives the result from public chain data alone.
Counterparty reputation is computed from those anchored events. Five dimensions score each organisation on what they delivered. The next buyer sees the record before they sign.
Trust on Nebula does not require trusting Nebula.
The company
Nebula Platform Pty Ltd.
ABN 51 667 540 025 · New South Wales
Australian company. Compute on Vercel pinned to Sydney; database on Neon in ap-southeast-2; object storage on Cloudflare R2 in the APAC group. Every API call, every scheduled job, every database query happens in Australia.
The long-form security and procurement detail lives on /security.
Talk to us
Tell us what you’re working on.
We respond within a business day. For procurement and security questionnaires, we share the SOC 2 controls matrix and the IRAP-aligned data-handling matrix under NDA.
Ready to see it? Sign up and upload a document.
Rolling Nebula across multiple teams? Talk to us about Enterprise.