Comparison of Hosting Providers
There are many different hosting providers that allow you to run your bot. It can sometimes be hard to keep track of how much they cost and how good their performance is. This is why the grammY community is collecting their experiences on this page.
What Is a Hosting Provider?
In order to keep a bot online 24 hours a day, you need to run a computer 24 hours a day. As mentioned in the introduction, you most likely don’t want to do that with your laptop or home computer. Instead, you can ask a company to run the bot in the cloud.
In other words, you just run it on someone else’s computer.
Comparison Tables
Please click the edit button at the bottom of the page to add more providers or to edit existing ones!
We have two comparison tables: one for serverless hosting and PaaS and one for VPS.
Serverless and PaaS
Serverless means that you do not control a single machine on which your bot is run. Instead, these hosting providers will rather allow you to upload your code, and then start and stop different machines as necessary to make sure that your bot always works.
The main thing to know about them is that on serverless infrastructures you are required to use webhooks. Most of providers below will have issues when you try running your bot with polling (bot or grammY runner) on them.
On the other hand, PaaS (Platform as a Service) provides a similar but more controllable solution. You can choose how many machine instances will be serving your bot, and when they are running. Using polling is also possible with PaaS if the provider you choose lets you keep exactly single instance running at all times.
Serverless and PaaS have a downside that doesn’t provide you with a persistent storage by default, such as a local file system. Instead, you will often have to have a database separately and connect to it if you need to store data permanently.
| Name | Min. price | Pricing | Limits | Node.js | Deno | Web | Notes |
|---|---|---|---|---|---|---|---|
| Deno Deploy | Free | $20/mo subscription for 5M req and 100 GB; $2/1M req, $0.5/GB network | 1M req | ❌ | ✅ | ❌ | |
| Fly | Free | $1.94/mo subscription for shared-cpu-1x and 256 MB RAM, $0.02/GB network | 3 shared | ✅ | ✅ | ❓ | |
| DigitalOcean Functions | Free | $1.85/100K GB-s | 90K GB | ✅ | ❌ | ❓ | |
| Cloudflare Workers | Free | $5/10M req | 100K req | ❌ | ✅ | ✅ | |
| Vercel | Free | $20/mo subscription | Unlimited invocations | ✅ | ✅ | ✅ | |
| Scaleway Functions | Free | €0.15/1M req, €1.2/100K GB-s | 1M requests | ❓ | ❓ | ❓ | |
| Scaleway Containers | Free | €0.10/100K GB-s, €1.0/100K vCPU-s | 400K GB | ❓ | ❓ | ❓ | |
| Vercel Edge Functions | Free | $20/mo subscription for 500K | 100K req | ✅ | ❓ | ✅ | |
| serverless.com | Free | ❓ | ❓ | ❓ | |||
| Heroku | $5 | $5 for 1,000 dyno hours/mo | 512MB RAM | ✅ | ✅ | ❓ | Deno is supported by a third |
| DigitalOcean Apps | $5 | ❓ | ❓ | ❓ | Not tested | ||
| Fastly Compute@Edge | ❓ | ❓ | ❓ | ||||
| Zeabur | $5 | $5/mo subscription | 2GB RAM, Unlimited invocations | ✅ | ✅ | ✅ |
VPS
A virtual private server is a virtual machine that you have full control over. You can usually access it via SSH. You can install any software there, and you are responsible for system upgrades and so on.
On a VPS, you can run bots using both long polling or webhooks.
Check out the tutorial on how to host grammY bots on a VPS.
| Name | Min. price | Ping to Bot API | Cheapest option |
|---|---|---|---|
| Hostinger | $14 | 1 vCPU, 4 GB RAM, 50 GB SSD, 1 TB | |
| Contabo | 15 ms 🇩🇪 Nuremberg | ||
| DigitalOcean | $5 | 1-15 ms 🇳🇱 AMS, 19 ms 🇩🇪 FRA | 1 vCPU, 1 GB RAM, 25 GB SSD, 1 TB |
| Hetzner Cloud | €4.15 | ~42 ms 🇩🇪 | 1 vCPU, 2 GB RAM, 20 GB SSD, 20 TB |
| IONOS VPS | €1 or $2 | 15 ms 🇩🇪 Baden-Baden | 1 vCPU, 0.5 GB RAM, 8 GB SSD |
| Scaleway | €~7 | 2 cores, 2 GB RAM, 20 GB SSD | |
| MVPS | €4 | 6-9 ms 🇩🇪 Germany | 1 core, 2 GB RAM, 25 GB SSD, 2 TB |
Unit Explanations
Base Units
| Unit | In Words | Explanation |
|---|---|---|
| K | thousand | 1,000 of something. |
| M | million | 1,000,000 of something. |
| € | Euro | The currency EUR. |
| $ | US-Dollar | The currency USD. |
| req | request | Number of HTTP requests. |
| vCPU | virtual CPU | Computing power of one virtual CPU, a part of a real CPU. |
| ms | millisecond | 0.001 seconds. |
| s | second | One second (SI unit for time). |
| min | minute | One minute, 60 seconds. |
| h | hours | One hour, 60 minutes. |
| day | day | One day, 24 hours. |
| mo | month | One month, approximately 30 days. |
| GB | gigabytes | 1,000,000,000 bytes of storage. |
Example Unit Combinations
| Unit | Quantity | In Words | Explanation |
|---|---|---|---|
| $/mo | cost | US-Dollars per month | Monthly cost. |
| €/M req | cost | Euros per million requests | Cost for handling one million requests. |
| req/min | throughput | requests per minute | Number of requests handled in one minute. |
| GB/s | throughput | gigabytes per second | Number of gigabytes transferred in one second. |
| GB-s | memory usage | gigabyte seconds | One gigabyte used for one second. |
| GB-h | memory usage | gigabyte hours | One gigabyte used for one hour. |
| h/mo | time fraction | hours per month | Number of hours in one month. |
| K vCPU-s/mo | processing time fraction | thousand virtual CPU seconds per month | Monthly seconds of processing time with one virtual CPU. |