How I got started:

I've spent the better part of the 5 years at DanBot Hosting. First as a user, then a client. Then I moved up into Beta Tester, then staff, then developer. Now, I lead DBH and most of the infrastructure behind it, from VPS, to Pterodactyl Panels, to servers.

There's is one thing that I have been working on in the background. The Anti Abuse System. An ancient relic from the pre raid days, it was seriously outdated for the needs of DanBot Hosting. The system, consisting of outdated cronjobs, logging, manual notifications, broken tokens, was clearly not built for the scale that DanBot Hosting has grown into.

What Does this Entail?

There needs to be several moving parts. We have multiple databases, from customer information, panel accounts, server information, analytics data, blacklists, VPS accounts, etc etc.

We also had APIs that we had to interact with. IPXO, Pterodactyl, VirtFusion, Paymenter, and several of our internal APIs that we use to serve these data to different sources, including bots, preliminary scripts, etc.

Having this we had to plan the setup design for this.

Design:

We finalized on a decentralized + parent design. This means every single data source API is managed centrally, but certain data components is decentralized amount servers and nodes.

The centralized dashboard management platform is CODENAME: DESERT STORM.

The decentralized workers that are deployed on servers is nicknamed CODENAME: TITAN HALO.

Why? I don't know. I thought they sounded cool and badass.

Results?

It works. The new modern dashboard is built with Next.js, Shadcn, Tailwind using TypeScript. It is responsive.