mind trying https://github.com/preloopdev/preloop? We follow the official runner protocol 100% so we should hopefully have more workflow-compat.we also run in cross-platform microvms, not docker containers.
Hopefully a good spot to plug my own project, preloop, which is a drop-in replacement of Github actions(both the runners and control plane) that runs locally or self-hosted in isoalted microvms, and supports debug-on-failure. You can also push to the server, run CI and then optionally create a draft PR. Not quite production-ready yet(for the self-hosted part), but the local part works well. We implement the official runner protocol 100% unlike act/gitea/forgejo, so your workflows are more likely to work out of the box with preloop(forgejo has the closest compatibility with Github Actions though so it's a good off-Github option) and we use microvms so no DinD issues. I'm working on getting the official runner vm image up to reduce any environment incompatibilities. Feel free to try it out: https://github.com/preloopdev/preloop
Hopefully a good spot to plug my own project, preloop, which is a drop-in replacement of Github actions(both the runners and control plane) that runs locally or self-hosted in isoalted microvms, and supports debug-on-failure. You can also push to the server, run CI and then optionally create a draft PR. Not quite production-ready yet(for the self-hosted part), but the local part works well. We implement the official runner protocol 100% unlike act/gitea/forgejo, so your workflows are more likely to work out of the box with preloop(forgejo has the closest compatibility with Github Actions though so it's a good off-Github option) and we use microvms so no DinD issues. I'm working on getting the official runner vm image up to reduce any environment incompatibilities. Feel free to try it out: https://github.com/preloopdev/preloop
Hopefully a good spot to plug my own project, preloop, which is a drop-in replacement of Github actions(both the runners and control plane) that runs locally or self-hosted in isoalted microvms, and supports debug-on-failure. You can also push to the server, run CI and then optionally create a draft PR. Not quite production-ready yet(for the self-hosted part), but the local part works well. We implement the official runner protocol 100% unlike act/gitea/forgejo, so your workflows are more likely to work out of the box with preloop(forgejo has the closest compatibility with Github Actions though so it's a good off-Github option) and we use microvms so no DinD issues. I'm working on getting the official runner vm image up to reduce any environment incompatibilities. Feel free to try it out: https://github.com/preloopdev/preloop
Hopefully a good spot to plug my own project, preloop, which is a drop-in replacement of Github actions(both the runners and control plane) that runs locally or self-hosted in isoalted microvms, and supports debug-on-failure. You can also push to the server, run CI and then optionally create a draft PR. Not quite production-ready yet(for the self-hosted part), but the local part works well. We implement the official runner protocol 100% unlike act/gitea/forgejo, so your workflows are more likely to work out of the box with preloop(forgejo has the closest compatibility with Github Actions though so it's a good off-Github option) and we use microvms so no DinD issues. I'm working on getting the official runner vm image up to reduce any environment incompatibilities. Feel free to try it out: https://github.com/preloopdev/preloop
Thanks! On the runner/control plane side, most of what is left is adding support for the latest's runner advanced features/fixes. Things like deferred/dynamic matrices, background steps, some edge cases in the old AZDO protocol, step-count expression evaluation etc. On the overall product side, there's quite abit more missing that's planned: support for macos/windows runners, a pass-through cache, an actually nice TUI, a bunch of refactors to make it more extensible, better general observability/logs and alot more work on reliability/performance, and the scheduler.
thanks for the feedback! Was it mostly the font, structure or content or everything? I’ll make sure to use a more minimal/standard docs site. For now I have them in /docs in the repo.
Yes! You could effectively use the official runner against preloop or our (almost) drop-in rust equivalent which is a 10x smaller binary and has far lower idle rss. The control plane currently is unfortunately coupled with the data plane, but a refactor is one of my top priorities soon.
hmm, the pricing table shows it bills per-CPU hours. why did you specifically chose sprites.dev vs an alternative or making your own?Anything they do particularly better than others?
Thanks! Here's a more detailed comparison: https://github.com/preloopdev/preloop/blob/main/docs/preloop.... The TLDR is act(much like Forgejo/Gitea) try to behaviorally emulate how your workflows run in docker containers. Preloop uses the exact same protocol the official runner does and runs each job in microvms. I try to match not only te request/response bodies, but down to the job/step log/annotations/conclusions level, so you could essentially use the official runner against preloop, and it would work as it would communicating with Github. Preloop is also designed to be agent-native from the ground up so an agent can drive the entire CI in real-time and debug like we do. Forgejo has the closest compatibility among the three in practice, and if you are fully off Github, I think it's a good enough choice. Here's a more detailed description of some things we do to ensure compatibility: https://github.com/preloopdev/preloop/blob/main/docs/conform...
Thanks! I'm glad it resonates. Still pretty beta, but I'm hoping this can be a good alternative when Github goes down, which unfortunately has been a bit too often, with as minimal of a lift from the user side. And of course, making it easier for agents to fully drive ci.
Looks cool! would be great if the pricing was down to the minute. Often some coding sessions might be quick ones, unless the focus is mostly on background agents that do long-running jobs.
Lots of fun projects being listed. I'm working on Preloop(https://preloop.dev), a way to run your unmodified Github Actions locally or self-hosted in isolated cross-platform microvms(uses smolvm which uses libkrun vmm).I got frustrated with Github Actions reliability and inability to run or test my workflows locally so i re-wrote the runner and reverse-engineered the control plane so it follows the exact runner protocol the offficial runner does. Each job runs in a microvm that boots in 400ms from a packed image. Also supports a way to pause on every failure so you or your agent can immediately shell at that point, fix and retry(in a new environment) to verify. Also supports the full DAP protocol so you can interactively step/forward/investigate context at each step/job.
As someone who’s building a github actions control plane replacement, the scheduler is extremely simple. It basically the kost naive version of a FiFO queue.
Is it? Last time I checked, I had to maintain a custom fork because they didnt support device auth for remote env so you couldn’t really use your chatGPT sub.
gotcha. yea ideally you take a full live snapshot of my current state, untracked files, processes etc, and resume them in the cloud. Congrats on the launch! A mobile app would also be nice
Huh? V4Flash is still incredibly price competitive. The new version is right around GLM 5.2 and maybe slightly worse than opus 4.8 depending on which benchmark you use while being much cheaper(even factoring how most US zdr providers charge 10x Deepseek’s api caching price). K3 is also a tad behind fable/sol while being alot cheaper
What’s the experience like going from an active on-going thread to a cloud-hosted one? I dont wanna always work on the cloud, and want my current setup to be exactly the same as in the cloud, and should be pretty seamless. Only folks i’ve seen solve these are folks who run the sandboxes locally and take that to the cloud like smolvm/microsandbox.
Why a clone over a worktree? The obvious disadvantage I can see is you dont share your git objects with a clone and for really large repos that becomes an issue