01 · GIT PUSH
Connect a repo or image
GitHub or any Docker image. Push to main and the build starts on its own.
Early access · EU nodesEarly access · EU nodes · more regions later
Push to deploy.
Pay for what runs.
The runtime platform for AI-native companies: a build from every commit, every service in its own sandboxed kernel, databases wired in — billed by the minute from a prepaid balance, on EU nodes.
webweb-4f2aapiapi-9c1e
postgres:5432 · 1 GB volume$23.4029 days runway · pauses at $0Runs
136 templatesEU nodes
The route
Three marks from push to production
Every commit sails the same chart. No YAML to write, no cluster to babysit.
01 · GIT PUSH
Connect a repo or image
GitHub or any Docker image. Push to main and the build starts on its own.
02 · BUILD & ISOLATE
Railpack builds it, every service in its own sandbox
Zero-config builds for Node, Python, Go, Ruby and PHP. Each service runs in its own gVisor or Kata sandbox.
03 · LIVE
Live on your domain
TLS domain, logs, metrics, backups — included. Point a CNAME at us and the certificate is issued for you.
What's on board
Built for the bill you can actually read
Everything a small team needs to run in production, priced from a balance you already paid.
Prepaid balance & spend limits
You can't wake up to a surprise bill. Top up, set a ceiling per workspace, and services pause at zero instead of charging you.
Pay how you want
Card, PayPal or crypto. Every top-up becomes usage credit; nothing is charged behind your back.
Databases in one click
Postgres, Redis, MySQL, Mongo. Provisioned next to your service, connection string injected as an env var.
app.skiffly.dev/ harbour
webOnline
web-4f2a · 512 MBpostgresOnline
pg 16 · :5432 · 1 GBDeploy · weba1f9c2e · main
- Initialization00:03
- Build00:31
- Deploy00:14
Live00:48
$23.4029 d runway
Project · harbourlive
webapipostgres$23.4029 days runway
Spend limitSpend limit · this month$26.60 of $50.00
worker · sleeping · $0.00 / hpauses at $0pauses at $0 — never overdrafts
App Sleeping
Idle apps cost nothing. A service with no traffic goes to sleep and wakes on the first request.
Backups included
Daily snapshots of every volume and database, kept off-node in the EU. No extra plan.
Railway-compatible API, CLI and MCP
Same shapes, same verbs. Move a project over with skiffly import --from-railway
Pricing
Pay for what runs. Nothing else.
Plans include usage credit. Usage is metered by the minute from your prepaid balance.
Free
$0
For trying the chart
- 1 app + 1 database
- 512 MB RAM, 1 vCPU
- Sleeps after 10 min idle (static sites never sleep)
- No card required
- 50 vCPU·h a month (100 once verified)
Hobby
Most chosen$5/mo
Includes $5 of usage
- Unlimited services and projects
- Up to 8 GB RAM, 8 vCPU per service
- Custom domains, daily backups
- App Sleeping optional
Pro
$20/mo
Includes $20 of usage
- Everything in Hobby
- Up to 32 GB RAM, 32 vCPU per service
- Team seats and spend limits
- Priority support
512 MB · 0.25 vCPU · 1 GB disk= $7.87 / month— or$0 on Free while it sleeps
See pricingCompare
Same workflow, different terms
PaymentSkiffly · Card, PayPal or cryptoRailway · Card
BillingSkiffly · Prepaid balance, hard spend limitRailway · Postpaid, usage-based
HostingSkiffly · Sandboxed kernel per service, EU nodes we ownRailway · Not disclosed, US-first regions
Competitor details as of 2026, from their public pricing pages. Corrections welcome.
FAQ
Questions we get asked
Something else? Write to support@skiffly.dev. A person answers.
How is this different from Railway?
Same workflow: connect a repo, get a running service with a domain. The differences are in the plumbing. Skiffly runs on its own EU nodes instead of a hyperscaler, gives every service its own sandboxed kernel (gVisor by default, a Kata microVM on request), takes PayPal and crypto as well as cards, and works from a prepaid balance so a bill can never surprise you. It is also a smaller, newer product with fewer regions and integrations.
What does early access mean?
The platform is running and billing is real, but the product is young: one region, a short list of templates, docs still being written. You get a person on support and a say in what we build next. Prices will not go up for early accounts.
Where is my data?
On our own servers in Helsinki, Finland, with more EU regions planned. Volumes, databases, logs and backups do not leave the EU.
I am not in the US or EU. Can I pay?
Yes. We accept cards, PayPal and stablecoins (USDT, USDC) plus BTC and ETH. Crypto top-ups are credited to your balance at the exchange rate at the moment of confirmation, with no extra fee from us.
What are the limits?
Free: one app and one database, each with 512 MB and 1 vCPU; the app sleeps after 10 minutes without traffic — static sites (HTML, Vite, Astro, Hugo…) are the exception and never sleep. Hobby: up to 8 GB and 8 vCPU per service, unlimited services. Pro: up to 32 GB and 32 vCPU per service. Volumes up to 250 GB each. Need more? Write to us and we will raise it. Free also has a CPU quota: 50 vCPU·h per billing period (100 once your account is verified); when it runs out, services pause until the next period and a paid plan removes the quota.
Do I need a card to start?
No — you sign in with GitHub and deploy. New accounts start unverified: 1 project, 2 services, 1 vCPU and 1 GB in total, 5 builds an hour, no TCP proxies or cron, and 50 vCPU·h of CPU a month on Free. Verification lifts all of that: a GitHub account older than 30 days with public activity is verified automatically at sign-in, or you top up $5 — the money stays on your balance as credit and the plan stays Free. Verified personal workspaces also get a one-off $5 welcome credit for usage beyond what a plan includes (it does not pay for the subscription itself). Signed up with Google or e-mail? Link a GitHub account older than 30 days with public activity in Settings → Security and the credit is added right away.
What happens when my balance runs out?
We warn you at 20% and at zero. After that you have a 3-day grace period during which everything keeps running. If the balance is still empty, services are paused, not deleted, and your data and volumes stay put. Top up and everything resumes. We never send an invoice for a negative balance.
Can I bring a Dockerfile or a private image?
Yes. If the repo has a Dockerfile we build it as is. You can also deploy directly from a public registry image (private registries are coming) and set the start command and health check in the service settings.
