Built by three people who use it every day.
AI Ticket Bot is an independent product made in Romania. It started as a weekend project, grew past three thousand servers, and was rebuilt from the database up. Here is the story, the team, and what the AI runs on.
- Independent, no investors
- Made in Romania
- Used in our own servers
Live figures
- 3,837
- Servers
- 194K
- Tickets
- 48%
- Solved by AI
- 4.3s
- Avg AI reply
Live from the bot: every server it is in, and every ticket since the first version.
Started as a hobby. Stayed honest.
It started as something to learn on, running off a database file. Everything since is what the servers using it taught us.
December 2024
It went live
Released on 9 December, after months of testing, failed ideas, a couple of name changes and more than one restart from zero. It ran off a database file sitting next to the code.
January 2025
The AI learned to be taught
We rewrote the AI so a server could teach it from inside Discord, and shipped the command to do it. Everything the bot is now grew out of that one change.
Spring 2025
Off the hobby setup
Discord approved the bot in February, which is what let it pass a hundred servers. In March we changed hosts and moved off that local file onto MySQL, and in April the site and the first dashboard went up.
Summer 2025
500 servers, then 1,000
Five hundred in June, a thousand by August. In July we said publicly that seventeen subscribers were paying for it and the project was still in debt, because that was true.
November 2025
Rewritten from scratch
Around 1,700 servers and 60,000 tickets in, the code had turned into ten-thousand-line files nobody should maintain. We threw it out and wrote it again, and the interface became translatable in the process.
December 2025
One year old
1,800 servers and 70,000 tickets on the first anniversary. Along the way the AI broke on every server at once and had to be rebuilt from nothing, which cost us trust we then had to earn back.
April 2026
3,000 servers, and a decision
We had also been building Mico by then. Rather than keep patching forum posts and DMs, we said out loud that the next version would put every ticket inside the server, in channels and threads.
June 2026
V2 shipped
On 27 June the rebuild went live: tickets in plain channels, no DM relay, and a new memory system behind the AI. That is the bot on this site.
Tickets belong in channels.
For the first eighteen months tickets ran on forum posts with a DM relay. Clever, and a tax on every new member. This is what broke, and what the rebuild changed.
What kept breaking
- Members did not know where to type, and replies landed in threads they did not recognise.
- One open ticket per member across every server, because Discord gives one DM channel.
- Members with DMs turned off never saw a staff reply at all.
- Deliveries and notifications failed at both ends of the relay.
- A pipeline so complex that keeping it alive was its own job.
- The AI: accuracy fell short, memory drifted in long tickets, token use was unoptimised.
What the rebuild changed
- Tickets live in plain channels every member already knows how to use.
- Every staff member with the role sees the whole conversation. No relay, nothing to break.
- NEXUS, our own AI system, handles every model call.
- Tighter token budgets on every call.
- A per-server brain your staff teaches over time.
We threw the old code out and started over from the database schema.
Three people. Same Discord servers.
Not a startup with a roadmap and a funding round. The people who built the bot and run it in their own communities, next to thousands of others.
Dani
Founder, bot developer
Started building Discord bots as a weekend habit. Owns the bot, NEXUS and the AI.
Alex
Co-founder, frontend
Owns the dashboard and this site.
Praetorian
DevOps
Keeps the servers up: deployments, reliability, backups.
What the AI runs on
The AI runs on infrastructure we own.
AI features are powered by NEXUS, our own AI platform built for Discord communities. Messages are processed by NEXUS and Anthropic’s model API, which performs the inference, and brain state (server-specific knowledge your staff teaches the bot) stays on our infrastructure. Voyage AI indexes that knowledge so the AI can search it, and Brave runs its web lookups; neither receives the conversation. On Pro, a server can connect its own AI provider instead, and that server’s conversations then go to the provider it chose.
NEXUS lives at nexbrain.dev. We do not sell your data and we do not use it to train outside models.
Read the privacy policy
AI Ticket BotTeach the AI (staff only).
Got it. I will tell members the refund window is 14 days from purchase, that refunds go back to the original payment method, and that they take 3 to 5 business days.
The next ticket
hey can i still get a refund? i bought it like 3 weeks ago
Our refund window is 14 days from purchase, so a purchase from about 3 weeks ago is outside it and I cannot issue a refund. If you think the charge was wrong, say so here and I will bring in a staff member.
Four things we will not bend on.
Tickets live in real channels.
No DM relay. Staff see the conversation, members see staff, and a new hire can scroll back and learn how things are handled.
The AI runs on infrastructure we own.
NEXUS is ours. Anthropic does the model work under no-training API terms, brain state stays on our servers, and on Pro you can run it on your own AI key instead.
Refunds without an interrogation.
14 days from your first subscription payment, full refund, no script. Token packs are delivered instantly, so those are final.
It works on a phone first.
Half the people running Discord communities live on their phone. Every page and the dashboard work at phone width before they ship.
It’s not just an AI, it’s your AI.
Friendly, reads the room, and never escalates for no reason.
The personality on this page is the one we want the bot to have in your server: warm enough that members ask it things, disciplined enough that staff trust what it says.
We also built Mico.
Mico
The AI-powered Discord application bot from the same team. Custom application forms, AI-assisted review, and an admin dashboard for community recruitment.
It’s not just an AI, it’s your AI.
Try the bot we built for ourselves.
Add it to your server and run one command. Everything on this page is in it.
Support, billing and data requests: [email protected]. Business: [email protected]. We reply within one business day.