Discord bots first
BotHoster is not trying to be a generic cloud dashboard. The product is shaped around long-running Discord bot processes and the questions bot makers actually ask.
Is it online? What changed? What did it log?
Company / About
A smaller surface
for a specific job.
BotHoster is being built for one deceptively demanding task: keeping Discord bots deployed, observable, and understandable without making every bot maker become a server administrator.
Why this exists
Bot hosting should feel like shipping a bot, not renting a tiny datacenter.
A Discord bot may look simple from the outside, but it still needs a runtime, dependencies, configuration, a persistent process, useful logs, and a sensible response when something fails. BotHoster brings those pieces into one focused workflow.
Many bot makers begin on a laptop. The code works, the bot answers commands, and everything feels finished—until the laptop sleeps or the terminal closes. Moving that bot to a general-purpose server introduces a new stack of work: operating-system updates, process managers, environment files, firewall rules, logs, and restarts.
BotHoster narrows that gap. The intended workflow is to connect a GitHub repository, configure the values the bot needs, and let the platform handle the repeatable hosting steps. The dashboard should show the operational truth without requiring a collection of shell commands.
The public product is currently in early access. That matters: this page describes the direction and the experience we are building, not a claim that every planned workflow is generally available today. If that approach fits how you build, the early-access list is the best place to start.
Product principles
The constraints we choose on purpose.
Specific products can make stronger decisions. These principles keep BotHoster centered on the bot maker instead of the infrastructure underneath.
Clear over clever
Hosting should explain itself. Deployment state, process state, logs, resource choices, and pricing should be legible without a cloud-computing glossary.
Operational detail without operational theatre.
A path for every maker
Developers can bring a repository. People who do not write code are part of the product direction too, through a component-based bot-building workflow.
Code or no code is a product constraint, not a slogan.
Who it is for
From first command to serious community utility.
BotHoster is for people who want to spend more time on what a bot does and less time nursing the process that runs it.
01 / Developers
Bring the repository you already use.
JavaScript and Python are the initial runtime focus. The product direction also includes more languages as the deployment system expands. Git remains the familiar place for code review and version history.
02 / Community builders
Start with the behavior, not the boilerplate.
A component-based builder is part of the product direction for people who know what their server needs but do not want to write and maintain a complete bot codebase.
Keep exploring
The details behind the direction.
bothoster.dev/discord-bot-hosting
Discord bot hosting
See the intended repository-to-runtime workflow.
Read more →bothoster.dev/securitySecurity approach
Read how BotHoster thinks about tokens, isolation, and access.
Read more →bothoster.dev/discordDiscord bot field guide
Understand the platform details every hosted bot depends on.
Read more →Next step
Help shape a bot host that stays focused.
Join early access to hear when BotHoster opens and help us prioritize the workflows bot makers need most.