Launched this week
DeployStack
Open-source, self-hosted alternative to Vercel and Render
9 followers
Open-source, self-hosted alternative to Vercel and Render
9 followers
DeployStack is a robust, self-hosted CI/CD platform that turns any VPS into a private deployment engine. Built for developers who want Vercel like automation without the vendor lock-in or high costs. Key Features Automated Pipelines: GitHub Webhook integration for instant containerized builds. Architecture: Kafka-driven job queues ensure stable, high-concurrency builds. Security: One-script setup with dynamic secrets and hardened local networking. Own your infrastructure. Deploy on your terms.
The "one-script setup on a fresh VPS" bar is the right one — most self-hosted CI/CDs lose people in the first 20 minutes of nginx + secrets + webhook config. Curious about the Kafka choice though: at the scale most solo-VPS deployers run, what made async job queuing worth the extra operational weight vs a simpler Redis/BullMQ stack? Genuinely curious where the inflection point landed for you.
@borrellr_ A big part of the decision was moving from a push-based model to pull-based architecture.
With BullMQ setup, the queue pushes jobs to workers, which can be heavy for a VPS if multiple deployment are there at once. Using Kafka, I can decide when to pull, when a deployment completes irrespective of it's status (success or failure), the runner can pull next deployment. This make a proper sequence in the backend and no racing between the deployments.
I've thinked upon one feature here too which is when a deployment fails, I can call a LLM model to identify the rootcause and then can tell the developer to fix that.
Hope this is what you're expecting, also please let me know if you have any other questions, love to hear that :)
RiteKit Company Logo API
The Kafka integration for handling deployment jobs is a smart move—async job processing is exactly what separates stable self-hosted solutions from ones that break under load. The security-first approach with databases bound to localhost is the kind of detail that matters when developers are trusting you with their infrastructure.
@osakasaul This is the reason for which DeployStack can handle load during heavy deployments and makes this reliable