Self-hosted CI without the CI platform. Small on purpose: one Go binary, one SQLite file, one Check Run per commit. Every commit gets a native GitHub Check Run from a GitHub App you own. You register the App, bind repos in a web UI, and the worker runs on a server you already have. UI, API, webhooks, and the job runner live in one process. Source, builds, secrets, and logs stay on your infrastructure. The pipeline file is `.ci.yml`, not Actions YAML. License: Apache-2.0.

I built openpreflight because I wanted Check Runs on a box I already pay for. I did not want to learn Actions YAML or run someone else's control plane. It is small on purpose: one binary, one SQLite file, one Check Run per commit. Commits to the openpreflight repo are checked by a self-hosted instance at https://ci.openpreflight.xyz, with a GitHub App registered the same way you would register yours. This does not replace GitHub Actions. We still use Actions to publish release images. openpreflight is for private repos when you want native Check Runs from your own server. Quickstart: https://docs.openpreflight.xyz/g... Source: https://github.com/openpreflight... Site: https://openpreflight.xyz

@trivedivatsal Congratulations Vatsal. Good to see you have made it open-source, I've seen you believe in "Build in Public", which is great, actually!

@pareshmayani Thank you! Really appreciate that. 🙌 Building in public and keeping things open-source has always felt like the right way to build and learn.

@trivedivatsal Congratulations Vatsal. Good to see you have made it open-source, I've seen you believe in "Build in Public", which is great, actually!

@pareshmayani Thank you! Really appreciate that. 🙌 Building in public and keeping things open-source has always felt like the right way to build and learn.