SMALL RUNTIME. BIG INDEPENDENCE.

Run local.
Share on
your terms.

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.

macOS·Windows·LinuxOpen source

LOCAL → ANYWHERE
SkiffLOCAL WORKSPACE

Containers 03

Engine ready
⌄   launchpadCompose project
N
webnginx:alpine
Running
JS
apinode:22-alpine
Running:3000
P
databasepostgres:17
Running:5432
TERMINAL

❯ docker compose up -d

✓ 3 containers started

❯

skiff context3 containers · 1 project↑
YOUR LINK. YOUR DOMAIN.preview.example.com ↗

INTERACTIVE PRODUCT ILLUSTRATION Try the sidebar or Share ↗

KEEP YOUR
muscle memory.

Docker CLI Compose BuildKit OCI images Kubernetes

01 / BUILT TO GET OUT OF YOUR WAY

Everything in reach.
Nothing weighing you down.

Run your stack, inspect what’s happening, and get back to building. One focused workspace for the things you do every day.

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 runtime

Small by architecture.

A 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.

Bring your usual tools.

Keep your Dockerfiles, Docker CLI, Compose workflows, and image registries. Skiff gives them a new engine.

$ docker context use skiff
$ docker compose up -d
✓ You know what to do.
Check compatibility

02 / WHY WE FORKED KIRI

Your localhost deserves better
than a company town.

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

One less club to join.

Kiri Share
A Kiri Cloud account via GitHub is required to share.
Skiff
No Skiff account. Temporary links need no account at all; custom domains use your Cloudflare account.

02 / THE ADDRESS

Your demo. Your name on it.

Kiri Share
Public links live under runkiri.cloud. Reserved names occupy slots in your plan.
Skiff
Use your own Cloudflare-managed domain. Skiff handles the tunnel and DNS setup.

03 / THE RULEBOOK

Skip the runtime’s velvet rope.

Kiri Share
Plans govern concurrent links, speed, and monthly transfer. Some show visitors a Kiri Cloud notice first.
Skiff
No Skiff sharing plan or Skiff visitor gate. Cloudflare’s service limits and terms still apply.

04 / THE DEPENDENCY

Keep us out of the middle.

Kiri Share
Public traffic travels through Kiri’s edge service. Its cloud account holds your links, names, and plan.
Skiff
Sharing goes through Cloudflare, without a Skiff-operated relay. Custom-domain tunnels and DNS stay in your account.

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.

The terminal
feels like home.

Start with the commands you know. Add a public link when you need one. The app and CLI work with the same Skiff engine.

~/your-next-project

# 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.

REAL COMMANDS. ILLUSTRATIVE SESSION.↵
Skiff application icon

05 / CHOOSE YOUR PLATFORM

A smaller runtime.
A bigger sense of freedom.

One independent project. Three operating systems. Your next stack starts here.

DEVELOPMENT PREVIEW

Skiff for macOS

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.

Apache-2.0 source x64 + ARM64 builds No Skiff account required

A FEW THINGS WORTH KNOWING

Open source.
Open answers.

Ask us on GitHub
Can I keep using Docker and Compose?+

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.

Do I need a Cloudflare account?+

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.

What happens when I stop sharing?+

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.

Is Skiff ready for production?+

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.

Why is Skiff an independent project?+

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.

Take the helm.

Get started with Skiff

PRIVACY, PLAINLY

A small site.
A small footprint.

This site sets no cookies and includes no advertising or analytics scripts. Fonts and artwork are served from this site.

To show current downloads, your browser checks the public Skiff releases on GitHub. GitHub and our host, Cloudflare, receive normal connection information such as your IP address. Demo inputs stay in your browser; they are not submitted or saved.

Links to GitHub and Cloudflare take you to their services, where their privacy policies apply.