Skip to content
Cadelic

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.

POSITION

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.

Documents

Our formal Architecture & Security Overview and Data Processing Agreement are currently being written. To request the current drafts, please email [email protected].

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 using Orbit on local hardware or private cloud, you bring your own API keys. Keys are stored locally in secure storage and never sent to our servers. Support for bringing your own keys to the managed Cloud tier is planned.

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.

SOC 2 Type 1In build
SOC 2 Type 2Planned
ISO 27001Planned
GDPR compliance (Cookieless)Working

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.

ProviderPurposeLocation
AWSCloud infrastructureEU / UK
Cloudflare PagesFrontend hostingGlobal edge
PostmarkTransactional emailUS, 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: [email protected]

We commit to acknowledging reports within 48 hours and providing timelines for remediation.

Documents

Architecture and Security Overview

PDFIn buildPlanned

Data Processing Agreement

PDFIn buildPlanned

Security Questionnaire (CAIQ)

XLSXPre-filledPlanned