No SDR, no sequence, no discovery call.
Messages here are read by the people building the product. Send something specific and you'll get a specific answer — including “no, that isn't what this does,” which is usually the faster outcome for both of us.
Six routes, and two of them leave this page.
- routes
- six
- replies within
- two business days
- read by
- the team, not a queue
- Security or risk
Security review
Architecture pack and DPA, and where SOC 2 stands rather than a completed attestation we don't hold. Questionnaire responses and the control narrative: [Awaiting owner: whether SIG Lite, CAIQ and the control narrative exist as documents]
Use the form - Procurement
Enterprise or Sovereign
Multi-vault deployment, your own AWS KMS signing key, custom retention, contract terms. Tenancy is row-level in a shared database; a dedicated deployment: [Awaiting owner: whether a dedicated deployment is offered, and what it means]. Expect a security review before signature rather than after.
Use the form - Founding cohort
Charter application
Rate locked for life, direct roadmap input and a working-group seat, in exchange for running this against real audits and telling us what breaks.
Apply - Audit firm
Protocol and verification questions
How verification works, a test bundle to evaluate against, or a walkthrough before your first engagement. No sales process attached to any of it — and you never need an account.
Ask us - Researchers
Security disclosure
Vulnerability reports go straight to the security inbox and are acknowledged within one business day. We'd rather hear it from you than from a customer.
security@deja.dev - Anyone
Something here is wrong
A claim that doesn't match what you're seeing, a stale status row, a broken link. Corrections get published with the date they were wrong from.
Tell us
Already a customer with a live issue? Sign in and use in-product support — it reaches the same people with your vault context attached.
The more specific the question, the faster the answer.
Scoped requests get scoped responses. Concrete inputs mean we can reply with something usable instead of proposing a call to find out what you meant.
Your request
No sequences, no automation, no list. Your details are used to answer your question and nothing else — see the privacy policy. Replies within two business days, from a person.
Useful to include
- Trigger
- What prompted this — an exam finding, an audit cycle, an incident nobody could evidence afterwards
- Stack
- Your error tracker and change source. If they're not on the status page, say so now rather than after a trial
- Timing
- Your next audit or examination date — it usually determines whether this is worth starting
- Reader
- Who has to accept the evidence. If it's an external audit firm, bring them into the conversation early
- Objection
- The reason you think this won't work. Genuinely the most useful thing in any message we get
Prefer email?
Write to hello@deja.dev instead — read by the team, not routed through a sales tier.
hello@deja.devWhat you'll get, and won't.
- You'll get
A written answer first
Where a question can be answered in writing, it is. A call happens when it's genuinely faster for you, not as a gate on getting information.
- You'll get
A straight no when it fits
If your stack isn't supported, or the timing is wrong, or you'd be better served by an incident-management tool, you'll be told. That costs us a pipeline entry and saves you a quarter.
- You'll get
The current gap list
What isn't demonstrated, what isn't certified, and what we don't yet claim — before a trial rather than during one.
- You won't get
A nurture sequence
No drip campaign, no re-engagement emails, no list. One reply to your question, and nothing further unless you write back.
- You won't get
A qualification call
Nothing here is gated behind a discovery conversation. Public documents are public and linked directly on the security page.
- You won't get
A number we invented
No ROI model built from our assumptions. What this saves depends on your audit calendar and your architecture, and it's yours to measure.
One thing worth setting expectations on. Déjà is early and founder-led. The upside is that the person answering you can change the product; the cost is that we are not a hundred-person vendor with a completed attestation and a decade of uptime. Both are true and you should weigh both.