Krios

Project Context

Krios started as an internal moderation bot and is today a commercial DayronLabs product, operated at kriosapp.dev. It is not a demo: it has paid Stripe plans, a customer panel, documentation, a changelog, a status page, and bilingual support. It is proof that DayronLabs does not only ship client projects — we also run our own software in production, held to the same availability and billing standards as any SaaS.

Technical Challenge

A serious Discord server usually pays for three or four separate bots: one for security, one for ticketing, one for levels, one for economy. Each with its own panel, its own subscription, and its own point of failure. The goal for Krios was consolidating all of it into one bot and one panel, without losing depth in any module, and documenting every moderation action with forensic traceability.

Problems Solved

• •Real anti-nuke: detecting and reverting a compromised-admin attack (mass channel, role, and ban wipes) by restoring structure from backup, without false positives that lock out legitimate moderators.
• •Multi-tenancy over Discord: one process serving independent servers, each with its own configuration, licence, and isolated data — solved with Discord OAuth2 and a per-guild PostgreSQL model.
• •Self-service Stripe billing: signup, upgrade, cancellation, and licence-state reconciliation via webhooks, so the bot knows each server's plan in real time.
• •Verifiable 24/7 operation: Docker deployment with per-subsystem monitoring and a public status page that exposes real uptime instead of promising it.

Technical Execution

End-to-end product: a Discord.js v14 bot with 120 commands and a forensic moderation suite (ticketing with HTML transcripts, infractions, audit logs, edited and deleted messages); a Next.js web panel with Discord OAuth2 login and visual configuration for every module; PostgreSQL with Prisma; Stripe billing; Docker deployment; documentation, changelog, and status page; and a full Spanish/English interface.

Results Obtained

Krios is live at kriosapp.dev with real servers connected, per-subsystem monitored uptime, and active billing. It replaces three or four paid bots with a single one, and its panel puts configuration in the server owner's hands without touching code or asking us for anything.

Visual Evidence