Skip to content

Enterprise

Assistants your security team can actually approve.

The blocker for AI in most organisations is not capability — it is that prompts and documents leave the building. deputyOS runs the assistant on infrastructure you control, with the evidence a procurement process asks for — and because we hold the signed image and encrypted state of every hosted device, those workloads move between your hardware and the cloud without reconfiguration.

Read this before you plan a rollout

deputyOS is at v0.3.0 — a public preview. There is no third-party security audit yet, no formal SLA, no SSO or SCIM, and no signed enterprise support contract. Organisations deploying it today are doing so with those gaps understood.

If you need those things before you can proceed, tell us which ones and on what timeline. That is genuinely more useful to us than a hypothetical roadmap, and it is how they get prioritised.

Managing more than one

Consumer appliance systems assume a single box. Past two or three machines that stops scaling, and most teams end up back at hypervisors plus configuration management. deputyOS treats the fleet as the unit from the start.

Three devices on separate networks — a Raspberry Pi behind home NAT, a mini-PC behind office NAT, and a cloud VPS — each hold an outbound tunnel to the deputyOS control plane, which a single console queries to manage all of them Home network · behind NAT Raspberry Pi 5 deputyd · agent running Office network · behind NAT Mini-PC deputyd · agent running Cloud VPS · public IP Hetzner CX22 deputyd · agent running outbound only — no ports forwarded api.deputyos.com tunnel relay · control plane console.deputyos.com one view · status, updates, spend
Each device opens the connection outward and holds it, so nothing needs forwarding at any of the three sites. Requests from the console travel back down a connection that already exists.
  • No inbound firewall changes. Devices connect outward, so a rollout does not require network exceptions at every site.
  • Staged updates. Push to a selection, verify, then widen. A failed update rolls back on the device without intervention.
  • Per-device cost visibility. Model spend is attributed per machine, so a runaway workload is obvious rather than a month-end surprise.
  • Portable workloads. A hosted device is a signed image plus an encrypted state backup, so it can be moved between your hardware and a cloud instance without reconfiguration — or rebuilt on replacement hardware in one command.
  • Allow-listed commands. Remote execution is constrained to a defined set and recorded with actor correlation — not a general remote shell.

Deployment patterns

Distributed workstations

One appliance per person or per team, managed centrally.

Each device holds an outbound tunnel, so nothing is forwarded at any site and remote workers need no VPN change. The console shows status, version and spend per device, and pushes updates to a selection.

Air-gapped / classified

Environments where no egress is permitted.

Built with AIRGAP=1, images carry the model weights and signature databases inside. Updates move as whole signed images on physical media, verified by signature before they are applied.

Cloud burst and migration

Capacity that moves, or sites being decommissioned.

Because a hosted device is defined by state we already hold rather than by its hardware, it can be migrated onto a cloud instance and managed from the same console — then moved back. Useful when hardware is being replaced or a site is closing.

On existing virtualisation

You already run Proxmox, TrueNAS or similar.

deputyOS runs as a guest with KVM acceleration, so your existing snapshot, backup and storage guarantees apply underneath while deputyOS handles the assistant layer above.

Regulated / evidence-led

You need to show an auditor what happened.

SBOM, signed provenance, CVE posture and queryable audit evidence are produced by the build and the runtime rather than reconstructed later.

Procurement questions

The questions that come up in every security review, answered directly.

Where does our data reside?
On hardware you control. Conversations, files, memory and provider keys never leave the device. Backups are encrypted client-side before upload, so any storage provider holds ciphertext only.
Can we run it with no internet access?
Yes. The air-gapped tier bakes model weights into the image and denies egress at nftables except RFC1918 and mDNS. It boots and works with the network cable out.
Do you have an SBOM?
Yes, CycloneDX, generated as part of the build rather than assembled afterwards. It covers the whole image, not just the application layer.
How do you handle CVEs?
CVE tracking enriched from OSV, NVD, CISA KEV and EPSS, matched against the SBOM so the question "does this affect us" is answerable in seconds rather than days.
What is the licence?
Apache-2.0. Commercial use, modification and redistribution are permitted, including in closed-source products, subject to the licence terms.
Can we verify what we deployed?
Builds are reproducible and every artefact ships a minisign signature and SLSA provenance. You can rebuild from source and compare hashes rather than trusting a description.
Is there an audit trail?
Audit batches are captured as compressed evidence and queryable with SQL, with compliance evidence export. Command execution is allow-listed and recorded with actor correlation.
What happens when a device fails?
Updates land in an inactive A/B slot with watchdog rollback, so a bad update reverts itself. For hosted devices we already hold a signed image and an encrypted state backup, so the device is reconstituted on replacement hardware — or on a cloud instance — in one command, resuming with its memory intact.
Can we move workloads between our hardware and the cloud?
Yes. Hosting is defined by us holding the device state, not by where it runs, so a hosted device can migrate from your hardware to a cloud instance and back without reconfiguration. That is useful for burst capacity, for sites you are decommissioning, and for keeping a service running while hardware is replaced.
How is this licensed per device?
There is no software licence to buy. Running deputyOS is free and unlimited under Apache-2.0, and every device is tracked in the console at no cost. You pay per hosted device — where we carry the managed tunnel, hold the encrypted backup and keep the state portable — which is a managed service rather than a licence. Enterprise negotiates that per-device rate and removes the volume ceiling.

Talk to us

Enterprise terms are negotiated rather than listed, because what organisations need varies enormously — some want support, some want the audit, some only need an invoice instead of a card.

Email enterprise@deputyos.com

It helps if you can include:

  • · Roughly how many devices, and where they sit
  • · Whether any need to be air-gapped
  • · Which compliance regime you report against, if any
  • · What would block approval today

A real person replies, usually within two working days. If deputyOS is the wrong fit for what you need, we would rather say so than sell you a preview.

Search

Search index isn't built yet. Run npm run build to generate it (Pagefind writes to dist/pagefind/).