Start a trial · 14 days · no card
Create your vault, and start the record.
Two read-only connections and a sealed genesis receipt. From that moment your ledger runs on its own — every signal from Sentry, the signal source demonstrated end to end today, is sealed when it is scored, whether or not anything is ever attributed to it.
A vault belongs to an organisation, not a person, so the address has to be on your firm's domain — personal addresses are declined at this step. If an organisation has verified your domain with Déjà, you'll join it instead of creating a new one — directly, or through a join request its administrators approve; if several have, you choose which to ask. Standard and Charter hold one vault; on Enterprise and Sovereign an organisation can hold several — firms routinely keep one per legal entity, environment or jurisdiction — and each vault's incident receipts chain separately. On Déjà's managed key every vault signs with the same key; on Enterprise and Sovereign a vault can sign with its own KMS key.
You're creating a Standard trial vault — fully featured, no card, nothing to unwind if you walk away. The 14-day trial starts when you sign up. After the trial, Standard is $10,000 a month, or $120,000 a year.
Bring your audit firm in. Auditor invitations are unlimited on every tier, trial included, and never count as seats. The trial is far more useful with the people who'll read the evidence actually reading it.
Not signing up — just verifying? Checking a receipt someone sent you needs no account and nothing from us. Verify a receipt.
Create your vault
A work email, your name, and a 6-digit code — or continue with GitHub or Google Workspace. There is no password to choose.
Already have a vault? Sign in
Have these open before you start
01
Admin access to an error tracker
Enough rights to add an integration and enable issue events. Sentry is the source demonstrated end to end today.
02
Admin access to a change source
Rights to install a read-only app on the repositories you want watched. GitHub today.
03
The services you want covered
You'll group them into zones during setup — roughly one per service.
04
Fifteen minutes, uninterrupted
Most of it is waiting for OAuth screens.
What happens after you click
No agent, no library, nothing added to your codebase, and no change to how anyone handles an incident.
Step 01
You connect two sources
An error tracker for the signal side, a change source for the producer side, both read-only. Déjà reads events and each pull request's metadata and diff as it's opened, updated and merged, secrets scrubbed — never a file outside that diff.
~15 minutes
Step 02
Your genesis receipt is sealed
Signed at the end of setup, once your zones are locked, with your organisation and the time inside the signature. It signs the link after the governance receipts setup made, every later governance receipt chains behind it, and the ledger is append-only.
end of setup
Step 03
You send one real event
Trigger a genuine error from the vendor and confirm a receipt appears. A connector that says connected has not proven it delivers — this is the check that matters.
the step not to skip
Then
The ledger runs unattended
Each new signal from Sentry, the signal source demonstrated end to end today, is queued for scoring as it comes in and sealed when it is scored. Where the signal carries an affected field, changes in the lookback window are scored against it. Where it doesn't, the receipt records that scoring was never entered — either way there's a receipt. Datadog, Splunk On-Call and Alertmanager · Grafana alerts are scored too, but not yet demonstrated end to end, and a Datadog alert ends only in a no-attribution record (R1-N). Alerts from New Relic, Dynatrace, Honeycomb, AppDynamics and Splunk (alerts) are received but not scored yet, and get none.
And
Your auditor checks it without us
Export a bundle and hand it over. They run the open verifier on their own machine, against a published key, with no Déjà account and no call to our API.
About trial receipts
A trial receipt is not marked as one. It is produced by the same code, signed with the same vault key and verified by the same procedure as a production receipt, and nothing in it says which it is. We would rather tell you that here than have you discover it in front of an examiner.
The useful half is that a trial genuinely proves the mechanism: what you see working in your environment during the trial is what runs afterwards, because it is the same path. The half to plan around is that there is no cryptographic marker separating trial evidence from production evidence today, so treat the trial as a demonstration and agree with your auditor what counts as evidence before you rely on it.
We say this here rather than in a footnote because the whole product is an argument about not being asked to take things on faith — and that argument would not survive a page that described a watermark we do not apply.
What to expect, honestly
Two weeks is long enough to find out whether this works for you. It's also long enough to be disappointed by something we could have told you now.
Most receipts
Won't be attributions
Attribution covers three field-change patterns — a field removed, renamed or retyped. Timeouts, capacity, auth and logic bugs get a receipt recording the outcome, not a cause. That's the design, not a shortfall.
Coverage
Is narrower than the integrations list
One qualifying signal source is demonstrated end to end today, and Python is the demonstrated language. The status page is current and gets narrower as often as wider — read it before you start.
Cross-service
Isn't proven yet
Attribution between two teams' repositories is built and in validation. Until it's demonstrated we don't claim it, so don't design your pilot around it.
If self-serve isn't your route
Regulated firm with procurement
Vaults bound to your legal entity, SAML SSO, a designated contact and a security review before signature.
Book a call →Charter cohort
Founding customers get rate locked for life, direct roadmap input and a DSR working-group seat. Limited places.
Apply →Not ready
Send us the objection instead. We'd rather answer it than run a pilot that was never going to work.
Talk to us →