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!
We use Mastra to run the agents in our CI harness. It's been great for being able to swap out models easily. More details here https://starsling.dev/blog/agent-loop.
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.
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.
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.
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 :(
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.
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.
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.
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!
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.
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.
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?
We use Mastra to run the agents in our CI harness. It's been great for being able to swap out models easily. More details here https://starsling.dev/blog/agent-loop.
Congrats on the launch! Will give it a run. Why is your CI fast? Curious to hear the technical details
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.
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.
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!
Thanks! It’s an unappreciated bottleneck so we feel your pain.
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.
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 :(
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?
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.
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.
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.
Congrats on the launch. This seems interesting.
Thanks! If CI is on your priorities list, give us a shot.
congrats on the launch!
Thank you!