The open-source engine for your software factory.
> Build your team’s software factory without rebuilding the infrastructure.
- You:
CI on main has been red since this morning. What happened?
- Shippy used:
- ✓list_workflow_runs ci · main · failed4 runs
- ✓get_step_logs run #1198 · test
- Shippy:
The test step has failed on every run since #882 merged. #882 switched CSV exports to semicolons, but export.test.ts still expects commas. Same assertion each time, so it isn't flaky.
Want me to open a PR that updates the test? - You:
Yes, open it.
- Shippy used:
- ✓start_workflow_run Task to pull requestrun #1205
- Shippy:
Done. The test now expects semicolons, and CI passes on the fix.
- Pull request: PR #884 · Update the CSV export test for semicolons✓ checks passed · ready to merge
Integrations
Connect the tools your team already uses.
Popular tools connect in one click. We enable the rest for your workspace on request.
Source control
- GitHub(connects in one click)
- GitLab(set up with our team)
- Bitbucket(set up with our team)
- Azure DevOps(set up with our team)
- Gitea(set up with our team)
- Graphite(set up with our team)
Issue tracking
- Linear(connects in one click)
- Jira(connects in one click)
- ClickUp(connects in one click)
- Asana(set up with our team)
- Shortcut(set up with our team)
- Trello(set up with our team)
Chat and email
- Slack(connects in one click)
- Microsoft Teams(set up with our team)
- Discord(set up with our team)
- Google Chat(set up with our team)
- Mattermost(set up with our team)
- Gmail(set up with our team)
Docs and meetings
- Notion(connects in one click)
- Claap(connects in one click)
- Confluence(set up with our team)
- Google Drive(set up with our team)
- GitBook(set up with our team)
- Loom(set up with our team)
Errors and analytics
- Sentry(connects in one click)
- PostHog(connects in one click)
- Jam(connects in one click)
- Datadog(set up with our team)
- Grafana(set up with our team)
- New Relic(set up with our team)
CI/CD and deploys
- CircleCI(set up with our team)
- Buildkite(set up with our team)
- Jenkins(set up with our team)
- Vercel(set up with our team)
- Netlify(set up with our team)
- Cloudflare(set up with our team)
Incidents
- PagerDuty(set up with our team)
- incident.io(set up with our team)
- Rootly(set up with our team)
- Better Stack(set up with our team)
- Statuspage(set up with our team)
Security
- Snyk(set up with our team)
- SonarQube(set up with our team)
- Semgrep(set up with our team)
- Socket(set up with our team)
- GitGuardian(set up with our team)
Cloud and infrastructure
- AWS(set up with our team)
- Google Cloud(set up with our team)
- Microsoft Azure(set up with our team)
- Terraform(set up with our team)
- Pulumi(set up with our team)
Data
- Snowflake(set up with our team)
- BigQuery(set up with our team)
- Supabase(set up with our team)
- Neon(set up with our team)
- dbt(set up with our team)
Support and CRM
- Zendesk(set up with our team)
- Intercom(set up with our team)
- Plain(set up with our team)
- HubSpot(set up with our team)
- Salesforce(set up with our team)
Anything else
- Custom webhook(connects in one click)
Send events from any system to a webhook URL, or ask for the integration you need.
Connects in one click
Set up with our team
Defined in code
Your software factory, defined in code.
Improve your factory the way you improve your code: small reviewed changes, tested on a branch, measured run by run.
.shipfox/workflows/fix-sentry-issues.yml
A workflow runs on its own when an event arrives. Steps run in order, and the gate sends the agent back until the tests pass.
What it does
run #2041 · Fix new Sentry issues
- triggerissue.created · TypeError in invoice export
- runnpm ci
- fixRead the stack trace, guarded empty invoices
- testnpm test · 1 failing
- gaterestart_from: fix · attempt 2
- fixKept the zero total in the CSV
- testnpm test · 214 passing
- usesopen-pull-request · PR #891 opened
Reviewed
Changes go through pull requests and your merge rules. Shipfox picks them up when you merge.
Shared
Everyone works from the same agents, workflows, and actions, instead of each engineer keeping a private setup.
Customized
Start from the agents and workflows your factory comes with, then change any prompt, model, or check.
Infrastructure
The factory infrastructure you’d build yourself.
Webhooks and sandboxes are the easy part. This is the backlog that comes after, and the Shipfox engine already handles it.
Intake · 7
Sandboxes · 8
Models · 6
Access · 6
Reliability · 7
Records · 5
- Your agents and their instructions
- Your workflows and checks
- Who reviews and approves
Build your factory. Reuse the engine.
Open source
Open at every layer.
Starting with the engine itself: choose your harness, models, compute, and where your data lives.
We run the engine, models, and storage for you. Runners can be ours or yours.
Layer 01
The engine
Layer 02
Any harness
Your choicePick the agent runtime for each step: the Claude Agent SDK, or pi for every other model.
- claude
- pi
Layer 03
Any model
Managed by ShipfoxFrom the latest frontier models to open-weight ones, with no keys to manage. Choose per step for cost, speed, or precision.
- Frontier
- Open weight
- Per step
Layer 04
Compute
Ours or yoursHosted runners start for each job. You can also register runners in your own network.
- Hosted runners
- Your network
Layer 05
Storage
Managed by ShipfoxWe store your runs, logs, and agent sessions, and keep them for 90 days.
- Managed storage
- 90-day history
Start with a factory that already works.
> Your workspace comes pre-populated. Make it yours when you’re ready.