Store the state of your VPS containers in a repo. Konta helps you use Git as a single source of truth, automatically sync changes with server containers using docker-compose files — no cluster, no control plane. Simply push changes to Git, and your containers will be updated automatically.

Hi everyone. I created Konta because I manage several small VPS servers with projects for which using Kubernetes or similar tools is simply not an option. I needed: - Git as a source of truth - Simple application configuration via Docker Compose - Automatic update deployment - No unwanted migration of a bunch of new config files So I created Konta. It's designed for developers who manage small and medium-sized infrastructure and want reproducibility without the hassle. It's a tool for servers with few resources and simpler tasks where powerful cluster utilities are overkill. You install it on your VPS, connect your Git repository, and it syncs all applications to your server according to the repository's instructions. It also keeps the list of containers up-to-date. I'd really appreciate your feedback: How interested are you in the GitOps approach for small projects? What would prevent you from using it for your needs? How often do you install, configure, and update applications on servers from scratch and what tools do you use? Thank you for your attention 🙌

@talyguryn What makes Konta lightweight enough for low-resource VPSes compared to other GitOps tools like Flux or Argo? Does Konta rely on a custom pull agent, scheduler, or reconciliation loop? How does it manage state?

Konta

GitOps for Docker Compose on low‑resource VPS

GitOps for Docker Compose on low‑resource VPS