Open source · MIT

The open-source engine for your software factory.

> Build your team’s software factory without rebuilding the infrastructure.

shippy · acme/webproject agent
  1. You:

    CI on main has been red since this morning. What happened?

  2. Shippy used:
    • ✓list_workflow_runs ci · main · failed4 runs
    • ✓get_step_logs run #1198 · test
  3. 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?

  4. You:

    Yes, open it.

  5. Shippy used:
    • ✓start_workflow_run Task to pull requestrun #1205
  6. Shippy:

    Done. The test now expects semicolons, and CI passes on the fix.

  7. Pull request:
    PR #884 · Update the CSV export test for semicolons
    ✓ checks passed · ready to merge
>Ask Shippy about this project

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

Browse every integration in the docs

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.

name: Fix new Sentry issues
triggers:
  new_issue:
    source: sentry_acme
    event: issue.created
jobs:
  fix:
    steps:
      - run: npm ci
      - key: fix
        prompt: Fix issue ${{ event.issueId }} with a test.
        integrations:
          - connection: sentry_acme
            include: [get-issue, get-issue-event]
      - key: test
        run: npm test
        gate:
          on_failure:
            restart_from: fix
      - uses: ./.shipfox/actions/open-pull-request
        connections:
          github: github_acme
        with:
          title: Fix ${{ event.title }}

What it does

run #2041 · Fix new Sentry issues

  1. triggerissue.created · TypeError in invoice export
  2. runnpm ci
  3. fixRead the stack trace, guarded empty invoices
  4. testnpm test · 1 failing
  5. gaterestart_from: fix · attempt 2
  6. fixKept the zero total in the CSV
  7. testnpm test · 214 passing
  8. 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.

Platform backlog

Intake · 7

Sandboxes · 8

Models · 6

Access · 6

Reliability · 7

Records · 5

Yours to build
  • 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.

Edition

We run the engine, models, and storage for you. Runners can be ours or yours.

  1. Layer 01

    The engine

    Managed by Shipfox

    We run and upgrade it for you, based on our MIT engine.

  2. Layer 02

    Any harness

    Your choice

    Pick the agent runtime for each step: the Claude Agent SDK, or pi for every other model.

    • claude
    • pi
  3. Layer 03

    Any model

    Managed by Shipfox

    From 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
  4. Layer 04

    Compute

    Ours or yours

    Hosted runners start for each job. You can also register runners in your own network.

    • Hosted runners
    • Your network
  5. Layer 05

    Storage

    Managed by Shipfox

    We 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.