Most CI/CD bottlenecks are found after deployment, not before. ForgeCI changes that — build, test, and deploy inside isolated Docker containers orchestrated through Kafka.
A real distributed CI/CD engine. Here is what happens when you connect a repo and run a pipeline.
Authenticate with GitHub OAuth. ForgeCI gets read access to your repos — lists them on your dashboard.
Create a forgeci.yml with stages: install, test, build, deploy. Each stage runs commands inside an isolated Docker container.
Orchestrator creates a build entry in Postgres, publishes a Kafka event. Worker nodes consume jobs from the queue.
Worker clones your repo, runs stages inside Docker. Logs stream live via Kafka → WebSocket. Artifacts upload to MinIO.
Production-grade distributed systems — the same patterns used by Jenkins, GitHub Actions, and GitLab CI internally.