Step 1
Describe the idea in an issue
Write it as an issue in your tracker, or ask an assistant connected to SHIP to file it. The Planner writes a plan with acceptance criteria before the Builder starts.
Governed prototyping
Early accessLet anyone build a prototype that engineering reviews and merges
Product, design or operations describe an idea, and SHIP builds a prototype that runs on a preview. Each build runs in a sandbox, and the Reviewer checks it against your rules.
- For
- Founders and engineering leads whose product and design teammates already vibe code.
- Instead of
- Prototypes built in tools outside your review and deploy pipeline.
Runs today: Hand an issue to SHIP from Linear or GitHub Issues. Each build runs in a sandbox, and the Reviewer checks it against your rules. Your own pipeline deploys the preview, and SHIP logs every run.
Answer 4 questions. SHIP emails you when it opens to you.
agents: planner: checkpoint: true reviewer: checkpoint: trueHow it works
Turn an idea into a prototype engineering can merge
Step 2
Get it built and checked in a sandbox
The Builder works in an isolated sandbox. The Reviewer checks the change against your repository's conventions, and the Tester tries the prototype on a preview.
Step 3
Merge the prototypes you want to keep
Every prototype is a pull request. Engineering merges the prototypes it wants to keep, after the same review as any other change.
Capabilities
Decide what runs and what merges
Run every build in an isolated sandbox
Agents never see your keys. SHIP holds them, adds them to each request that leaves the sandbox, and gives every task short-lived access to only what it needs.
Block CI changes nobody asked for
SHIP blocks any change to your CI configuration unless a person asked for it. Checkpoints can also pause a run after the plan or the review.
Review against your own rules
The Reviewer and Tester read their instructions from your repository's base branch. A prototype cannot change the rules that SHIP uses to check it.
Deploy only through your pipeline
Your own delivery pipeline deploys each preview with your own secrets. A prototype only goes where your pipeline would put any other change.
Read what every agent did
Each run keeps a session log of what every agent read, ran and decided. You have the record before anyone asks for it.
Cap what a prototype can spend
A mission pauses at 2 credits, or 6 agent-hours, until a member of your organization lets it continue.
FAQ
Frequently asked questions
Is governed prototyping available today?
Partly. The controls are live, and a teammate can hand an issue to SHIP today and get the prototype back as a pull request. A workspace for non-engineers to describe and change prototypes is in early access.
What is governed vibe coding?
Governed vibe coding means people outside engineering build prototypes with AI, while engineering decides what runs and what merges. In SHIP, the Builder works in a sandbox, the Reviewer checks each prototype against your rules, and only someone with merge rights merges it.
Who approves a prototype?
Someone with merge rights on the repository, as with any pull request. Checkpoints can also pause a run after the plan or the review, so an engineer reads it before it continues.
Where does a prototype run?
On a preview your own delivery pipeline deploys, with your own credentials, so SHIP holds no cloud credentials of yours. Without previews, the Tester builds and runs the prototype in its own sandbox and tests it there.
What does a prototype cost?
Each prototype is one mission, and one credit covers up to 3 agent-hours. Feedback on the open pull request continues the same mission, which pauses at 2 credits until a member of your organization approves more. If a mission fails or needs attention without a pull request, you get the credits back.
Open prototyping to your whole company
Join early access. Every prototype then goes through the same review and checks as engineering's own work.
Join the early-access list
Answer 4 questions. SHIP emails you when it opens to you.