Pricing · metered per minute
A plan sets the ceiling per service and includes some usage. Usage is billed per minute of reserved memory, CPU and disk, and drawn from a balance you top up. No invoices, no overage surprises.
Upgrade any time: the difference is prorated for the rest of the billing period. Downgrades take effect at the end of the period.
$0forever
No usage credit
Try a real deploy. One small service, no card.
$5per month
$5 of usage included
Side projects and small production apps.
$20per month
$20 of usage included
Teams and workloads that need headroom.
Move the sliders; every figure comes from the rates below. The last line is the same setup at Railway's list prices.
One service, this month
$16.70on Hobby
We bill reserved memory and CPU per minute. Railway bills memory held and CPU actually used, so a mostly idle service can cost less there than the list price suggests. Hours below 730 model a service that sleeps.
The same on every plan. A service reserves memory and CPU; you pay for the reservation per minute, whether it is busy or idle. Scale it down and the meter slows down.
Monthly usage before the credit included in your plan. 730 hours a month.
| Setup | Reserved | Usage / month |
|---|---|---|
| Static site or small Next.js app512 MB · 0.25 vCPU | 512 MB · 0.25 vCPU | $7.75 |
| API + Postgres + 10 GB volume1 GB / 0.5 vCPU + 512 MB / 0.25 vCPU + 10 GB | 1 GB / 0.5 vCPU + 512 MB / 0.25 vCPU + 10 GB | $24.45 |
| Worker fleet, 4 services4 × 2 GB / 1 vCPU | 4 × 2 GB / 1 vCPU | $124.00 |
On Hobby the first example costs $7.75 minus $5 included, so $2.75 on top of the $5 plan. Free has no subscription and no metering: one app and one database within the Free limits run at $0, and the app sleeps after 10 minutes without traffic. Free is capped at 50 vCPU·h per period (100 once the account is verified).
If you know Railway you know Skiffly. Same shape of product, different trade-offs: fewer regions, cheaper usage, EU-only data, more payment options and stronger isolation.
Railway figures from railway.com/pricing, September 2026. Check their page for the current numbers. A check marks the column with the lower price or the wider option; regions are a real advantage of Railway.
Something else? Write to support@skiffly.dev. A person answers.
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.
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.
On our own servers in Helsinki, Finland, with more EU regions planned. Volumes, databases, logs and backups do not leave the EU.
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.
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.
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.
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.
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.
Upgrades apply instantly and are prorated; downgrades take effect at the end of the billing period.