Shared Responsibility Model
Version 1.0 · Effective 2026-09-07
PlatformSmith is unusual among developer tools in one specific way: the containers that run your code run on infrastructure you own. We provide the control plane; you provide the compute.
That split is deliberate — your code and credentials never need to sit on our machines — but it means responsibility is genuinely shared, and being vague about the line would not serve either of us. This page draws it. It forms part of our terms of service.
The division
| Area | Ours | Yours |
|---|---|---|
| Control plane (API, web app, database) | Operate, patch, secure, back up | — |
| Controller and runtime software | Build, version, publish, document changes | Deploy it, keep it updated |
| The host it runs on | — | Provision, patch, secure, monitor, size |
| Network policy around your runtimes | Document what is needed | Configure and enforce it |
| Isolation from the rest of your estate | — | Yours: what your runtimes can reach is your network’s decision |
| Credential scope | Make scope visible; mint short-lived tokens where we can | Choose the scope. Decide what to connect and how narrowly |
| Reviewing what the agent does | Provide the controls | Use them |
| Session transcripts | Store, secure, delete on request | Decide what enters a session |
| Availability of your runtimes | — | Yours, since the host is yours |
| Availability of the control plane | Ours, on a best-effort basis — this is a free beta with no SLA | — |
What this means in practice
Your credentials are inside the agent’s blast radius. The Git token and the model key you connect are resolved into the runtime so the agent can use them. An agent that is manipulated by content it reads — see known limitations — is manipulated while holding those credentials. Everything you can do to narrow them narrows the worst case:
- install our Git application on specific repositories, not an entire organisation;
- use a dedicated service account rather than a personal one;
- do not connect production infrastructure credentials during the beta;
- rotate anything you think may have been exposed.
Your network is yours to segment. We do not currently constrain what a runtime can reach on your network. If your runtimes should not be able to reach your production databases, that is a control you place on your host, and we would encourage you to place it.
Your host is yours to size and watch. Runtimes consume CPU, memory, and disk on your machine. We do not currently set resource limits on them, so a heavy session competes with whatever else runs there. Do not run runtimes on a host that cannot afford to be busy.
Telling each other about problems
We will tell you if we become aware of a compromise or serious defect in our control plane or in the controller and runtime software you run.
Please tell us at security@platformsmith.com if you find a security problem in the Service, or if you believe a session on your infrastructure was compromised. We would much rather hear it from you early.
Changes
We may update this page; the version and effective date above identify the current version.