How SHIP fits into your organization
Read what SHIP runs today, what a cycle costs, and what stays under your control.
Which coding agents and models can SHIP run?
SHIP supports Claude Code, Codex, Pi, OpenCode, and Kilo Code as agent harnesses. For models, it supports OpenAI and Anthropic models, plus every model available through OpenRouter. You can assign a different harness and model to each role, from budget to frontier, without changing code.
Can I use my active subscription keys?
Yes, as long as your provider allows programmatic access with your subscription keys. SHIP orchestrates agents just like you do in your local environment. If you're able to use your keys for non-interactive sessions on your CLI, you're good to go. Subscription OAuth tokens typically have 1 year of lifetime.
Does any agent see my secrets?
No. Agents work in an isolated sandbox with scoped, per-task access. The platform holds your credentials and calls providers on the sandbox's behalf.
Does SHIP keep a copy of my code?
No. Your repository is cloned into an isolated, ephemeral sandbox that is destroyed when the run ends. SHIP keeps session logs of what each run did for observability, but not a copy of your repository.
What does a cycle cost?
It depends on the work and the models behind it. Every cycle reports its own cost, attributed by stage, priced on the model that actually served each request.
Do I need Linear?
Linear and GitHub are what SHIP connects to today. Work starts from an issue you assign and lands as a pull request in your repository.
Do I have to approve every change?
By default a human accepts the work at the end. Put a checkpoint at any stage, or let the loop ship without one.
What happens when an agent gets it wrong?
Review and test stages block the work, and the loop retries with that feedback. When it stops making progress, it stops and asks for you.
Can it run on my own cloud and CI?
Yes. Deploy and test run through your own SDLC, including the CI and deployment pipelines you already have. Inference runs on your own provider contracts. Agent execution runs in a secure sandbox, and the session data that powers your logs, metrics, and audit trail is held under SHIP's own security controls.
How is this different from a coding assistant?
An assistant helps an engineer write code. SHIP takes an assigned issue through plan, build, review, deploy, and test, then reports what it delivered and what it cost.
Ready to put the fleet to work?
Contact us for a demo with an expert.