Overview
What Podos is
Podos is a lightweight container platform. One binary, podos, is the
daemon and the command line. You describe your application in a short
manifest, and podos deploy runs it. There is no Docker, containerd or
Kubernetes underneath: Podos pulls OCI images itself and runs them with
crun.
The goal is simple to state: from a fresh server to your application on HTTPS in under five minutes.
Podos is in early development. Version 0.1 is not released yet: there are no release binaries yet. This site marks every feature as Available (in the code on the main branch; build it from source) or Planned · 0.2 (with the milestone or version that brings it). See Status and roadmap.
Who it is for
- Developers and small teams who want to run their applications on one server they control, without learning Kubernetes.
- Operators who want a small, understandable system: one binary, one state database, one process to watch.
- Anyone who has outgrown a single
docker runbut does not need a cluster.
Podos is not a Kubernetes replacement for large fleets. It aims to give the essential operational experience of an orchestrator (deploy, roll out, recover, logs) on one node first, with a path to a few nodes later.
What it looks like
An application is a directory with a podos.toml (or podos.yaml) manifest:
namespace = "shop"
[service.web]
image = "ghcr.io/example/shop:1.4.2"
replicas = 2
env.DATABASE_URL = "postgres://app:${secret.DB_PASSWORD}@db.internal:5432/shop"
namespace: shop
service:
web:
image: ghcr.io/example/shop:1.4.2
replicas: 2
env:
DATABASE_URL: "postgres://app:${secret.DB_PASSWORD}@db.internal:5432/shop"
Then, on the server:
podos secret set DB_PASSWORD # asks for the value twice, without echo
podos deploy # pulls the image and starts two containers
podos ps
podos logs web
What works today
Available in the code on main (milestones M0 to M5):
podos setupandpodos daemonon one Linux server, as root;- the manifest in TOML or YAML, with environments and per-environment
overrides, checked strictly by
podos manifest validate; - environment values and encrypted secrets, set from the CLI and used as
${env.NAME}and${secret.NAME}; - files per environment (config files, key files, templates), mounted
read-only with
filesandpodos file; podos deployof public images from OCI registries, with every blob verified against its digest;- containers supervised by
conmon, which keep running when the daemon stops or restarts; podos ps,podos logsandpodos down;- private networks per namespace and environment, with service names in DNS;
- the built-in HTTPS proxy:
domainsandtls(auto,self-signed,offor an uploaded certificate withpodos cert); - published ports, volumes, and restart policies;
- health checks, rolling updates and automatic rollback;
- READY and RESTARTS in
podos ps; - remote use over HTTPS with
podos login, contexts and scoped API tokens, andpodos releases; - building from source on the server (
build = ".", see Build from source); - the install script, with a systemd unit, upgrade, rollback and uninstall. It needs a published release, and there is none yet.
See Status and roadmap for the rest.
Principles
- One binary. Daemon, CLI and the web UI (Available) are the same
podos. - Private by default. Each namespace and environment has its own network (Available); nothing is reachable from outside unless you say so.
- Standards at the edges. OCI images, OCI registries and the OCI runtime specification are the compatibility boundary.
- Small enough to understand. Few dependencies, SQLite for state, no extra services to run.
- Secure defaults. Strict input validation, secrets encrypted at rest and kept out of logs, containers with a reduced capability set and a seccomp profile.
Where to go next
- Quick start: run your first container.
- Concepts: namespace, environment, service, release.
- Manifest reference and CLI reference.
- Comparison with Kubernetes and similar tools.