Kyiv & remote, EU
Run the loop. Keep the memory.
Harbor Gang builds the substrate AI‑native engineering teams run on. Ship orchestrates the SDLC loop from ticket to merged PR. Lighthouse gives agents a knowledge base they can cite — open source to self-host, hosted by us if you'd rather plug in. Buzz turns the same model on marketing. Built by the team that wrote the book on it — literally.
Ship · the loop
8 states
15 specialists · 8 routines
live tickets →Lighthouse · memory
temporal graph
- docFastAPI streaming● live
- rfcRFC 9110 §15● live
- docNext.js 15 segments● live
14k facts · 3 MCP tools
global instance live →Buzz · channels
multi-channel
- queuedX / Twitter12 drafts
- scheduledLinkedIn8 drafts
- queuedBluesky6 drafts
- draftYouTube3 drafts
47 posts · 6 channels
waitlist →Cadence · measured from Ship's own delivery
Cadence from the team that builds Ship.
Measured from the engine shipping its own changes through this loop. Deploy frequency and lead time are real and verifiable; we don't publish change‑fail or recovery numbers we can't yet measure cleanly. A missing number beats a flattering one.
17
PRs shipped, last 24h
Elite10 min
Median lead time, open → merge
Elite85%
PRs merged under an hour
Live1
PRs in flight right now
LiveThe operator moves a card; a transition dispatches the stage; the agent commits its own work and the runner opens the PR. Deploy frequency and PRs‑in‑flight read live from the workspace; lead time is the median over the last 40 merged pull requests on ElMundiUA/ship. Pulled, not rendered — every number is one you can re‑run.
The surfaces
One operating model. Three pieces.
Ship runs the loop. Lighthouse keeps the memory — self-hosted on your infra or hosted by us. Buzz turns the same model on marketing.
The loop · Ship
Closed beta
Ticket to merged PR, named owners.
Seven states. Versioned specialists. Event-driven dispatch off your tracker — work moves on a transition, not a clock. Repo, tracker, knowledge, evidence — one accountable workspace.
See Ship in actionThe memory · Lighthouse
Live
Canonical docs your agent can cite.
71K chunks of RFCs, OWASP, NIST, framework docs over MCP. 21 role recipes, refreshed on cadence. Free anonymous tier; Pro $12/mo unlocks rerank and per-agent tokens.
Plug in to LighthouseSelf-host · Lighthouse
Apache‑2.0Same engine, your hardware, your corpus.
Ingest pipeline, BM25 + pgvector hybrid retrieval, cross-encoder rerank, MCP server. Apache‑2.0, ~50 MB image, runs on a $20/mo VPS. Bring your private docs.
Self-host from GitHubShip · closed beta
The shipping floor for AI‑native engineering teams.
Where every other "AI dev tool" sells the demo, Ship sells the discipline. Named states, accountable agents, approvals you sign from your own agent, an audit trail for the auditors. Built on an opinionated process model — and pressure‑tested by running our own delivery on it.
Workspace home
Ask your agent what's in flight
Priorities live in named buckets — needs‑you, active, drafts, parked. Ask your own agent over MCP and it reads back what's moving and what's waiting on you.
Decisions
Approvals, not a mailbox
Clarifications, approvals, blockers — surfaced by your agent and the /approve page. Resolve, approve, or dismiss; every disposition is logged. Nothing to drain.
Process · SDLC
Seven states. Named owners.
Backlog → Planning → Executing → Reviewing → Awaiting input → Blocked → Closed. A transition dispatches the one routine for that stage — each names which agent acts and what it produces.
The book
We wrote the book on AI‑native engineering.
Forty short chapters. About three hours end to end. A memoir of operators — not best practices, scars. The night the agent shipped nothing. The afternoon fifteen identical fix commits landed in a row. The cron guard that lied about the wall clock.
Free to read online. Hardcover and PDF coming. Read the prologue before deciding whether your team is ready to run a loop this honest.
Field notes
Receipts, not slogans.
Policies before prompts
If your agent doesn't have a policy, it has a vibe. The 200 lines we wrote before any prompt — and why we'd write them again.
Read it →
Boring failures are good failures
When the system breaks, you want the failure to be boring — a contract unmet, a step that refused — not a creative improvisation.
Read it →
Clarification is not failure
When an agent asks a question it counts as progress. We let it cost us — until we measured what cost was actually saved.
Read it →
One operating model
Run the loop. Keep the memory. Ship faster with both.
Ship is in closed beta. Lighthouse is live with a free tier — and open source if you'd rather self-host. The book is free. Pick the door that matches your urgency.