We are early, and we would rather you heard it here.
Déjà is a small company building one thing: a record of what your systems reported and what changed, kept as it happens and checkable by someone who trusts neither you nor us. This page says who is building it, what we will and won't claim, and where the product actually stands.
What is implemented, and what is not claimed.
Last reviewed 2026-09-22. A row moves left only when something can be demonstrated, and rows have moved right before.
- Implemented
- 4
- In validation
- 2
- Not claimed
- 4
| Claim | Status | How you check it yourself |
|---|---|---|
| Signals from Sentry are sealed when they are scored | Implemented | Send a test event from Sentry during the trial and watch the ledger sequence advance. 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 every connected source get a receipt | Not claimed | Alerts from New Relic, Dynatrace, Honeycomb, AppDynamics and Splunk (alerts) are received but not scored yet, so they get no receipt, and whether PagerDuty, AWS CloudWatch, Azure Monitor, Google Cloud Monitoring, incident.io, Rootly and FireHydrant incidents reach scoring is still being checked. |
| Signed receipts verify offline against a published key | Implemented | Run the open CLI on an exported bundle, on a machine we don't control. |
| Scoring is deterministic with published thresholds | Implemented | Every attribution receipt carries its scoring version and score. |
| Exceptions are sealed, not discarded | Implemented | Look at the no-attribution and failed-resolution receipts in your own ledger. |
| Cross-service attribution between two teams' repositories | In validation | Not claimed until it is demonstrated. Ask for the current state before the trial. |
| Attribution outside Python | In validation | JavaScript and TypeScript are supported and not yet demonstrated by us. |
| Every receipt type carries an Ed25519 signature | Not claimed | The bundle states, per receipt, whether it is signed or content-hashed. |
| Issuance timestamps are anchored to an external time source | Not claimed | Issuance time is asserted by us today. If that matters to your control, raise it before the trial. |
| A completed third-party security attestation | Not claimed | In progress. [Awaiting owner: whether SIG Lite, CAIQ and the control narrative exist as documents] |
This table is maintained as the product changes. A row moves left only when something can be demonstrated, and rows have moved right before.
The request always arrives long after everyone stopped remembering.
Déjà came out of fifteen years in financial services, on the side of the desk that gets asked for the evidence. The pattern repeats with a consistency that stops being funny quite quickly: an examiner, an auditor or a client asks what happened on a given day, and the honest answer is that several systems each hold a fragment, none of them holds the relationship between the fragments, and the person who could have explained it left in March.
What gets produced instead is a reconstruction — assembled carefully, in good faith, by people reading their own logs after the fact. It is usually accurate. It is never independent, and everyone in the room knows it.
The record was never too hard to keep. It was only ever kept afterwards.
The gap isn't monitoring. Firms are extremely well monitored. Every vendor proves what happened inside itself, and does it well. The gap is that nothing owns the relationship between two vendors' systems — and the relationship is precisely what the question is about. Whose change, which service, at what time, and how do we know.
So Déjà does the narrow thing well rather than the broad thing approximately. It watches the systems that were already going to fire, writes what they said at the moment they said it, and hands the result to someone who can check it without asking us anything.
Three sentences that have to hold everywhere.
Every document we publish, every deck and every page of the product uses this model. When something we've written elsewhere contradicts it, this is the version that's right.
One
Every scored incident signal produces a sealed record.
Two
An eligible schema mutation produces a deterministic attribution attempt.
Three
Certain receipt types are additionally signed — Ed25519 on Déjà's managed key, RSA-PSS or ECDSA on a vault's own KMS key — and the bundle states which, per receipt.
"Sealed" and "signed" are not synonyms here and we don't use them as if they were. Sealing is what happens to everything; signing is a stronger property that applies to specific receipt types. Any sentence of ours that blurs the two is a mistake, and we'd like to know about it.
Rules we hold to when they cost us.
Narrowness up front
What Déjà cannot attribute is on the homepage, not in month two of the pilot. A buyer who finds out late is right to be annoyed; a buyer who knows first can decide.It reads, and says where it writes
Déjà approves nothing, blocks nothing and remediates nothing. It writes back in two places, and says so: an event into Honeycomb when an incident is resolved, and ServiceNow incidents if you turn on incident sync.Verifiable without us
If verification required calling our API, we'd be asking you to trust a company you're using precisely because you don't want to trust anyone's word.No borrowed credibility
No customer logos we haven't earned. An integration mark appears only beside the status we have measured for it — demonstrated end to end, or connects, with what it does today — and never as a partnership or an endorsement. No regulator's name implying an endorsement nobody gave.Exceptions are the product
The receipts where nothing was found are the ones that make the ledger a record of the period rather than a highlight reel. They are never counted or charged for.Your data isn't our material
Customer data is not used to train models, not sold, and not pooled across tenants. Déjà never clones your repositories. It reads each pull request's diff as it's opened, updated and merged, and keeps it, secrets scrubbed, as attribution evidence; it reads no file outside a pull request's diff.
Small on purpose, and not pretending otherwise.
Déjà is founder-led with a small engineering team and contract specialists brought in for adversarial testing — someone whose job is to try to break the product and report what they find, rather than to confirm it works.
The founder spent fifteen years in financial services across wealth management, banking and asset management, in roles where producing evidence for an examiner was somebody's actual Tuesday. The engineering questions Déjà answers are downstream of that: the product exists because the request kept arriving and the answer kept being a reconstruction.
Being this size has a cost and a benefit, and we'd rather state both. The cost is that we are not a hundred-person vendor with a completed attestation and a decade of uptime. The benefit is that when you find something wrong, you will be talking to the person who can fix it, and the fix will not wait for a quarterly planning cycle.
Company facts
- Legal
- Déjà, Inc. — Delaware C corporation
- Structure
- Founder-led, engineering team plus contract security and reliability specialists
- Funding
- Self-funded to date
- IP
- Patent applications pending on the schema deduction engine and the dual-layer ledger
- Standard
- DSR/1.0 — receipt and bundle format, published. Its verifier, dsr-verifier-cli, is publicly released at v1.7.2.
- Customers
- Charter programme open; no production customer deployments to reference yet
Things Déjà will not do, including for money.
Approve, block or remediate in your systems
No approvals, no automated remediation, no agent in your runtime — not as a roadmap item and not as an enterprise option. The writes Déjà does make are the two listed above, and neither changes how your code or your infrastructure runs.Claim to discharge a regulatory obligation
Déjà supplies a record. Determination, classification, filing and certification stay with your named accountable individuals, and any vendor telling you otherwise is selling you a problem rather than solving one.Rank guesses and call the result deterministic
Where confidence is below the threshold, the receipt says so instead of promoting the best available candidate. A number that is always produced is not a finding.Charge more for a bad quarter
No per-receipt billing and no overage. Standard and Charter include an allowance of attribution receipts that warns rather than blocks or bills. Pricing responds to scope — vaults, retention, key custody, support — and never to how many incidents your systems had.Make an auditor create an account
Verification runs on their machine with open tooling and a published key. The person checking the evidence should not have to enter a relationship with the company that produced it.Describe a connector as working before we've seen it work
The status page distinguishes demonstrated from supported from beta, per connector and per language, and it gets narrower as often as it gets wider.
The useful conversation starts with your objection.
If something on this site doesn't survive contact with your architecture, we'd rather hear it now than in month four of a pilot. Bring the security review, bring your audit firm, and bring the connector we haven't demonstrated yet.