Hosted when the bottleneck isn't belief,
it's bandwidth.
threep.cloud is for teams that want the evidence-backed workflow of threep.ai, but do not have the time or internal capacity to run the stack themselves. Same discipline, less operational drag.
Answers grounded in your documents. Gaps stated plainly.
No self-hosting required.
For teams short on time, not standards.
threep.ai is the open-source, local-first path. For some teams, that is exactly the right fit.
But not every team wants another deployment to own. threep.cloud exists for teams that want the same evidence-backed method in a managed environment, so they can focus on questionnaires, assessments, and remediation instead of infrastructure.
The operating model changes. The discipline does not.
Less setup. Less upkeep.
Same evidence.
threep.cloud removes the operational surface area so your team can focus on the compliance work, not the platform underneath it.
Skip the upkeep
Don't spend cycles on deployment, updates, model plumbing, or runtime babysitting. We handle it.
Get to usable evidence faster
Move from documents to defensible answers, visible gaps, and working assessments without standing up the stack first.
Adopt the workflow without owning the system
Use the method with less internal setup, less dependency on one technical owner, and less operational drag.
Keep the signal
Hosted changes the environment, not the product philosophy. threep.cloud is still built around evidence discipline and honest uncertainty.
The operating model changes.
The discipline does not.
threep.cloud runs on the same principles as threep.ai. The evidence discipline is not a feature of self-hosting — it transfers to the managed environment intact.
threep only cites what exists in your uploaded documents. No confabulation from training data, no generic fallback text.
Every YES or PARTIAL answer includes a pointer to the document, section, and excerpt that supports it. Traceable. Auditable. Defensible.
If your documents don't cover a control, threep says PARTIAL or NONE — not YES. Gaps surface here, not at audit time.
Assessment results are meant to be reviewed, challenged, and improved — not accepted blindly. A starting point, not a rubber stamp.
Choose the deployment model
that fits your trust boundary.
Local-first, self-hosted
The open-source path for teams that want to run everything in their own environment. Full control. No external dependencies. Everything stays on your infrastructure.
Managed, no self-hosting
The managed path for teams that want the workflow without owning the stack. Less setup, less upkeep, less operational drag. The evidence discipline remains intact.
Same evidence discipline. Different operating model.
Join the early access waitlist.
threep.cloud is in active development. Sign up to hear when early access opens and help shape the hosted experience.
You're on the list.
We'll be in touch when early access opens. In the meantime, threep.ai is open source and available today.
Explore threep.ai →Prefer to run it yourself?
threep.ai remains fully open source and local-first. If self-hosting fits your team, start there. If the blocker is bandwidth, threep.cloud is the shorter path. Same evidence discipline either way.