Hi — I'm building BotShade.
A short introduction from the solo developer behind BotShade — why this product, what it's becoming, and what I'm trying to make a little less frustrating.

|
|
Published: May 3, 2026Hello.
Thanks for finding this page.
I’m Tettu, the developer building BotShade.
Going forward I’ll be writing more technical pieces too — operations notes, incident reports — but if everything is technical, the thinking behind the product gets lost. So I wanted a place for lighter posts like this as well.
Table of contents:
About me
I’ve been running Discord servers and building Discord bots since I was a student, and I’ve thought, more times than I can count, “why does building a bot have to be this stressful?”
Endless errors in Python (discord.py), patch after patch, and by the time it actually works I’m already burnt out. As a break I tried a few existing no-code bot makers — and each time something didn’t quite reach where I wanted, so I’d end up writing the thing myself anyway. That cycle, again and again.
BotShade started from that personal frustration.
Why I’m building BotShade
There isn’t a grand mission statement.
I just want to strip out the unnecessary stress involved in building a bot, as much as possible.
Trying existing services, I’d notice small things adding up — getting tired by an English-only UI every time, guessing my way through unintuitive settings panels, feeling that the same kind of bot would come out no matter where you built it. Lots of tiny snags piled on top of each other.
There’s a binary right now: people who can code DIY their way through, and people who can’t aren’t even at the door. I want that gradient to be a little smoother. I want a place where you can think of an idea, shape it, run it — and have that simple loop feel good to keep doing.
That’s the unglamorous reason I sit and write code every weekend.
What’s next
BotShade is still a small product.
I can’t offer enterprise SLAs or zero-downtime guarantees right now. Instead, I’m putting weight on keeping operations as open as possible:
- Live status is always public at status.botshade.com
- When something breaks, the incident report goes up — no hiding
- Maintenance is announced ahead of time on Discord, the dedicated page, and in-site notifications
- On this blog too, I’ll write about progress and what I’m thinking, plainly
Features may not ship at a fast pace.
But I want this to be a product without lies.
If you’d like
If you try BotShade and have any reactions, please drop by the Discord server and tell me anything.
Praise, complaints, feature requests — all of it is fuel.
I’ll keep writing here, gently and honestly.
Thanks for being here.