plint deploys any directory to a global CDN. Sites, documents, reports, artifacts — if it's a file, it's live in seconds.
Why plint
You have files. You want them online. That shouldn't require a platform account, a config file, or a build pipeline. plint is one command. No dashboard. No YAML. No middleman.
Point plint at a folder or a file. It's live on a global CDN. No config. No build step. No dashboard.
Re-deploys take seconds. Unchanged files stay put. SHA-256 diffing.
First deploy auto-provisions storage and CDN. No setup steps. No portal.
Pay for what you use — storage at $0.01/GB/mo, bandwidth at $0.01/GB. No tiers. No per-seat pricing. No surprises.
Bring your own Bunny.net API key. No plint account. No middleman. You own the infrastructure.
Stable --json output. No interactive prompts. Built for Codex, Claude Code, and CI.
Workflow
Save your Bunny.net API key. Stored locally, never sent to us.
Point at a directory or file. CDN, caching, and SSL are automatic. You get a URL.
For you and your agents
Human-readable output at the keyboard. Stable JSON when your agent is driving. Same tool, same command — just add --json.
Global CDN
Your files are cached at 100+ points of presence worldwide. Fast for every visitor, everywhere. No CDN configuration required.
What people deploy
If it's a file, plint puts it on the internet. Same command, whatever you're deploying.
Portfolios, landing pages, blogs
Proposals, reports, client deliverables
Generated HTML reports, data visualizations
Compiled assets, release bundles
API docs, wikis, knowledge bases
If it's a file, plint puts it online
Almost free
No plint account. No plint billing. You pay Bunny.net directly for storage and bandwidth — and new accounts get $25 free.
Open source. Free forever.
--json agent outputYour infrastructure. Your billing.
Commands
Every command supports --json. Nine commands. That's it.
See all commands on GitHub →
Get Started
One line. Five seconds. You're live.