North star
From sign-up to your first closed ticket: one day for SMB, one week for enterprise.
That's the bar. Everything below is what's live, what's in motion, and what we're growing toward to keep that bar honest at every team size.
Production depth
Development process — production depth
Eight states from intake to PR review carry product work end to end with a named owner at every step.
tech Live in workspace `/process` with state transitions, capacity guards, and tracker mapping for Linear / Jira / GitHub Issues / GitLab / Azure DevOps.
Inbox — five item types, five canonical actions
Clarifications, improvements, approvals, failures, exceptions — all routed to the right person, all closed with a recorded reason.
tech Workspace-scoped routing rules bind handles to users, groups, or built-in strategies (`round_robin` and friends). Side-effect-free preview before save.
Knowledge buckets + distiller
Context that agents and reviewers lean on, reviewable like code, supersedeable when the rule changes.
tech Mirrored from `.ship/knowledge/*.md` in connected repos, imported from Notion / Confluence / Firecrawl-backed websites. Distiller routes raw notes to the right bucket.
Workspace + member roles + integrations
Owner, admin, member — three roles with last-owner protection. Integrations in Settings, secrets in the workspace store, audit log on every privileged change.
tech GitHub App for repo activation, OAuth/PAT trackers, Slack/Teams/OTel/S3 export sinks, encrypted workspace secret store with per-event audit.
In active build
Sign-up to first closed ticket
One day for small companies, one week for enterprise. The full path — workspace, repo, tracker, members, policies, first routine — finished in a single working session.
tech Wizard polish, smart defaults per repo size and tracker shape, inline guidance, and onboarding telemetry that flags stuck cohorts before they churn.
Navigator — best AI assistant in the industry
An assistant that knows your workspace cold: what's in flight, why it stalled, which knowledge applies, what to do next. Not a chatbot — a navigator.
tech Workspace-aware retrieval over Inbox, processes, knowledge, audit, and tracker context with topic-shift detection and explicit save-to-bucket flow.
More processes
Marketing, documentation, testing improvements, sales, and support — using the same specialists already in the catalogue.
tech Drafted shapes on `/process` with `marketing_operator`, `support_success`, `technical_writer`, `qa_automation`, and `data_ml_engineer` specialists. Each lifted from draft to production depth one process at a time.
Wider integration base
Talk to Ship from the tools your team already uses — Slack, Teams, Discord — and bind to whatever tracker the company runs on.
tech More orchestrators, more trackers, native chat-app surfaces (Slack/Teams/Discord) for routed Inbox items and routine output, not just notification hooks.
Growing toward
Mobile + voice
Approve, clarify, and decide from your phone. Open the Inbox by voice on the way in. The workspace travels with the operator.
tech Native iOS / Android apps with push routing, plus voice intake for clarification answers and approval flows — same Inbox contract, new surface.
Custom desktop app
An always-on workspace surface that lives outside the browser and survives the next tab close.
tech Electron / Tauri shell wrapping the console with native notifications, persistent agent sessions, and offline-tolerant sync.
Release process automation
Promotions and rollbacks become a process like any other — with states, owners, and evidence that survives the ship-it adrenaline.
tech Release as a top-level process with environment progression, rollback approvals, and post-release retro routines tied to the same audit log.
Compliance & security certifications
SOC 2 Type II, ISO 27001, and the rest of the procurement checklist enterprise customers ask for.
tech Audit-log retention guarantees, evidence collection automated through compliance routines, third-party attestation in flight.
Out of scope, on purpose
Four things we won't build
Saying yes to everything is how a tool ages into a vendor demo. Saying no in writing is how the contract stays defendable when budget and quarter both close at the same time.
We won't teach you how to run your business
You know your customers, your roadmap, and your constraints better than any tool ever will. Ship adapts to how you already work — it doesn't push opinions about strategy onto teams that already have them.
We won't transform your processes
We automate the processes you already have. If your engineering team uses Linear and Jira, your support team uses Zendesk, your marketing uses Notion — we plug into all of them. We do not ship a new operating model and expect you to migrate.
We respect the difference between solo and company
A solo developer with Claude Code or Codex doesn't need a workspace. A company with twenty contributors and three trackers does. We build for the second audience without pretending the first one is broken.
We won't keep you spending months on banal projects
Companies still pay months and millions for repeatable delivery work that should be a routine. The whole point of Ship is to make those routines reviewable, fast, and boring — so the team's expensive hours go where the judgement calls actually live.
Technical appendix
Agent runtime support matrix
For platform engineers picking an agent runtime: fourteen runtimes ship today. The four core runtimes carry the weight of production; the rest are working and waiting for early adopters to feed back what they learn. The contract is the same across every row.
| Tier | Agent | Marker | Install target |
|---|---|---|---|
| core | cursor | .cursor/, .cursor/rules/ | .cursor/rules/ship-artifacts-protocol.mdc |
| core | claude | CLAUDE.md, .claude/ | CLAUDE.md |
| core | codex | .codex/ | .codex/SHIP_API.md |
| core | copilot | .github/copilot-instructions.md | .github/copilot-instructions.md |
| adjacent | agents-md | AGENTS.md | AGENTS.md |
| adjacent | claude-md | CLAUDE.md | CLAUDE.md |
| adjacent | aider | .aider.conf.yml, AIDER.md | AIDER.md |
| adjacent | cline | .clinerules | .clinerules |
| adjacent | continue | .continue/config.json | .continue/ship.md |
| adjacent | windsurf | .windsurfrules | .windsurfrules |
| adjacent | zed | .zed/, .zed/settings.json | .zed/ship.md |
| adjacent | gemini | GEMINI.md, .gemini/ | GEMINI.md |
| adjacent | opencode | .opencode/ | .opencode/ship.md |
| adjacent | cursor-cloud | .cursor/environments.json | .cursor/environments.json |
Next
Pick a runtime, run the contract
The catalogue you see today is a snapshot. The trajectory is what matters. If you want to ship on it now, the closed beta is open by invite.