opencompany
Toggle navigation menu

Turn feature ideas into shipped PRs.

Ship runs on the coding agents you already use — Codex and Claude Code — triggered by what your users report, with your company's context built in.

Demo — coming soon

Slack ticket → Ship picks it up → Codex builds with your conventions → PR opens for review.

The whole loop, start to finish — no manual triage, no blank branch.

Ship turns user feedback into code, so your backlog shrinks while you sleep.

  • Any trigger Slack, Linear, email — wherever users report things.

  • Bring your own agent Runs on your Codex or Claude Code subscription.

  • Company context Your conventions, decisions, and docs in every PR.

  • You review Nothing merges without you.

  • Your whole team Everyone sees what's shipping and why.

  • Gets better Every correction you make is remembered.

# How it works

  1. 1.

    Connect where users report bugs and ideas.

  2. 2.

    Ship builds it with your coding agent and your context.

  3. 3.

    Review the PR. Merge.

Ready to ship the backlog?

# FAQ

Before you connect a repo.

The practical details about setup, sources, models, pricing, and your data.

01Do I need a Codex or Claude Code subscription?+

Yes — bring it with you. Ship drives the agent subscription you already pay for; we don't resell agent usage on top.

02Why not just use Claude Code directly?+

Nothing fires when a bug lands in Slack. Ship is the trigger — it watches where your users report things and hands the ticket to your agent with your company's context already loaded.

03What does Ship do with my code and data?+

Your code stays in your repo. Ship opens PRs on branches you control and only reads what it needs to do that — nothing is used to train a model.

04How much does it cost?+

Ship is in early access. Pricing will follow OpenCompany's usage-based model — no per-seat licensing. Get early access and we'll confirm details before anything's charged.

05Is this for non-technical founders?+

No — Ship is for semi-technical founders and teams. You still review and merge every PR, so you need to be able to read a diff and know your codebase.