Stackbone Cloud or your own infrastructure. Here is what we hold in each.

Where things run

Stackbone Cloud

Stackbone runs the runtime for you and stores what your agents process in its own infrastructure. Builder tokens are included in the plan; model calls at run time use your own gateway key or Stackbone’s gateway, billed by usage. Choose it when you want to start without running servers and nothing in your data or your contracts requires your own account.

Your own infrastructure

Agent runtimes deploy into your own AWS, Azure or GCP account, or run self-hosted or on-prem. The data your agents process never leaves your perimeter. It does not transit Stackbone, and we cannot read it.

Your model keys

Stackbone is model-agnostic. On your own infrastructure you bring your own provider keys, whether that is OpenAI, Anthropic, OpenRouter, an open-weights model you host yourself, or anything speaking an OpenAI-compatible API. We never proxy that model traffic through Stackbone accounts, and prompts and completions are not visible to us. On Stackbone Cloud, the plan’s builder tokens cover building. At run time your automations call models through your own gateway key, or through Stackbone’s gateway billed by usage; with Stackbone’s gateway, that model traffic passes through Stackbone.

Air-gappable by design

The self-hosted install runs the control plane and Studio inside your network, next to the agents, so Stackbone can be deployed in environments with no outbound internet access. This matters for defence, banking, healthcare and public sector work. Talk to us if that is your situation.

What Stackbone does hold

We are specific about this so you can scope your review properly. Our control plane holds account and organisation data (emails, names, sessions), each agent's identity (name and description), installation and deployment configuration (runtime URL, image tag), billing status and an audit log. When you run on your own infrastructure, it does not hold agent versions, execution records or the data your agents process.

On Stackbone Cloud, Stackbone also runs the runtime. Agent versions, execution records and the data your agents process sit in Stackbone’s infrastructure.

Platform security

• Encryption in transit. Stackbone's hosted dashboard, API and dev-tunnel endpoints are served over HTTPS. Runtimes you deploy in your own cloud or self-host serve plain HTTP inside your network; you terminate TLS at your own proxy or load balancer and register the runtime by its https:// address.
• Encryption at rest. Deployment signing secrets and token-signing keys are encrypted by the application before they are stored. On your own infrastructure, the data your agents process stays in your account, under the encryption you configure there.
• Secrets. Your agents' secrets live in the agent runtime, not in the control plane. The only secrets the control plane stores are each deployment's signing secrets, encrypted by the application and write-only: you can replace one, not read it back. On your own infrastructure the runtime is yours, so your agents' secrets never reach Stackbone.
• Isolation. Every deployable ships as a container. Tenants are isolated at the infrastructure level.
• Authentication. Product access uses passwordless email links, so there are no passwords to leak. SSO and SAML are available on request for enterprise plans.
• Authorisation. Role-based access control at the organisation level, so people only reach what their role allows.

How we operate

• Least privilege. Internal access is granted by role, reviewed periodically, and removed on the day someone leaves.
• Identity. Google Workspace is our identity provider, with mandatory two-factor authentication on every account.
• Change management. All code lives in a single repository. Every change goes through peer review and an automated pipeline before it can reach production.
• Monitoring. Infrastructure and application logs are centralised and retained, with alerting on anomalies.
• Backups. Control plane databases are backed up continuously with point-in-time recovery, and restores are tested.

Audit and governance

Regulated buyers do not just need agents that work. They need to prove what the agents did.

Your runtime records an execution trail: which version of which agent ran, on whose authority, against which configuration, with what outcome. On your own infrastructure, that record lives in your own database, not with Stackbone. On Stackbone Cloud, it lives in the runtime Stackbone runs for you.

Compliance

We are in a SOC 2 Type II programme, with ISO 27001 to follow. We operate under GDPR as a data processor for our customers.

If you are running a vendor security review and need our current status, our subprocessor list, our DPA or a completed questionnaire, write to [email protected] and we will send what we have.

Incident response

We have a documented process for detecting, containing and communicating security incidents. If an incident affects your data, we will notify you without undue delay and within the timeframes our agreements and the GDPR require.

If an incident is affecting you and you have not heard from us, write to [email protected] and say what you are seeing.

Reporting a vulnerability

If you have found a security issue, we want to hear about it. Our Vulnerability Disclosure Policy explains how to report it and what you can expect from us.

Contact

[email protected]