Security & Data
Industrial control code is sensitive. Daritas is built so you never have to upload source to a cloud you don't control, and so the knowledge you gain stays yours.
Your source stays on your floor
The engine runs inside your own network and ingests your source where it lives. The deep reading uses an AI — your own local model, your API key over a single controlled connection, or (for fully air-gapped sites) the deterministic engine alone, with the reduced depth honestly marked. Everything you receive works air-gapped forever. You decide what, if anything, leaves the premises.
Bring your own AI
Where AI assists — condensing logic, drafting prose — it can run against a model you provide. You are not forced to send source to any particular AI provider; the pipeline is designed so the sensitive reading step stays under your control.
Evidence, not opinion
Every statement in a model is bound to a verbatim source quote, and a proposed statement whose quote is not found in the source is rejected before it is stored. The deliverable is grounded and checkable — not an opaque summary you have to take on faith.
You own the model
Your model exports to an open, documented format that is dependency-free and readable without us. The knowledge is a durable asset you keep, not a rental that disappears if you stop subscribing. See The Model & Evidence.
IP protection
When work does involve our reviewers, options exist to reduce how much of your source is exposed — so a sensitive system can be understood without handing over more than necessary. For the most critical systems, you can remove external exposure entirely by verifying with your own engineers (below).
Your reviewers, no external eyes
For critical systems you can staff verification with your own engineers — employees or trusted contractors — on Daritas’s rails, so the model is reviewed with no external eyes at all. See Verification & Sign-off.
Isolation in the cloud
When you do use the cloud app, your data is isolated:
- Each organization’s model is locked to that organization; access is by invitation.
- The model tables are protected at the database level, reachable only by the server after an authorization check — never directly by other tenants.
- API keys are stored hashed and scoped to a single organization.