Every app, one dashboard.
Deploy, stop, wake, and manage everything from a clean web UI, or skip it entirely and use the CLI.
Early release: expect some rough edges. Feedback welcome.
#selfHosted/Open Source/Lightweight
Every time I wanted to show someone a demo, it was already gone — killed to free up RAM for the next one. One cheap VPS meant one app. Cloud free tiers work until you hit their framework limits or your app gets purged for inactivity. Existing self-hosted platforms are built for always-on production workloads. Nothing fit what I needed.
So I built LiteBin — entire stack under 58MB. Push from your laptop, no building on the VPS. Apps sleep to zero when idle, wake on the first request. Deploy as many as your disk holds.
Idle Memory Footprint
* Sleep-state RAM only.
vps under load
Think about infra once, so you can build what matters.
LiteBin itself sips memory and idle apps sleep to zero, so the deploy threshold drops to nothing. Spin up the fifteenth experiment; it costs the same as the first.
No traffic? The app's RAM goes back to your VPS. Every idle project costs exactly nothing. No meters, no purge policies, no "inactive app deleted".
A visitor hits the URL, the container starts in the background, the page refreshes into your app. Links you share never die of old age.
Paying users, a live demo, anything where the first second matters: flip that project to always-on. It's a per-project choice you can make anytime.
The core feature, live on real LiteBin instances.
Container Lifecycle
Container stopped
0 MB in use
Waking your app…
Container is running and serving traffic.
One command from any directory. No YAML, no CI config, no Dockerfile needed. Builds happen on your machine. The VPS just runs the result.
Connect your GitHub account once. LiteBin creates the App, writes the deploy workflow into your repo, and sets the secrets itself. Push to deploy.
Add the LiteBin MCP server to Cursor, Claude Code, or any MCP-capable editor. Your agent pairs once, then deploys, verifies, sets env and restarts, end to end. No dashboard visits, no SSH.
l8b init --mcp writes it for youAll three paths authenticate the same way. No SSH keys on your CI or your agent.
# done once, by LiteBin 1 connect github 2 pick a repo — LiteBin writes the rest: workflow .github/workflows/litebin-myapp-deploy.yml action mtsandeep/l8bin-action@v0.2.0 trigger push to main secrets L8B_SERVER + L8B_TOKEN_MYAPP (set for you) # every push after that → code pushed to github → action connects to your litebin server, deploys → site live: https://myapp.l8b.in
no terminal, no dashboard, no ssh. the agent held the keys you approved and nothing more.
The situations that led to LiteBin.
You demoed something on a free tier and moved on. Weeks later, someone actually clicks the link — purged for inactivity. Apps here sleep, they don't disappear. The URL keeps working; it just wakes on the first hit.
Every experiment deserves a URL, but RAM says otherwise — so you keep deleting the old to make room for the new. Idle apps cost nothing here. Stop choosing which project gets to exist.
You build in Cursor or Claude, but shipping still means a dashboard, a card on file, a per-app plan. Give the agent a scoped token instead: it deploys, health-checks, reads logs and redeploys while you stay in the editor.
The VPS runs your stuff; it doesn't need a 500MB+ tenant moving in. LiteBin's whole stack rests under 58MB, manages what's already there, and when one box isn't enough you connect more from the same dashboard.
The client site you shipped last year? The URL is theirs now — redesigned, redirected, or gone one day. Keep your own copies on your VPS instead: a living archive of your freelance work, where idle copies cost nothing and wake the moment someone clicks.
Anything you want live without a per-app bill — a demo, a portfolio, a side project, an internal tool, a small SaaS. Custom domains and TLS included.
Deploy, stop, wake, and manage everything from a clean web UI, or skip it entirely and use the CLI.
Manage a fleet of tiny droplets from a single command center. LiteBin uses mTLS to secure communication between your Manager and Agents.
Your FrankenVPS
All connections secured with mTLS
An honest look. We know our lane.
| LiteBin (L8B) | |
|---|---|
| Idle stack overhead | < 58 MB total resting stack |
| Hosting model | Self-hosted, scale-to-zero, VPS cost only |
| Deploy from laptop | Yes, l8b ship streams the image directly, no registry needed |
| GitHub Actions CI | Yes: GitHub App (workflow & secrets written for you) or a one-curl deploy token |
| Made for | Anything you want live without per-app bills: demos, portfolios, side projects, internal tools, small SaaS |
* Comparisons are approximate
Full comparison visible on wider screens.
LiteBin thrives on tiny, high-value boxes.
These links may earn a small commission at no extra cost to you.
Already have a spare box? Connect it. LiteBin doesn't care where your servers come from. Mix providers freely; each one gives you room for more apps.
Free and open source. Your first app is minutes away.
One command over SSH installs LiteBin on your VPS:
curl -fsSL l8b.in | bash
Linux · macOS · Windows · x64 / arm64
New to LiteBin? View Quick Start Guide →