A hosted custom bot gets you a bot under your own name and avatar in minutes, with someone else responsible for the server, uptime and updates; self-hosting on a VPS gets you full control and custom code, at the cost of writing or maintaining that code and keeping a machine alive yourself. Neither is universally better, they trade the same responsibilities in opposite directions.
What self-hosting on a VPS really involves
- Renting a server. A VPS from any provider, billed on a recurring schedule regardless of how much the bot is actually used.
- Writing or downloading bot code. Either your own, or an open-source project you configure and keep updated.
- Keeping the process alive. A tool like pm2 or a systemd service to restart it after a crash or a server reboot.
- Patching it yourself. Discord.js updates, Node.js version bumps, and security patches on the underlying OS are all on you.
- Being the one who notices it's down. There's no infrastructure watching the bot on your behalf unless you set that up too.
What a hosted custom bot involves instead
You create an application and token in the Discord Developer Portal, the same first step either path needs, and paste that token into a host's dashboard. From there, the host's code and infrastructure run it under your bot's identity. There's no server to patch, no process to keep alive, and no update to apply yourself, the feature set improves whenever the host improves it, not when you find time to pull the latest code.
| VPS self-hosting | Hosted custom bot |
|---|---|
| Exact code, exact behavior, nothing you didn't write or choose | Whatever feature set the host offers, nothing more, nothing less |
| You keep the process alive and patch it | The host's infrastructure does that |
| A recurring server bill, whether the bot is busy or idle | With Noxyr, one free Top.gg vote, no subscription |
| You notice outages, or you don't | The host's monitoring notices, usually before you do |
| Full control over data and where it lives | Data lives in the host's database, under their access controls |
Cost, honestly
A VPS is a recurring monthly cost no matter how much the bot is used that particular month, on top of whatever time you spend keeping it patched. A hosted custom bot's cost depends entirely on the provider, most premium white-label bots charge a subscription for exactly this. Noxyr's Custom Bot is the exception: the entire cost is one Top.gg vote, free, repeated roughly every three and a half days to avoid the grace period ever lapsing.
When self-hosting is the right call
Pick a VPS when you need behavior no existing feature set offers, a custom command, an integration with something outside Discord, logic specific to your community that nobody else would build. It's also the right call if you're already comfortable running a Node process and want that level of control as a default, not an exception.
When a hosted custom bot is the right call
Pick a host when the feature set already covers what you need, tickets, a store, security, giveaways, verification, and you'd rather spend zero time on servers, patches or monitoring. This covers most servers, most shops, and most agencies managing several client servers under one identity.
The middle option people forget: free hosting for your own code
Self-hosting doesn't have to mean a paid VPS. Plenty of free tiers exist for running your own bot code, with the trade-off usually being less reliable uptime, tighter resource limits, or the free tier disappearing without much notice. It's worth knowing that option exists as a third point on this spectrum, closer to a VPS in that you're still running and maintaining your own code, just without the recurring bill. Our free bot hosting guide covers that path honestly, including where it tends to fall short.
Can you switch later?
Yes, and this is the part people don't expect: the application and token from the Developer Portal aren't locked to either path. Resetting the bot's token ends whichever service is currently using it, your own VPS process or a host, instantly. Moving from a VPS to a hosted custom bot, or back, is a matter of resetting the token and pasting it somewhere else, not starting the whole application over.
Common questions
Which one should a first-time bot owner pick? The hosted route, almost always. A VPS is easy to justify in hindsight once you know exactly what custom behavior you need; starting there before knowing that just means paying for a server while you figure out the basics a ready-made feature set already covers.
Is a VPS more reliable than a hosted custom bot? Not automatically. Reliability depends on who's actually watching the process; a host running health-checked infrastructure can be more resilient than a solo VPS with no monitoring set up.
Do I need a VPS to run Noxyr's Custom Bot? No, that's the entire point. There's no server for you to provision or maintain.
Can I move from a VPS to Noxyr's Custom Bot without starting over? Yes. Keep the same application, reset the token, and paste the new one into Custom Bot instead of your own code.
Can I run the same bot on a VPS and a host at once? No, not with the same token. Only one process should be logged in as a bot at a time; resetting the token to move it disconnects wherever it was running before.
Is self-hosting actually free? The code can be free, open source or your own, but the server it runs on almost never is.
See our free bot hosting guide if you're writing your own code, or add Noxyr free to skip the server entirely.