Models and data
Your models, your data classes, your servers
You choose the model providers. Each model is cleared for a data class. Secrets are sealed at rest and every outbound request is checked against allowed hosts.
Data classes
Restricted data reaches only models cleared for it
You choose your model providers. Each model is cleared for a data class. The kernel checks the data in a request against the model before the call.
An agent does not pick where your data goes. The model it may use for a piece of work depends on what that work touches.
Clearances are set by people. A request that would send restricted data to a model not cleared for it is refused.
model clearance (example)
A hosted model
Cleared: Up to internal data · Asked for: Drafts, summaries, internal notes
A model on your own servers
Cleared: Up to restricted data · Asked for: Customer records with personal data
A hosted model
Cleared: Up to internal data · Asked for: Customer records with personal data
Secrets and egress
Keys stay in the kernel. Traffic goes where you allow.
01
Sealed secrets
Connection secrets are sealed at rest. Agents never hold your vendor keys.
02
No vendor keys in agents
Agents do not hold keys to your CRM, billing or email. The kernel runs the approved action with its own credentials.
03
Checked egress
Every outbound request is checked against the hosts you allow. Anything else is refused.
04
Your providers
You choose which model providers OrchKernel may call, and which data class each model may see.
05
Runs where your data lives
Self-hosted: one binary and one database file, on your own servers.
Self-hosting06
A kernel per tenant
Multi-tenant hosting, with a separate kernel for each tenant.
Tenancy and the licenseFrequently Asked Questions
Put an agent on real work, with people in charge
Design partners run one real workflow on OrchKernel and work directly with the engineers building it.
OrchKernel is source-available and self-hosted.