I am rewriting Coolify in Rust
coolify-rs is a project of mine: one Rust binary in place of Coolify’s PHP, Laravel, Horizon and Redis, serving the same REST API against the same Postgres database.
A brief about my own project, so take the enthusiasm with the appropriate pinch of salt.
coolify-rs is a Rust reimplementation of Coolify, the self-hostable deployment platform. It serves the same /api/v1 REST API, reads and writes the same PostgreSQL schema, encrypts secrets the same way and ports the same web UI. Underneath, one compiled binary stands in for PHP, Laravel, Horizon, the scheduler and Redis.
The numbers I measured, running both as isolated stacks on 2 CPU cores with the same data: 30 MiB at idle against Coolify’s 372 MiB, 1,155 to 1,430 API requests per second against 165 to 178, and a 0.22s start against 1.62s. Migration goes both ways, so a Coolify database can be adopted and handed back at the same version. Where it deliberately differs from upstream, KNOWN_LIMITATIONS.md says so. Apache-2.0, and not affiliated with coolLabs.
Why it matters: mostly as an answer to a question I had been carrying for a while, which is what Laravel’s runtime actually costs on a small server once you stop guessing and measure it.
The caveat: it is early. First commits were on 3 November, there is no tagged release, and the installer expects you to build and serve it yourself. The benchmarks are mine, on my setup, not independent. Read it, do not put it in front of your deployments.