A flat, always-on home for apps that never sleep
Koyeb is a serverless platform: containers and functions that autoscale and can scale to zero, billed by usage in USD. Ruust takes the opposite bet. One flat price per Egg per month in GBP, egress unmetered on every tier, and every Egg kept warm around the clock. If your apps are small and always meant to be on, usage-based pricing is just a tax on being reachable.
Flat price per Egg, in GBP · unmetered egress · no cold starts
Both let you ship a container to production quickly. The difference is the bill and the behaviour at rest. Koyeb meters what you use and can spin idle services down; Ruust charges a fixed monthly price per Egg, never meters egress, and keeps everything running.
| Ruust | Koyeb | |
|---|---|---|
| Pricing model | Flat GBP per Egg, per month. Nano £3, Small £6, Standard £12, Large £24. | Usage-based, tends to bill compute and resources by consumption, priced in USD. |
| Egress | Unmetered on every tier. No egress bill, ever (fair-use rate caps only). | Bandwidth tends to be metered beyond an included allowance. |
| Cold starts | None. Every Egg is kept warm 24/7, no scale-to-zero, no spin-up lag. | Serverless model can scale idle services to zero, so requests may wait on a cold start. |
| Predictability | Same number every month, same price in every region. No surprise invoices. | Bill moves with traffic and usage, which is efficient but harder to forecast. |
| Autoscaling | Manual horizontal scaling with replicas; you choose the size. | Automatic autoscaling, including scaling down to zero, is a core strength. |
| Databases | Managed Postgres and Redis database Eggs with a persistent volume, private to your Coop. | Focuses on stateless services; databases usually come from external providers. |
| Private networking | Eggs in a Coop reach each other by hostname, deny-by-default with explicit peering. | Offers private service networking within your account. |
| Regions | eu-west (London) and us-east (Virginia) live, with Frankfurt and Singapore coming. | Multi-region edge deployment tends to be a headline feature. |
Koyeb details are as we understand them and can change. Always check Koyeb's current pricing and features for the latest.
What you get by switching.
The bill you can actually forecast
Ruust is a flat price per Egg per month in GBP: Nano £3, Small £6, Standard £12 (the popular one), Large £24, or a custom size at £12 per vCPU plus £6 per GB. Koyeb's usage-based approach only bills for what you consume, which is genuinely efficient, but it also means the invoice moves with your traffic. With Ruust you know the number before the month starts.
Unmetered egress, so traffic is never a tax
Every Ruust tier ships with unmetered egress. A busy month costs the same as a quiet one, and a viral day does not become a line item. Usage-based platforms tend to meter bandwidth beyond an allowance, so the more people reach your app the more you pay. We keep per-Egg fair-use rate caps to stop abuse, but there is no volume cap and no egress bill.
Always warm, no cold starts
Ruust keeps every Egg running 24/7. There is no scale-to-zero and no spin-up lag, so the first request after a quiet spell is as fast as the last. Serverless platforms like Koyeb can scale idle services down to save money, which is great for spiky workloads but can leave always-on apps paying a latency cost on wake-up.
Batteries included for small, real apps
Connect a repo, let Nixpacks autobuild (or bring your own Dockerfile), pick a region and size, and you are live on HTTPS in about two minutes with TLS issued in roughly ninety seconds. Managed Postgres and Redis Eggs, private Coop networking, custom domains, health checks and zero-downtime rolling deploys are all part of the flat price.
Where Koyeb is the better fit.
Serverless autoscaling and scale-to-zero
If your workload is spiky or genuinely idle for long stretches, Koyeb's autoscaling and scale-to-zero can be the more economical model. Paying nothing whilst nothing runs, then scaling out under load, is exactly what serverless is good at. Ruust deliberately trades that away to keep apps warm, so bursty or intermittent workloads may suit Koyeb better.
Edge reach and global regions
Koyeb leans into multi-region edge deployment, which usually means more locations and getting compute closer to users worldwide. Ruust runs independent regional cells and, at time of writing, has eu-west and us-east live with more on the way. If broad geographic coverage today is a hard requirement, Koyeb tends to have the wider map.
Functions alongside containers
Beyond long-running containers, Koyeb's serverless model is built for functions and event-driven, per-request execution. If you want to deploy small functions that only run when called, rather than a service that is always on, that is squarely their design and not what Ruust optimises for.
Ruust vs Koyeb, the common questions.
Is Ruust actually cheaper than Koyeb?
It depends on your shape of traffic. For small, always-on apps that serve steady or bursty traffic, Ruust's flat GBP price plus unmetered egress is usually cheaper and always predictable. For workloads that are genuinely idle much of the time, Koyeb's usage-based billing and scale-to-zero can win. Ruust's advantage is that you know the number in advance.
Does Ruust really never charge for egress?
Correct. Egress is unmetered on every tier, so there is no bandwidth bill regardless of volume. We do keep per-Egg fair-use rate caps to prevent abuse, but that is about protecting the platform, not metering your traffic. A viral day does not turn into a surprise invoice.
What about cold starts?
Ruust has none. Every Egg is kept warm 24/7, with no scale-to-zero and no spin-up delay, so response times stay consistent even after quiet periods. Serverless platforms that scale idle services to zero can make the first request after inactivity wait on a cold start.
Can I migrate from Koyeb to Ruust easily?
Usually yes. If you deploy from a git repo, connect it and let Nixpacks autobuild, or bring your own Dockerfile. Pick a region and size, add any managed Postgres or Redis Eggs you need, and you are typically live on HTTPS in about two minutes with TLS issued automatically.