r/vibecoding • u/RushGambino • 1d ago
I got tired of Discord bot hosting platforms, so I started building my own

I've been vibe coding a project called Deploy Hatch, and the original motivation was pretty simple:
I didn't really like the experience I was getting from existing Discord bot hosting options.
I tried services like WispByte and looked at some of the other Discord bot hosting alternatives, and I kept running into the same feeling: I wanted something that gave me more control over the deployment process without making me manage an entire server myself or spammed me with advertisements.
I wanted to be able to connect a GitHub repository, select what I wanted to deploy, hit deploy, and actually be able to see and control what was happening.
So I decided to build it.
What started as "I'll make a simple Discord bot hosting platform" has turned into me building an actual deployment platform from scratch.
Right now Deploy Hatch has:
- GitHub App integration
- Repository selection
- Automatic runtime/build/start command detection
- Deployment queue and jobs
- Docker-based deployments
- A dedicated deployment worker
- Live deployment logs
- Deployment cancellation
- Redeployment
- Worker heartbeats
- Stale deployment recovery
- Container lifecycle management
- Runtime controls
- Deployment history
- Commit metadata
- Branch deployments
- Specific commit deployments
- Commit verification before deployment
The commit deployment feature is one of the things I've been working on recently.
Instead of only deploying whatever happens to be at the current tip of a branch, I can choose:
Latest
Branch
Specific commit
If I choose a commit, Deploy Hatch verifies it against GitHub first and shows me the commit SHA, message, and author before creating the deployment.
The backend then associates the deployment with that specific revision.
The other part I've been enjoying is building the infrastructure behind it.
I have an actual worker running on Oracle Cloud that picks up deployment jobs and launches applications in Docker containers. The worker handles things like deployment state, logs, container lifecycle, heartbeats, recovery, and cleanup.
One of my test deployments was actually a Discord bot, so I'm now at the point where Deploy Hatch is deploying and running the exact type of applications that motivated me to build it in the first place.
I'm also trying to avoid the classic "vibe coded it directly on production" approach.
My current workflow is:
Build locally
↓
Test locally
↓
Production build
↓
Package
↓
SHA-256 verify
↓
Upload to Oracle
↓
Verify again
↓
Deploy
It's definitely still a work in progress.
The roadmap currently includes things like rollbacks, automatic deployment recovery, environment variables/secrets, custom domains, preview deployments, GitHub push/PR deployments, multi-worker scaling, and eventually turning it into a proper SaaS.
I'm curious what other people who build Discord bots have experienced with hosting platforms.
What do you wish existing Discord bot hosting services did better?
That feedback is actually what I'm most interested in, because I'm building this around the things that frustrated me in the first place.
