Discord systems, panels and the infrastructure behind them.
Everything below is running in production right now. Head straight to a project, or scroll down if you want something built.
Work with meProjects
Each card says who it was built for.
Tools
Free to use. Public API endpoints are being built.
Services
Most projects are some mix of these four.
Discord Systems
Bots for moderation, tickets, whitelists and economy, with a web dashboard so nobody has to edit config files.
- Moderation & tickets
- Whitelist and accounts
- Web dashboard included
Web Applications
Dashboards, control panels and internal tools, built around what the people using them actually do all day.
- Admin & control panels
- Role-based access
- Responsive by default
APIs & Backend
REST endpoints, auth flows, webhook handlers and the databases behind them. Documented and ready to plug in.
- REST APIs
- OAuth & webhooks
- MySQL / MariaDB
Game Server Tools
Panels and systems for multiplayer communities: player administration, faction tools, logging, statistics.
- Player administration
- Access logs
- Live statistics
FAQ
Mostly Discord bots and the dashboards around them, plus web applications, control panels and the backend infrastructure underneath. Built to actually run in production, not to sit in a portfolio.
Next.js and TypeScript on the frontend, Node.js or PHP on the backend depending on the project, and MariaDB/MySQL for storage. Everything runs on my own servers behind Apache and PM2. The stack follows the job, not the other way around.
Send a message on Discord describing what you need. You get an honest assessment of what is realistic, roughly how long it takes and what it costs, before anything is agreed.
It depends entirely on scope, so there is no price list. Small tools and bots start low, full systems with a dashboard are a different scale. You always get a fixed number before work starts, so there are no surprise invoices.
A small bot or tool is usually days. A full system with dashboard, authentication and admin area is closer to weeks. You get a realistic estimate up front, and a heads-up early if something turns out bigger than expected.
Yes. What gets built for you belongs to you, including the code and the database schema. Nothing is locked to a platform you cannot leave.
Going live is where the real work starts. Monitoring and uptime checks run continuously, and bugs that show up in the first weeks get fixed as part of the project. Longer-term maintenance can be arranged separately.
Often yes, as long as the code is in a reasonable state and accessible. There is an honest look at it first, because sometimes rebuilding is genuinely cheaper than repairing, and you will be told that plainly.
Contact
Describe what you need. What comes back is an honest read on whether it is realistic, including when the answer is no.