Launch HN: StarSling (YC P25) – Self-improving CI for agent-volume repos

starsling.dev

56 points by yonasb 8 hours ago

We’re Yonas and Daniel and we’re building StarSling (https://starsling.dev), fast GitHub Actions runners with AI agents that ship PRs to continuously improve your tests and workflows.

Every CI job gets its own ephemeral sandbox on the fastest Zen 5 machines and NVMe Disk with unlimited concurrency so a burst of agent PRs all run at once. We’re different from other runners because ours come with agents that cut down your CI bill over time. PRs are generated through our CI harness, which runs an agent loop that’s tuned to improve your CI speed and reduce cost.

Mastra now merges over 1,800 PRs a month and we got their slowest workflow from 29m 56s on GitHub-hosted runners down to 5m 06s (5.87x) on StarSling. We realized the true value of having an agent loop running on top of fast runners when our agents found an 11-month-old performance bottleneck in better-auth. The fix made one of their test jobs 5.4x faster: https://github.com/better-auth/better-auth/pull/10762.

I previously founded StackShare, which grew to over 1.5M developers. Daniel helped build Netflix's internal developer portal. Last year we started building AI agents for DevOps because shipping code to prod fell way behind agentic coding. We hit the CI bottleneck ourselves as we were building agents. Our own agents shipped so many PRs that at peak our job queues were backed up for hours and our CI bill got close to our inference bill.

We now support per-second billing, and just shipped StarSling Disks - persistent disks that give you a 4.9x speedup in dependencies ready over actions/cache. You can see a quick demo of disks in action here : https://www.youtube.com/watch?v=2JrrpRm9Mww.

Our CI harness runs a loop that has agents: - Analyze your workflows, run logs, and machine telemetry - Propose an optimization - Test your unchanged workflow side by side the proposed change - Deterministically judge that the difference is statistically significant - Ship the winner to you as a PR with benchmarks evidence

We benchmarked open source repos on our runners and average 10x speedup in wall clock time with 70% less runner time: - https://github.com/starsling-demo-org/benchmark-gogs (12.8x) - https://github.com/starsling-demo-org/benchmark-shellcheck (5.5x) - https://github.com/starsling-demo-org/benchmark-chatwoot (3.9x) - https://github.com/starsling-demo-org/benchmark-transfer.sh (11.7x) - https://github.com/starsling-demo-org/benchmark-mirotalksfu (36.4x)

Yes, you can do these optimizations yourself with prompts so we’ve released skills for this: https://github.com/starslingdev/skills. The benefit of using our agents is that you don’t need to spend tokens and CI compute finding optimizations yourself.

We started building our runners on AWS at the beginning of the year and realized that was too expensive. But at that time there weren’t any cloud providers that could give us the same machines we were getting on AWS, billed per minute (microVMs). So we convinced a handful of sandbox providers to get Zen 5s and started benchmarking them publicly (https://github.com/starslingdev/hpc-sandbox-benchmarks).

We’ve learned that fast infrastructure is table stakes for CI, but it’s not sufficient on its own. To get fast and cost effective CI you need a process that continues making improvements. We turned CI optimizations from OpenAI, Anthropic, Linear and others into playbooks for your agent: https://starsling.dev/ci-playbooks.

To try it, give your agent this URL: https://docs.starsling.dev/start. You get 2,000 free minutes. Our agents start opening PRs once you've hit about 10,000 minutes.

Today we announced our CI Challenge: if StarSling can't save you at least 10% on your next CI bill, we'll literally give you $1,000. Eligibility and rules here: https://starsling.dev/blog/ci-challenge.

We’d love your feedback on the headless experience and what you’d like to see improved in your own CI setup!

colek42 6 hours ago

We should probably be measuring deployable merges to main. The math just doesn't work for pipeline based CI as you add more agents.

Three things matter.

1 -- How many non-conflicting changes can actually be made at one time (Fan Out)

2 -- How long a critical path takes

3 -- How many times you have to run that critical path. Most orgs run it 2-3x, once before the PR in the agent loop, once in CI, and another in the MQ

This is why most orgs cant get past about 12 PRs an hour.

  • dbworku 6 hours ago

    Definitely agree that agent volume will push beyond pipelined CI. Most teams we’ve talked to are still working to get up to 100 PR/hour.

  • jwilliams 3 hours ago

    > 3 -- How many times you have to run that critical path. Most orgs run it 2-3x

    This is the one we went after. Our agents have to run tsc, lint and the unit tests before they push (it's in a hook), and CI was then doing all three again from scratch. Now the agent records what it ran as a git trailer on the commit and the PR build skips those steps [1]. Anything headed to main still runs everything, so the trailer only has to be trusted on the intermediate pushes.

    Builds went from ~10 minutes to 1.5 over a few weeks, and a good third/half of that was this change. It tends to compound too - getting the build time down led to lower contention, warmer caches, faster throughput. All the usual queuing theory stuff.

    [1] https://jonathannen.com/dont-run-it-twice/

    • dbworku 1 hour ago

      Clever use of a git trailer! This seems like a great middle ground to cut some CI minutes without the full rigor of a CI engine.

      We love Buck2 and Bazel, from first principles. Unfortunately, the DX hurdles of making a codebase hermetic have prevented widespread adoption IMO.

      • jwilliams 16 minutes ago

        Thanks! We actually call it the poor-mans Bazel :)

bekacru 4 hours ago

Bereket from Better Auth - we've been on StarSling for about a year now, it's been such a hard a problem for us ot solve CI to the amount of PRs we get and continues need of optimization and faster runners, im so bullish!

  • yonasb 3 hours ago

    Merging the runner migration was such a proud moment for us! So glad we've been able to take CI off your plate :)

emscb 2 hours ago

So the agent compares the changed workflow with the existing one and judges whether the speedup is significant. But a change that re-shards or skips tests would always look like a win on speed alone, wouldn't it? How do you check that such changes still catch the bugs the old workflow caught? I had the same worry when I trimmed our tests because CI was too slow.

  • yonasb 1 hour ago

    Good question! In terms of the what counts as a win for our agents: speed alone isn't enough. A change only counts if the patched run and the unchanged run executed the same tests (same test IDs, same coverage).

    Re-sharding is allowed because it only changes where tests run, not what runs. It has the same sort of parity check as other patches but it also has a cost check to make sure the change doesn't increase runner time by more than 5% by default. We added the cost check after seeing the agents crush wall clock while 10x'ing costs on some test :)

    Judging whether or not a test should be trimmed isn't something our agents do yet, because as you alluded to, it's hard. But we're working on it! If you have any ideas or an approach that's worked for you, would love to hear it.

    • emscb 19 minutes ago

      When I trimmed my tests, I looked for ones that could be merged. Many unit tests shared the same setup and teardown, so when I merged their middle parts, that setup and teardown only had to run once. Even after merging, the tests still had to stay independent of execution order, so I checked that. In another case, some infrastructure checks were repeated across tests in one folder. For example, “the app needs environment variable A at startup” is already a test of its own, but every application-layer test also asserted it at the start. I kept that check in one place instead.

jstrasner 6 hours ago

So good! CI is still such a pain. Out of curiosity, do you use any open source harnesses under the hood or did you roll your own?

brunoarueira 2 hours ago

Congrats on the launch! In the past pre-AI I did an improvement to the github actions pipeline from 20 minutes down to 6, it's a relief when you improve things like this and improve the team throughput!

  • dbworku 1 hour ago

    Yeah it accelerates the whole team! If you remember, what was the biggest lever? We're always looking to expand the patterns in our /speed-up skill. :)

tristenharr 2 hours ago

Hmm this is very interesting! Good idea.

  • yonasb 1 hour ago

    Thanks! Give it a shot, let us know what you think :)

dotmike 7 hours ago

Congrats on the launch! Will give it a run. Why is your CI fast? Curious to hear the technical details

  • dbworku 7 hours ago

    Our primary difference is self-improving PRs from continuously analyzing the telemetry from your CI. Most folks just sell fast hardware and are happy to charge you for jobs that don't saturate the host.

    In our examples with open-source repos above you'll see that most of speedups that lead to a 10X speedup come from code changes or optimizations.

sochs 5 hours ago

Off topic but every time I read a name like "Star Sling" I get excited to see another space startup tackling a difficult challenge; and so when it turns out to be CI for agents, it's a letdown and an annoyance. Idk, this project seems cool, but maybe pick a less pretentious name.

  • yonasb 4 hours ago

    We chose the name because our original inspiration was an agentic developer portal. So we thought Stargate + Dr. Strange's sling ring that opens portals was a cool mashup. Sorry to disappoint :(

buildwrangler 6 hours ago

Congrats! I spent alot of time scaling really large and complex CI and integration testing builds so its great seeing a product that can help devs with this.

  • dbworku 6 hours ago

    Thanks! It’s an unappreciated bottleneck so we feel your pain.

  • yonasb 5 hours ago

    Thank you! Yeah most teams don't have someone with your experience so they end up with really inefficient GHA setups. Doing our best to help!

gkoberger 7 hours ago

Congrats on the launch! These benchmarks look really great, can't wait to start using this.

What are some of the most interesting things the AI has caught + fixed so far?

  • dbworku 7 hours ago

    Oof. It's hard to pick one! I like the subtle fixes like swapping sleeps in tests with DB readiness checks or pinpointing a single long running test causing a shard to run slow.

d-sanoj 6 hours ago

Congrats on the launch. This seems interesting.

  • yonasb 6 hours ago

    Thanks! If CI is on your priorities list, give us a shot.

esafak 5 hours ago

As you note, we can do those optimizations ourselves. The kind of person looking for CI runners is likely doing that already. What I value is speed, cost, scheduling delay, reliability, observability, local reproducibility, not using YAML... There is a lot of value to provide but workflow optimization is not where I would look.

  • yonasb 5 hours ago

    That's fair. At a certain point, once you value all of those things enough, you'll just move off of YAML entirely (we think of this as Level 4 of CI https://starsling.dev/blog/levels-of-ci#level-4). But I think there are a lot of people still trying to get the biggest gains with the least amount of effort. That's who we're going after first.

  • Bnjoroge 3 hours ago

    I think YAML used to matter more when humans were writing much of the code, but they matter alot less now, especially because you can already write much of your YAML workflows in high level code. It's still matters, but alot less than it used to or enough to be a pain. I agree with the rest of the concerns though.

kinfish 6 hours ago

congrats on the launch!

  • yonasb 5 hours ago

    Thank you!