A home for your whole stack.
Containers, Compose projects, images, volumes, and networks. Open logs, a shell, or files without losing your place.
Explore the runtimeSMALL RUNTIME. BIG INDEPENDENCE.
A lightweight container runtime with familiar Docker tools and public links on infrastructure you control. Your dev environment shouldn’t double as somebody else’s cloud funnel.
❯ docker compose up -d
✓ 3 containers started
❯
INFO Starting nginx
INFO Listening on :80
200 GET /
200 GET /assets/app.js
200 GET /api/status
▌INTERACTIVE PRODUCT ILLUSTRATION Try the sidebar or Share ↗
KEEP YOUR
muscle memory.
01 / BUILT TO GET OUT OF YOUR WAY
Run your stack, inspect what’s happening, and get back to building. One focused workspace for the things you do every day.
Containers, Compose projects, images, volumes, and networks. Open logs, a shell, or files without losing your place.
Explore the runtimeA Rust engine and native desktop integration. Linux runs directly on your kernel. macOS uses Apple’s virtualization. Windows uses WSL2.
No Electron. No bundled browser.Keep your Dockerfiles, Docker CLI, Compose workflows, and image registries. Skiff gives them a new engine.
02 / WHY WE FORKED KIRI
Kiri is open source. Its built-in sharing still comes with a house account, a house address, and house rules. We think your runtime should serve your workflow, not recruit it.
01 / THE ACCOUNT
02 / THE ADDRESS
runkiri.cloud. Reserved
names occupy slots in your plan.
03 / THE RULEBOOK
04 / THE DEPENDENCY
Both projects run local containers without a cloud account. This
comparison is about their built-in public sharing. Skiff is in
early development, and Cloudflare sharing requires
cloudflared.
Checked November 18, 2026 against Kiri Share, Kiri Cloud, and Skiff’s sharing guide.
04 / LESS CEREMONY. MORE BUILDING.
Start with the commands you know. Add a public link when you need one. The app and CLI work with the same Skiff engine.
# With Skiff installed and the engine running
docker --context skiff run -d \
--name web -p 8080:80 nginx:alpine
skiff share 8080
Your local web server, ready for a public preview.
05 / CHOOSE YOUR PLATFORM
One independent project. Three operating systems. Your next stack starts here.
Apple’s Virtualization.framework, a native desktop window, and a home in your menu bar.
macOS 14 or later · Apple Silicon and Intel
The first public release is being prepared. Preview artifacts are available for Linux and Windows through GitHub Actions and require a GitHub login. Build macOS from source while its release is prepared.
Yes. Skiff provides a Docker-compatible API and a
skiff Docker context. Keep your existing Dockerfiles,
CLI, and Compose workflows. Compatibility is an ongoing project;
see the
feature list and known limitations
for the exact supported behavior.
Only for sharing on your own domain. Temporary Quick Tunnel links
don’t require an account or domain. Both sharing modes require
cloudflared on your computer. Custom domains must be
managed in your Cloudflare account. Local containers work without
Cloudflare.
Skiff stops its local tunnel process, so that share stops serving your app. Your Cloudflare tunnel and DNS record remain in your account for reuse. You can manage or delete those resources in Cloudflare. Treat a public link as public access to the service you choose to expose.
Skiff is in early development. Use the preview builds to try local workflows and share feedback. Published macOS releases will use Developer ID signing and notarization; Windows installers are currently unsigned. Review the known limitations before depending on Skiff for important workloads.
Skiff began after Kiri’s maintainer declined our optional Cloudflare Tunnel integration for user-controlled hosting and domains. The maintainer later expressed interest; our proposal remains closed and unmerged as of November 18, 2026. Skiff continues independently with that control built in, while retaining upstream’s Apache-2.0 attribution. See the comparison and the full story.
YOUR CONTAINERS. YOUR INFRASTRUCTURE. YOUR LINKS.