Shipvane
Your code · Your cloud · Your call

Ship your code,
just point the way.

Shipvane Engine is a full-stack ADLC — the Agentic Software Development Life Cycle — run inside your own cloud. One ticket in, a merge-ready PR out: planned, built, and proven against a real CI build, gated by your approval.

The difference

Your code, your cloud, your call.

Black-box SaaS agents run your codebase in someone else's opaque environment and hand back code they can't truly verify. Shipvane runs in your cloud and proves its work against your actual build.

Black-box SaaS agents

Hand it over and hope

Your repo runs inside a vendor's sealed environment you can't see or control. The model generates code it never truly runs, guesses at your conventions, and hands you a PR that may not even compile.

Shipvane

Owned, then proven

Shipvane runs agentic AI inside your own AWS account — a real branch, your real build & tests. It reads the actual errors and iterates until the gate is green. Nothing leaves your environment; nothing merges without your say.

The ADLC

One agentic loop. The whole lifecycle.

ADLC — the Agentic Software Development Life Cycle. Every stage a senior team runs, Shipvane Engine runs autonomously across your whole stack — from a raw ticket to a merged PR, all inside your own cloud. Point it once; it sails the entire voyage.

1

Intake & triage

A ticket or idea lands. Engine reads it alongside your repo to scope the real work.

2

Enrichment

Sharpens the ticket — acceptance criteria, affected areas, and labels — so the plan is grounded.

3

Planning

Designs the change across the stack, in your conventions, before a line is written.

4

Implementation

Writes frontend and backend on a real branch in a fresh checkout in your cloud.

5

Tests

Writes and runs the tests that prove the change actually does what the ticket asked.

6

Real CI gate

Runs your actual build & tests, reads the real errors, and iterates until the gate is green.

7

Pull request

Opens a clean, merge-ready PR — the full diff, ready for review where your code already lives.

Review & merge

You hold the final say. Feedback loops back through the cycle; on your approval, it merges.

A full loop, not a one-shot — review feeds back in and the cycle runs until it's earned the merge.

The Shipvane Fleet

One ship. Every station crewed.

Shipvane isn't a single tool — it's a small fleet of parts, each named for the job it actually does on a ship. Learn the vessel and you've learned the product.

Capstan hauls the backlog Bridge sees everything Helm sets the course Ensign flies the flag Engine drives the work Connect gets you aboard

Swipe the diagram to see the whole ship →

Engine

In development
Drives the work

The agentic core, packaged to deploy into your own AWS account. It runs the real checkout, build and CI loop where your code already lives — so you own the environment, the logs and the keys.

Connect

In development
Gets you aboard

The tender: point it at a ticket and it hands the work to your Engine, streams progress back, and keeps you in the loop on every approval — without leaving the shell you live in.

Bridge

In development
Sees everything

The dashboard. Run history, live logs, and launch or stop controls — from your browser or your phone.

Open Bridge →

Capstan

In development
Hauls the backlog

The autonomous loop. Point it at a backlog and it works the queue end to end, one reviewable pull request at a time.

Helm

Planned
Sets the course

The dispatcher: what runs, in what order, at what concurrency, under what spend cap. Designed, not yet built — and we'd rather say so.

Ensign

Not a product
Flies the flag

The colours a ship runs up to declare who she is. It's this site — the one part of the fleet you're already looking at.

Proof, not promises

Watch it build a real app.

Anyone can claim an agent writes working code. TideLog is a real app — a harbor operations logbook — that we build entirely with Shipvane, in the open, so you can read every line it wrote and check the build that passed.

1

A ticket goes in

A plain feature request on TideLog's board — no prompt engineering, no hand-holding.

2

Engine does the work

Reads the repo, plans the change, writes the frontend, backend and tests on a real branch.

3

The build has to pass

It runs TideLog's own CI and iterates on the real errors until the gate is green.

4

A PR you can read

The whole diff, open for review — nothing merged until a human says so.

A real example. "Agent notifications for port call events" went in as one sentence. Engine came back with nine files and about 1,100 lines across the API and the UI, plus the test file it wrote to prove the feature worked — green in TideLog's CI before anyone looked at it.

Bring your own AI client

One Engine. Many front doors.

Shipvane Engine speaks the Model Context Protocol and signs in over OAuth — so beyond the Connect CLI, you can drive it straight from the AI client you already use. No custom integration, no lock-in.

Claude Code
Claude Desktop
Claude Mobile
ChatGPT coming

…and any MCP-compatible client, authenticated over standard OAuth.

The safety contract

Nothing ships off-course.

Shipvane is built on one promise: code only moves forward when it's earned the right to.

Runs in your own cloud
Green CI, every time
Your approval to merge
Ephemeral, per-ticket runs
Early access

Be first aboard.

Shipvane is in early development. Join the waitlist and we'll reach out when it's ready to sail.