Introduction

KibanOS is an open-source infrastructure platform. Developers build software — Kiban builds infrastructure.

What is KibanOS?

KibanOS is a self-hosted platform that lets you deploy and manage services — databases, monitoring tools, CMSs, AI models, and more — without touching Docker commands, writing compose files, or configuring reverse proxies.

You think in projects, environments, and services. Kiban handles everything else: containers, networking, routing, ports, and health checks. It is not a layer on top of Docker Compose. It is a complete abstraction that replaces it.

The platform ships with a catalog of over 100 services across 30 categories. Installing PostgreSQL, Grafana, Redis, or Nextcloud is a single click. No YAML. No terminal. No configuration files.

What KibanOS is not

KibanOS is not a Docker UI, a Docker Compose editor, a PaaS, or a Kubernetes dashboard. Docker is the runtime underneath, but Kiban abstracts it away completely. You never see container IDs, image names, or network configurations.

If you are looking for a tool to manage compose files visually, KibanOS is not that. If you want direct Docker access with a nicer interface, there are other tools for that. KibanOS is built for people who want to deploy services without thinking about the infrastructure layer at all.

Key features

• Service catalog — 100+ services across 30 categories: databases, AI, monitoring, CMS, productivity, messaging, and more.
• Project and environment management — group related infrastructure into projects, with fully isolated environments per project.
• Automatic reverse proxy — Traefik-based routing with local URLs like {service}.{project}.localhost. No manual configuration.
• Interactive terminal — debug running service containers directly from the web UI.
• Service logs — real-time logs with auto-refresh, copy, and clear.
• Health monitoring — Docker Health as the authoritative signal for service status.
• Automatic port assignment — no port collisions, no manual mapping.
• Zero-code extensibility — adding a new service requires only a catalog folder, no code changes.

How it works

KibanOS organizes infrastructure into three levels:

Projects
  └── Environments (Development, Staging, Production)
        └── Installed Services (PostgreSQL, Redis, Grafana, etc.)

Each project groups related services. Each environment is fully isolated with its own network. Services are installed from the read-only catalog and managed through a single web UI.

Kiban owns HTTP routing. You never configure Traefik labels or Docker networks manually. Everything is generated from the service catalog and your project configuration.

Why KibanOS?

Self-hosting today means choosing between convenience and control. Cloud platforms are easy but expensive and lock you in. Hosting your own services gives you control but requires deep Docker knowledge, constant maintenance, and debugging networking issues.

KibanOS removes the trade-off. You get the simplicity of a managed platform with the freedom of self-hosting. Your data stays on your server. Your costs are predictable. And you never have to write a docker-compose.yml again.

Getting started

KibanOS requires Docker and Docker Compose. Install it with a single command:

curl -fsSL https://get.kibanos.com | sh

Then open the web UI and create your first project. For detailed instructions, see the Installation guide.