Thoria adds no new vendor to your stack.

The deployment

Thoria ships as a container image you run yourself, on your own servers or in your own cloud tenancy. Your administrators control where it runs, who can reach it, how it is backed up and how long records are kept. It sits inside your perimeter and behind your existing access controls.

The enterprise deployment is self-hosted by design, not by default. The records a firm seals are its own, held inside its own perimeter, and we do not intend to change that.

Where the models run

The image includes a local inference runtime. Work handled there runs on your hardware and transmits nothing.

Where Thoria calls a frontier model, it does so through an endpoint you configure, using your own credentials. Bedrock, Azure, a direct enterprise agreement with a lab, or another provider entirely. The point is that it is your provider: one you have already put through vendor review, already have terms with, and already send work to.

This is the part most firms expect to be a fight and find is not. Thoria does not ask you to accept a new processor, sign a new data agreement, or route work through a company you have not assessed. If you change providers, you change a configuration value.

Why that architecture, and not an easier one

It would be simpler for us to run inference through our own account and bill you for it. We do not, because the AI landscape is fragmented and getting more so. Firms use different models, at different intensities, under different agreements, and they change. An accountability layer that is tied to one provider inherits every one of those constraints.

Thoria is meant to be the constant. The models underneath will keep changing; what a named person understood and owned should be recorded the same way regardless.

What reaches Thoria, Inc.

Not your work. The enterprise deployment does not send us document content, agent transcripts, questions, answers, judgements or sealed records. There is no telemetry channel, no usage reporting and no backup that carries them to us. We could not produce your records if compelled, because we do not hold them.

If you want our help diagnosing something, you decide what to send and you send it deliberately.

Identity

A Thoria account authenticates through OAuth against your existing corporate identity provider. Your directory remains the authority on who someone is and whether they still work for you. That is not a convenience feature. A seal names a person, and an identity list that drifts from your directory is an identity list that can attribute ownership to someone who was no longer there. Revoking access in your directory revokes it in Thoria, in the same action.

The seal

Each sealed record is cryptographically signed and can be verified by a third party without access to the instance that produced it. A counterparty, a regulator or opposing counsel can confirm that a particular record was sealed, when, and by whom, without you granting them access to your systems and without the underlying work being disclosed.

That property is the reason Thoria is a company and not a feature. A firm attesting to its own diligence is marking its own homework. Verification that holds outside the organization requires a neutral party, and it is why the value compounds: the more organizations that seal with Thoria, the more seals are verifiable against a common standard.

At a glance

The legal position

Our privacy policy sets out what data exists and who controls it. Our terms set out the licence, what happens when it ends, and what a seal does and does not claim. Both are written to be read rather than skimmed.

Ask us anything

If your security review needs something that is not here, ask. We would rather answer a hard question than have you infer an answer.

Mark Kakoma, Chief Executive Officer — mkakoma@thoria.io
James Burnham, Chief Operating Officer — jburnham@thoria.io