About
Built for Discord communities that take support seriously.
AI Ticket Bot is an independent product made by a small team operating from Romania. One bot, focused on one thing: helping your staff close real tickets faster.
Our story
Started as a hobby. Stayed honest.
Two and a half years ago this was a weekend project, a single Python file, and an SQLite file next to it. People started using it anyway. We have been learning in public ever since, and the rebuild you are looking at is everything that learning turned into.
Early 2024
The hobby
A learning project. SQLite, everything in one main.py, no real architecture. Shipped it to a couple of our own Discord servers to see if it would even survive a weekend.
2025
First production rebuild
Moved to a real database, better servers, a proper codebase. Tickets ran on Discord forum posts with a DM relay so staff replies reached the user. It worked, but every part of it taught us something. AI broke more than once. Token usage was nowhere near optimized.
Late 2025
3,000+ servers
The bot crossed three thousand Discord communities. That stopped being a hobby number. We started taking the feedback seriously, especially around AI accuracy and the friction of the forum-post system.
Early 2026
Mico
Took everything we learned and built a second product: Mico, an AI-powered application bot. Different problem, same bar. Running Mico in production taught us what shipping a Discord bot at scale actually costs.
Mid 2026, now
AI Ticket Bot, rebuilt
The forum-post + DM-relay system was clever, but the UX was a tax on every new user. Move to normal channels, fix the AI accuracy and memory issues, give NEXUS its own home. We threw the old code out and rebuilt from the schema up. This site is the launch surface for that rebuild.
What V1 taught us
Tickets belong in channels.
The 2025 rebuild used Discord forum posts as tickets, with a DM relay so staff replies reached the user even when they were not watching the forum. Mechanically it was clever. As a product it was a steady tax on every new user, and each fix below was the signal to stop patching and rebuild.
- Forum-post tickets were unfamiliar. Members did not know where to type, or thought the bot was broken when their reply landed in a thread they did not recognize.
- Hard limit of one open ticket per user across ALL servers: the DM channel was the relay, and Discord only gives one.
- Members with DMs disabled (a popular privacy setting) never saw staff replies at all.
- Occasional message-delivery failures and notification bugs at both ends of the relay.
- A pipeline so complex and inefficient that supporting it was its own job.
and the AI side
- Accuracy was not where it needed to be.
- Memory drifted across long tickets.
- Token usage was wildly unoptimized.
- Tickets live in plain Discord channels every member already knows how to use.
- Visible to every staff member with the right role. No relay, nothing to break.
- NEXUS, a separate AI system on our infrastructure, 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.
The team
Three people. Same Discord servers.
We are not a startup with a roadmap and a Series A. We are the people who built the bot and use it in our own Discord servers every day, alongside thousands of other communities that picked it up over the last two years.
dani
Founder, bot dev
Started building Discord bots as a weekend habit. Owns the bot core, NEXUS, and the AI brain. Romania.
!⁶⁹ Alex
Co-founder, frontend
Full-stack with a frontend lean. Owns the dashboard and the marketing site. Romania.
Praetorian
DevOps
Keeps the infrastructure standing. Deployment pipelines, server reliability, backups.
NEXUS
The AI runs on infrastructure we control.
AI features are powered by NEXUS, our own platform built for Discord communities. NEXUS lives at nexbrain.dev and is operator-owned end to end. When your staff teaches the bot with /ai train, the entry lands in your server’s brain on our infrastructure. When the AI replies to a ticket, the conversation routes through NEXUS for inference.
NEXUS calls Anthropic for the actual model work. Anthropic runs with the default no-retention API posture: nothing your members write is kept by them or used to train their models. No third-party AI middleman, no resold OpenAI markup.
We do not sell your data. We do not use it to train external models. Full details on the privacy policy.
What we hold to
Four tenets we will not bend on.
- 01
Tickets live in real channels.
No DM relay. Staff see the conversation, members see staff, new hires can scroll back and learn how things get handled. That is the architecture.
- 02
AI runs on infrastructure we own.
NEXUS is ours, hosted at nexbrain.dev. Anthropic does model inference under no-retention API terms. Brain state stays on our boxes.
- 03
Refunds, no interrogation.
14 days from your first subscription payment, full refund, no script. Past 14 days we still consider pro-rata refunds when refunding is the right thing. Token packs are delivered instantly, so those are final.
- 04
Mobile parity from day one.
Half the people running Discord communities live on their phone. Every page works at 380px before we ship. Same goes for the dashboard.
It’s not just an AI, it’s your AI.
Friendly. Reads the room. Does not escalate to staff for no reason. The personality on the page is the personality we want the bot to feel like in a server: warm enough that members ask it questions, disciplined enough that staff trust what it says.
Sister product
We also built Mico.
Mico
Our second product, by the same team. AI-powered application panels with scoring and staff review. Same Direction A design bar, different problem space.
Get in touch
Email us.
Support, billing, refunds, data-rights: [email protected]. Legal and business: [email protected]. We reply within one business day on weekdays, sooner when something is on fire.