Skip to content
A night harbour: a loaded skiff leaves the pier towards the lighthouse

For vibe coders

You built it — now ship it.

Five minutes from a folder of code to a working site: you get an HTTPS address immediately, and your own domain whenever you want it. Need a database or a bot later? They are right here — no moving out.

How it looks

Three steps, no servers to configure

No Docker, no nginx, no need to know what “deploy” means. Just the code — including the code your assistant wrote a minute ago.

A dockside crane lowers a glowing crate into a small skiff moored at a night pier
01 · Code

Hand over a folder or a repo

Run npx skiffly up in the project folder and it uploads. Have GitHub? Connect the repository and every push ships itself.

A boat shed lit warm amber from inside, a skiff on the slipway with a few sparks and a teal glow
02 · Build

We build it for you

We detect Node, Python, Go, PHP or a static site and build it without a line of config. Bring your own Dockerfile if you prefer.

A lighthouse sweeps its beam over a skiff with a teal sail moored at a jetty with a lit signpost
03 · Online

An HTTPS address right away

Your site opens at name.skiffly.cloud with a certificate. Your own domain is two DNS records and we walk you through them; static sites never sleep on the free plan.

terminal
# в папке, которую сгенерировал ассистент
npx skiffly up

✔ uploaded 1.2 MB
✔ build finished in 38s
✔ live at https://myapp-4f2a.skiffly.cloud
When you outgrow static

Then comes everything static hosts do not do

A week in, the project has a database, a login and a background job. That is usually where you start gluing three services together. Here they are all one click apart.

A database in one click

Postgres, MySQL, Redis or Mongo from a template; the connection string lands in your app's variables automatically.

Bots and background jobs

A Telegram bot, a scraper, a queue, a schedule — an ordinary process with no execution time limit.

Your domain with TLS

Add the domain, point a CNAME at us, and we issue and renew the certificate.

No surprise bill

The platform runs on a prepaid balance: when it runs out, services pause instead of running up a debt. You can also set a spend limit.

Free

Nothing to pay while the project is small

Plans and prices
  • One service: 512 MB of memory, 1 vCPU, a volume up to 1 GB
  • An *.skiffly.cloud address with HTTPS, plus your own domain
  • Static sites never sleep; an app with a process sleeps after 10 idle minutes and wakes on the first request
  • 50 vCPU·h of CPU a month (100 once your account is verified)
  • No card: sign in with GitHub, Google or an e-mail link
Questions

The short version

Do I need GitHub?
No. You can upload the folder with npx skiffly up — no repository required. GitHub only matters if you want the site to update itself on every push.
What if I am not comfortable with a terminal?
Ask your assistant: Claude Code, Cursor and Codex can deploy to Skiffly themselves through our MCP server — just say “ship this project”. See the [MCP guide](/docs/guides/mcp).
Will the site be on my domain?
Right after the deploy it is on our subdomain with a certificate. Your own domain takes a couple of clicks: add it in the dashboard and point a CNAME at us; we issue and renew the certificate.
What does it cost?
Nothing while you fit in the free plan. After that Hobby is $5 a month with $5 of usage already included. Everything is paid from a prepaid balance, so a bill can never surprise you.
Can I deploy straight from an AI editor?
Yes. Connect mcp.skiffly.dev in Claude Desktop, Cursor or Claude Code and the assistant will create the project, deploy it and hand you the link.
What if the project takes off?
Drag the memory and CPU sliders up, add replicas, a database with backups and separate environments. Same buttons, no migration.
Dawn over open water: a skiff with a teal sail heads for the horizon along a dashed chart line drawn on the sea

Show what you made

Five minutes, no card.