RUNTAINER — Every container on your machine, finally within reach

00 / WHY

Containers won.
The interface didn't.

Somewhere between docker ps and a wall of YAML, we accepted that running software on your own machine had to feel like piloting a submarine through a keyhole. The power is extraordinary. The experience is not.

RUNTAINER is our answer: one calm, dark, honest window onto everything your host is running. It scans your machine by itself. It shows you each container, alive, with its access link right beside it. And when you want more — a database, a cloud, a mail server, an entire dev hub — it is never more than one click away.

It is built for the person who has never touched Docker and the engineer who lives in it. One size fits user and developer.

— The Calizu, Inc. team

1.Command to install

5sAuto-scan interval

20+Deployable apps & images

MITOpen source, forever

01 / THE LOOP

See it. Deploy it.
Move it.

The whole life of a container, in one gesture.

Most tools cover a slice of the story — a CLI for starting, a registry for pulling, a prayer for migrating. RUNTAINER treats your containers as a continuous loop you can enter at any point.

Step 01 — See

Your host, scanning itself

RUNTAINER watches the Docker socket and refreshes every five seconds. Every container appears as a living window — a snapshot-style preview, its uptime, its CPU, memory and network — with the access link sitting right beside it. Click, and you're inside.

Step 02 — Deploy

From anywhere, to running

Pull an app from the marketplace, boot a bare Linux base image, paste a Git repository and let it build in its own isolation, or fire a complete one-click platform. Every path ends the same way: a running container and a link to open it.

Step 03 — Move

Pack it all into one file

When it's time for a new machine, RUNTAINER bundles every Git-deployed container — the manifests, the configs, and RUNTAINER itself — into a single portable file with a restore script. Drop it in the home folder of the new machine, run it, and your world reassembles.

02 / PRODUCT

Five ways in.
One way out: running.

01 / COMMAND CENTER

Every container, alive on one screen.

Open RUNTAINER and it has already done the rounds. Each container renders as a window with its own snapshot-style live preview — dashboards look like dashboards, terminals look like terminals — flanked by the thing that matters most: the link to open it.

Automatic host scan, refreshed every five seconds
Live CPU, memory and network readouts per container
One-click start, stop, restart, remove — no flags to memorize
Access link with copy and open, always beside the preview

auto-scanlive statsaccess links

RUNTAINER containers view — grid of running containers with live previews and access links — runtainer / containerslive · 5s scan

02 / MARKETPLACE

A registry you can actually browse.

Docker Hub, GHCR, LinuxServer.io, Bitnami — the marketplaces you already trust, presented as shelves instead of search boxes. Pick a template, fine-tune the ports, CPU, memory and restart policy in a friendly dialog, and deploy.

Or start from nothing: Ubuntu, Debian, Alpine, Fedora, Arch or openSUSE base images, one click each, ready to become whatever you need next.

nginx, Postgres, Redis, Grafana, Home Assistant, Nextcloud, Jellyfin, Portainer
Six Linux base images for clean-slate builds
Advanced specs — CPU shares, memory ceiling, env vars, networks, read-only rootfs

4 registriesbase imagesfine-tuning

RUNTAINER marketplace — app templates and Linux base images from multiple registries — runtainer / marketplace4 registries

03 / GIT DEPLOY

Paste a repo. Get a running container.

This is the one developers feel in their chest. Drop any Git URL into RUNTAINER and it clones, builds and launches the project as a standard Docker container — on its own isolated bridge network, with its own labels, its own blast radius.

Branch and build-strategy selection
Isolated git-net-* network per project
Streaming build log, ending in a ready access link
Every Git container is tracked, labeled and migratable

clone → build → runisolated networksbuild logs

RUNTAINER Git deploy — repository URL form with isolation toggles and streaming build log — runtainer / git deployisolated

04 / MIGRATION

Your entire setup, in one file.

Moving machines used to mean a weekend. RUNTAINER packs every Git-deployed container on the host into a single bundle — manifests, environment, a generated restore script — and always includes RUNTAINER itself, so the new machine boots straight back into the same command center.

Choose exactly which containers travel
Optional volumes, optional encryption
Restore script installs Docker if the new machine doesn't have it
Drop the file in a home folder, run one script, done

.rtpack bundlerestore.shruntainer included

RUNTAINER migration — select git containers and create a portable bundle with restore script — runtainer / migrationone file

05 / ONE-CLICK PLATFORMS

Whole platforms,
one button.

Not thin wrappers — complete, prepackaged stacks. Each one pulls its images, wires its networks, and hands you a link to a finished platform.

RUNTAINER one-click apps — complete platforms deployable with a single button — runtainer / one-click appscomplete stacks

:8088

Nextcloud Hub

Your own cloud — files, calendar, contacts, office — deployed as a complete stack and opened from one link.

:8443

Mail Platform

A real email server with the complete software included. One click and your domain has a post office.

:8181

Web Host

A ready web hosting client — sites up, served, and reachable before your coffee cools.

:3100

Chat Client

A private chat home for your team, family or community — self-hosted by default.

:3000

Dev Hub

A development cockpit in a container — editor, tooling and runtime, nowhere near your host system.

:3101

Monitoring

Dashboards and metrics for everything else on this page — watch it all from one pane.

06 / PHILOSOPHY

One size fits everyone.

For the user

01No terminal required. If you can click a link, you can run Nextcloud, a mail server, or a chat platform.
02Instant access — every deployed thing is one click from open, always with its link beside it.
03Demo mode: explore the entire product with a simulated host before Docker ever touches your machine.
04Moves with you — your whole world migrates to a new computer as a single file.

For the developer

01Git URL to running, isolated container — labeled, networked, logged, and migratable.
02Fine-tune CPU, memory, restart policy, env vars, networks and read-only rootfs from the GUI.
03Real Docker under the hood — standard containers, no lock-in, no proprietary runtime.
04MIT-licensed and readable: a React front end, a small Express bridge to the Docker socket. Fork it, shape it, ship it.

07 / POSSIBILITIES

What will you run?

The Homelabber

A spare laptop becomes a household cloud.

Jellyfin for movie night, Home Assistant for the lights, Pi-hole for the ads, Nextcloud for the family photos. Each appears on the RUNTAINER screen with its little window and its link — and when the laptop dies, the migration bundle rebuilds the household on the replacement before anyone notices.

The Indie Maker

Every side project, running and reachable.

Push to Git, paste the URL, watch the build log stream to its final line: access link ready. Twelve experiments can live side by side, each in its own isolation, each one click from a demo you can send to a friend.

The Team Lead

Onboarding that fits in a chat message.

New engineer? Hand them the migration bundle. The restore script installs Docker if needed, lays RUNTAINER into their home folder, and rebuilds every service the team depends on. The dev hub is running before the HR paperwork is.

The Educator

Thirty students, thirty identical labs.

Demo mode lets a classroom explore container concepts on machines without Docker at all. Then one bundle provisions every workstation with the same containers, the same ports, the same starting line.

The Agency

Client handovers without the handover document.

Build the client's stack — site, mail, monitoring — as RUNTAINER containers. At handover, export the bundle. Whatever machine it lands on, RUNTAINER arrives with it, so the client inherits the same calm control panel you used.

The Future

Where this goes next.

The architecture is deliberately simple — a React window, a small bridge to the Docker socket — so the community can take it anywhere: richer marketplace catalogs, container templates shared as links, fleet views across many machines. Forks aren't just welcome; they're the point.

08 / INSTALL

Running in
sixty seconds.

the easy way

# clone, then let the installer do everything

$ git clone https://github.com/CALIZU/RUNTAINER.git

$ cd RUNTAINER && bash install.sh

# checks Node 20+, checks Docker, builds, and starts on :3000

# no Docker? it offers demo mode instead of an error

the docker way

$ docker build -t runtainer .

$ docker run -d -p 3000:3000 \

-v /var/run/docker.sock:/var/run/docker.sock runtainer

# or: docker compose up -d (compose file included)

Then open http://localhost:3000 — your containers are already there.

RUNTAINER.

Containers won.The interface didn't.

See it. Deploy it.Move it.