Where it runs
Almost every AI tool is a website you send your data to. DouJou is the opposite: it installs inside the cloud account your company already owns, so your information doesn't have to travel anywhere to be useful.
The difference that matters
This is the whole argument, and it’s an architectural one — not a promise in a contract.
Your data is sent to servers your company doesn’t own, sitting alongside other customers’ data, governed by a third party’s infrastructure decisions and retention policy — not yours. When you want to know what happened to it, you file a support ticket.
One dedicated instance, installed into the cloud account you already own, already pay for, and already audit. Your existing controls, logging, and network rules keep applying, because nothing moved.
What leaves your boundary
An AI model still has to be asked a question. The question that reaches it is the smallest, de-identified version of what was needed — never the underlying records.
How it gets there
You grant a role, and DouJou stands up your instance, verifies your AI access actually works before promising it does, generates the secrets, and confirms the deployment is healthy. Every installation is a custom fit to your environment, not a one-size-fits-all script — you get real attention on the deployment itself, not just the tooling behind it.
DouJou provisions into your own account on all three major clouds today — whichever one you already run on. The deployment is custom-fit to your environment, not a generic template.
Wherever DouJou itself runs, it can connect to and inventory resources across all three major clouds — plus your databases, document stores, and code repositories.
Those two are genuinely different things, and a lot of vendors blur them. Where the software runs and what it can see are separate questions — so we answer them separately.
Being precise about it
This is the part most vendors leave out. If you’re going to trust the claim, you should know exactly where its edges are.
The model call still goes to the AI service your company has chosen and configured. What changes is what reaches it— the de-identified minimum, never your records. If you want inference itself inside your own account, that’s a configuration to work through together, not something we’ll pretend is automatic.
Installing and updating DouJou means assuming a role you explicitly grant, and delivering our signed software image into your account — the same way any enterprise software vendor ships you a build. You can inspect that grant, and you can revoke it.
DouJou checks in periodically for licensing and updates. Plenty of vendors claim air-gapped operation; we don’t, because ours isn’t, and you’d find out during your security review anyway.
We’d rather be the vendor whose claims survive the review than the one whose claims got them into the review.
Why this isn’t just another badge
Certifications are worth having, and they matter. But they describe how carefully a vendor handles your data on their infrastructure. That’s a statement about someone else’s practices, audited once a year. Where the compute happens is a statement about physics — it either left your account or it didn’t, and you can check that yourself, today, in your own console.
Next step
The best way to trust this is to watch where it actually sits — inside a cloud account you already control.