Introducing enterprise inquiries: the honest version

The pricing page now has an Enterprise column. Here is exactly what it buys, what it doesn't, and what happens when you email us. It is written plainly, because the audience for this plan can smell filler.

There is now an Enterprise plan on the pricing page. Before anyone asks: no, we did not move features behind it. The detection surfaces (decoy identities, trap facts, the Shield firewall, honeypots, agent monitoring) work the same on every plan, audit logging starts on Shield as it always has, and only the limits change from there. That has been our pricing rule from the start and Enterprise doesn't break it.

What Enterprise actually buys is the operational wrapper that larger teams need before they can adopt anything: an SLA, negotiated capacity where the standard tiers don't fit, dedicated support, compliance documentation, a custom contract, and invoice billing instead of a card on file. It is listed at $120/month or $999/year as the anchor, and the honest description is 'Pro plus paperwork and promises in writing.'

Here is what happens when you send an enterprise inquiry: your email goes to the team that builds the product. There is no sales sequence, no SDR handoff, no mandatory discovery call. You will get a reply from someone who can actually answer questions about hash chains, data retention, and what the API does under a 402.

If you want a fast, useful exchange, include three things: which surfaces you care about, roughly what volumes you expect (documents, inspections per month, agents), and which compliance regime you're answering to, if any. That's enough for us to say yes, no, or 'here's the gap' in the first reply.

And what we won't promise, even for a contract: we won't claim the legal export PDF is court-admissible everywhere. It is tamper-evident, and admissibility is a question for your counsel in your jurisdiction. We won't claim out-of-the-box EU AI Act compliance: our audit records can feed an Article-12-style logging regime, but deployer-specific fields are yours to map. And we won't commit to shipping features that don't exist yet just to close a deal.

If that level of bluntness is what you were hoping an enterprise conversation would sound like, the address is hello@canaryvaults.com.

This article is about a shipped surface: All product surfaces. Integration details live in the docs.