

It is, compared to AWS, Azure, and Google Cloud. Here’s 2024 revenue to give an idea of scale:
- Akamai - $4B, Linode itself is ~$100M
- AWS - $107B
- Azure - ~$75B
- Google Cloud - ~$43B
The smallest on this this list has 10x the revenue of Akamai.
Here are a few other providers for reference:
- Hetzner (what I use) - €367M
- Digital Ocean - $692.9M
- Vultr (my old host) - not public, but estimates are ~$37M
I’m arguing they could put together a solution with these smaller providers. That takes more work, but you’re rewarded with more resilience and probably lower hosting costs. Once you have two providers in your infra, it’s easier to add another. Maybe start with using them for disaster recovery, then slowly diversify the hosting portfolio.
But far less reliable. If your data center has a power outrage or internet disruption, you’re screwed. Signal isn’t big enough to have several data centers for geographic diversity and redundancy, they’re maybe a few racks total.
Colo is more feasible, but who is going to travel to the various parts of the world to swap drives or whatever? If there’s an outage, you’re talking hours to days to get another server up, vs minutes for rented hosting.
For the scale that signal operates at and the relatively small processing needs, I think you’d want lots of small instances. To route messages, you need very little info, and messages don’t need to be stored. I’d rather have 50 small replicas than 5 big instances for that workload.
For something like Lemmy, colo makes a ton of sense though.