Trust and security at Cadelic
What leaves your network in each deployment mode, where inference runs, how keys are handled, and where our compliance work currently stands. Stated plainly, with dates.
What we can see
Our position on data access is entirely defined by the deployment mode you choose. The default state for Orbit is that it runs on your hardware, and no data leaves your network unless you configure an external model provider.
Deployment modes and network boundaries
Local
Runs on a single machine you control. The ledger and graph are stored locally.
Text equivalent for screen readers
- ✓ Inference runs locally
- ✓ Zero outbound traffic
Private Cloud
Deployed in your own VPC. You control the infrastructure and the network rules.
Text equivalent for screen readers
- → Outbound: Configured APIs
- → Outbound: Optional telemetry
Cloud
Managed by us. Hosted on our infrastructure with strict isolation guarantees.
Text equivalent for screen readers
- → Outbound: Configured APIs
- → Storage: Managed instances
Local inference
Orbit can run inference entirely on your own hardware. If you supply a capable local model, no prompt or response ever crosses a network boundary.
The recommended minimum requirement for full agentic capability is 32GB of unified memory. Smaller models degrade the quality of the unprompted synthesis, though entity resolution and retrieval will continue to function on 16GB systems.
Bring your own keys
When you choose to use external model providers, you bring your own API keys. Keys are stored locally on your device in secure storage (or in your VPC's secrets manager) and are never sent to our servers.
A request sent to an external provider contains only the context necessary for that specific prompt. The full graph remains local.
Data handling and portability
Orbit does not hide your knowledge in a proprietary database. The graph and the ledger are stored as standard files on a disk you control.
Because the store is just files, retention, deletion, and export are operations you perform using standard filesystem tools. If you choose to stop using Orbit, your data remains exactly where it is, in a structured format you can read.
Compliance posture
We are building toward standard enterprise certifications. Our roadmap is stated plainly below, without inflation.
Sub-processors
Applicable only to the managed Cloud tier. If you run Orbit locally or in your VPC, we use no sub-processors for your data.
| Provider | Purpose | Location |
|---|---|---|
| AWS | Cloud infrastructure | EU / UK |
| Cloudflare Pages | Frontend hosting | Global edge |
| Postmark | Transactional email | US, Standard Contractual Clauses |
Security practices
We enforce multi-factor authentication across all internal systems. Code changes require peer review, and dependencies are automatically audited for known vulnerabilities.
We do not claim security certifications we do not hold, and we do not inflate basic hygiene into enterprise security features.
Responsible disclosure
We welcome reports from security researchers. If you find a vulnerability, please email us directly.
Contact: security@cadelic.com
We commit to acknowledging reports within 48 hours and providing timelines for remediation.