VPS or dedicated server
Bring a Linux box from Hetzner, DigitalOcean, AWS, OVH, Linode, or any provider you already trust.
- Provider independent
- Keeps data on your machine
- Good for public services
Open source self-hosting
Your infrastructure.
Simplified.
BETAKiban lets you deploy and manage self-hosted services from your own server, without turning every app into an infrastructure project.
Install in one command
curl -fsSL https://get.kibanos.com | shSelf-hosting, without the complexity.
KibanOS
Services100+ available
- PostgreSQLRunning
- GrafanaRunning
- ImmichRunning
- RedisRunning
Self-hosting shouldn't mean managing everything yourself.
Getting a self-hosted stack running usually means stitching together Docker Compose files, networks, environment variables, volumes, updates, and dependencies. It works, but it takes time and attention that could be spent elsewhere.
One place for your self-hosted stack.
Kiban provides a unified interface for deploying and managing self-hosted services, with Docker and Compose as the foundation underneath.
Simple
Install and manage services without starting from scratch every time. Kiban handles the repetitive setup so you can focus on using the tools.
Open
Built on open technologies and Docker Compose. No proprietary runtime. No hidden abstractions. Your stack stays portable.
Yours
Your servers. Your data. Your infrastructure. Kiban runs where you want and keeps you in control of every service.
The system
One control layer for the whole self-hosted stack.
From choosing a service to keeping it updated, Kiban turns the repetitive parts of Docker-based self-hosting into a clear workflow without hiding the underlying infrastructure.
01
Choose
Pick a service
Select an app from the Kiban catalog instead of starting from a blank Compose file.
02
Configure
Set the few things that matter
Ports, local URLs, volumes, environment values, and dependencies are presented in one guided setup.
03
Compose
Generate a portable stack
Kiban keeps Docker and Compose underneath, so the result remains readable and movable.
04
Run
Start it on your server
Services run on your own Linux machine, connected through isolated networks and persistent volumes.
05
Operate
Start using it
Kiban keeps status, logs, health, access points, and service controls in one place.
Where it runs
Your server. Your rules.
Kiban is designed for infrastructure you own or rent directly. No managed cloud is required to keep the control plane alive.
Homelab and local hardware
Run the stack on a mini PC, NAS, Raspberry Pi, or an old machine you control at home.
- Local-first services
- No subscription required
- Works with small setups
Existing Docker hosts
Use Kiban as a calmer operating layer for services that should remain plain containers underneath.
- Docker-based foundation
- Readable Compose model
- No proprietary runtime
How it works.
No complex setup. No hidden configuration. From a fresh server to a running stack in minutes.
01
Install
Kiban sets up the core environment and leaves the rest of your system untouched.
curl -fsSL https://get.kibanos.com | sh02
Create a project
Organize your services into projects. Add environments to isolate development, staging, or production stacks.
Project → Environment03
Pick a service
Kiban wires up Docker Compose, networks, volumes, and environment variables for you.
Catalog → Review → Install04
Manage
Start, stop, restart, and inspect Kiban from the CLI. Your data stays on your server.
kiban statusEverything you need to run a stack.
Kiban covers the repetitive parts of self-hosting so you can spend time using your services instead of configuring them.
Deploy
- Browse 100+ services in the catalog
- Install from prepared service templates
- Start, stop, restart, and delete
- Automatic port assignment
Organize
- Projects to group services
- Environments per project
- Service configuration in one place
- Service details in one view
Connect
- Built-in reverse proxy
- Environment-isolated networks
- Automatic local URLs
- No manual proxy configuration
Operate
- Interactive terminal per service
- Streaming logs per container
- Health status at a glance
- Dark theme and responsive UI
Product roadmap
Services today. Infrastructure control next.
Kiban starts with self-hosted service management, then expands into the pieces that make running your own infrastructure practical: CLI, secrets, domains, backups, notifications, applications, Git, and plugins.
NowAvailable
Self-hosted services
Kiban already focuses on the core self-hosting workflow: choose a service, install it, access it, and operate it from one place.
- 100+ service catalog
- Kiban CLI
- Projects and environments
- Custom domains and HTTPS
- Logs, health, terminal, access points
NextOngoing
Infrastructure controls
After the first release, Kiban expands into the operational pieces every self-hosted stack eventually needs.
- Variables and secrets
- Backups and restore
- Notifications
- Application deployments
- Git integration
LaterPlanned
Applications and plugins
The long-term direction is a complete control layer for self-hosted infrastructure, without becoming a cloud provider or Kubernetes distribution.
- Rollback workflow
- Plugin system
- Application stacks marketplace
- Multi-server management
100+ services ready to deploy.
A catalog organized into 30 categories. Databases, AI, monitoring, productivity, media, and everything in between.
Straight comparison
Where Kiban fits.
It sits between fully manual self-hosting and managed platforms: more structure than raw Docker, more ownership than a cloud dashboard.
Area
KibanOS
Manual Docker
Managed cloud
Where it runs
KibanOn your own Linux server, VPS, homelab, or dedicated machine.
Manual DockerAnywhere Docker runs, but you assemble the operating layer yourself.
Managed cloudInside the provider’s cloud or control plane.
Configuration model
KibanGuided service setup with Docker and Compose still visible underneath.
Manual DockerHand-written Compose files, notes, scripts, and provider docs.
Managed cloudDashboard settings that are often tied to the vendor.
Service catalog
Kiban100+ self-hosted apps organized behind one workflow.
Manual DockerEvery service has its own README, defaults, and upgrade path.
Managed cloudLimited to the services the platform chooses to expose.
Control and lock-in
KibanPlain containers on infrastructure you control.
Manual DockerMaximum control, but more maintenance burden.
Managed cloudConvenient, but workloads and data flow through someone else’s system.
KibanOS is not a cloud provider, a managed hosting platform, or a Kubernetes distribution. It is a tool that simplifies the infrastructure you already control.