CI that actually runs when you push.

Faster. More reliable. Same GitHub Actions YAML. Your code stays on your infrastructure.

Our mascot, a German Shepherd
This dog is impatient.
So are we.

The problem with CI today

You push code. Then you wait. GitHub Actions queues your job. The dispatcher forgets to dispatch. A cold VM spins up. Dependencies install from scratch. You wait a minute to learn you forgot a semicolon.

30-60 second queue

Jobs sit in queue before they start. Every push, every PR, every time.

The dispatcher forgets

Sometimes jobs just never start. You refresh the page. Still queued. You wait.

Cold starts every run

Fresh VM, fresh git clone, fresh dependency install. Same work, every time.

Your code leaves your infra

GitHub clones your repo to their servers. Builds run on their machines.

How HorseCI fixes it

Immediate dispatch

We wrote a faster dispatcher. Webhook to worker in milliseconds, not seconds. No queues, no forgotten jobs.

Warm workspaces

Your worker stays on your machine. Dependencies cached. Repo already there. Second push is fast.

Your code stays yours

We dispatch webhooks. Your worker checks out code and runs builds. We never see your source.

Same YAML

Use existing .github/workflows/*.yml. No migration. No code changes.

How it works

You run a worker binary on your machine. It connects to our dispatcher via WebSocket. When you push, we route the webhook immediately. Your machine runs the build. We never touch your code.

HorseCI vs GitHub Actions

GitHub Actions

  • 30-60 second queue
  • Dispatcher forgets to run
  • Cold VM every time
  • Code on GitHub servers
  • Secrets in GitHub env
  • Pay per minute

HorseCI

  • Immediate dispatch
  • Actually runs when you push
  • Warm workspace, cached deps
  • Code on your hardware only
  • Secrets stay on your machine
  • Flat monthly fee
Get Started