discord-bot.net — Full-cycle Discord Bot Development · C#

What we do

Full-cycle means we own every layer — from the library up to the rack.

01

Architecture & Design

We start from your community's actual workflow. Command surface, permission model, data shape, growth path. The first deliverable is a written architecture — not a prototype.

Discovery
02

Custom Discord.NET Library

Our own fork of Discord.NET carries the optimizations we couldn't upstream: connection pooling for shard managers, reduced-allocation hot paths, structured logging, and a command pipeline that holds up past 20,000 servers.

Core engine
03

High-Load Engineering

Sharding strategy, Redis-backed caches, RabbitMQ for backpressure, Postgres for state, Prometheus and Grafana for telemetry. We engineer for the day your bot trends — not the day it launches.

Scale
04

Hosting & Infrastructure

Owned server room. Physical rack. Proxmox virtualization, OPNSense edge, Harbor registry. No rented VPS — we control the full stack from the chassis to the container.

Owned metal
05

Multilingual & Public Bots

Internationalization built into the command layer — not bolted on. We have shipped public bots serving 20,000+ servers across multiple languages with translation pipelines that don't break on updates.

i18n
06

Maintenance & SRE

Long-term operation is the unglamorous half of full-cycle. Wazuh for security, Grafana for latency budgets, on-call discipline. Bots we built in 2019 are still running today.

Operations

Public bots · 20,000+ servers combined

Two bots we built for ourselves — and the 20,000 communities that adopted them.

Public Bot · 01

Mashiro

Mashiro#6180

A multifunctional bot with a focus on economy and social features.

mashiro.discord-bot.net →

Mashiro is the larger of our two public projects — a 200,000-line C# codebase spanning 500+ commands across economy, social interaction, administration, utilities, and moderation. It is the bot we use to stress-test our library: every optimization to Discord.NET lands here first.

The economy and social systems are the spine: marriage, reputation, currency, leaderboards, gambling, daily rewards. Around them sits a layer of administrative tooling — auto-mod, role management, logging — and a long tail of utility commands that communities request and we ship.

// Live metrics

8,000+

Active servers

Commands500+

Codebase200,000 LOC

LanguageC# · .NET 10

RuntimeOwned infra

ShardingMulti-shard

Economy
Social
Administration
Utilities
Moderation
Leaderboards
Marriage
Reputation
Currency
Daily rewards
Gambling
Auto-mod

Public Bot · 02

Kuro

Kuro#5836

Smaller, sharper, easier to use — and adopted by 19,000+ servers.

kuro.discord-bot.net →

Kuro is the distillation of everything we learned building Mashiro. Same C# core, same library, same infrastructure — but a deliberately smaller command surface tuned around interaction and economy. The result: a bot that communities install, understand, and keep.

Where Mashiro is broad, Kuro is focused. Onboarding takes seconds, the default command surface fits on one page, and the economy loop is tight enough to drive daily return visits. 19,000+ servers have decided that is the right shape.

// Live metrics

19,000+

Active servers

FocusInteraction · Economy

AdoptionHighest of our public bots

OnboardingSingle-page default

LanguageC# · .NET 10

RuntimeOwned infra

Interaction
Economy
Fast onboarding
Tight loop
Multilingual
Low friction

Owned infrastructure

Not rented VPS. A physical rack, in a room we control, running the bots we ship.

RACK-01 · SERVER ROOM

SELECT A UNIT

— Select a unit —

Hover or tap any rack unit to see its specifications, role, and current load.

Since 2018 we have operated our own server room. The rack is ours, the network is ours, the virtualization layer is ours. When a bot we built needs to scale, we don't open a billing tab on a cloud provider — we provision a container on hardware we already own.

Proxmox hosts the virtual machines. OPNSense sits at the edge. Harbor holds our container registry. Kubernetes orchestrates the production workloads. Wazuh watches the fleet. Every layer is observable in Grafana through Prometheus metrics.

This is why we can offer full-cycle: hosting is not a third party we have to coordinate with. It is the same team that wrote the bot.

host.discord-bot.net →

Virtualization

Proxmox

Edge firewall

OPNSense

Orchestration

Kubernetes

Registry

Harbor

Telemetry

Grafana · Prometheus

Security

Wazuh

Technology stack

The tools we actually run in production — not the ones that look good on a slide.

Languages

C#
Node.js
Python

Frameworks

Discord.NET (custom)
ASP.NET
Entity Framework
React
Avalonia

Data layer

PostgreSQL
MySQL
Redis

Messaging & RPC

gRPC
RabbitMQ

Infrastructure

Docker
Kubernetes
Proxmox
OPNSense
Harbor

Observability

Grafana
Prometheus
Wazuh

AI / LLM

vLLM
llama.cpp

Core library

Custom Discord.NET
Shard pooling
Low-allocation paths

The team

Three people. Every bot we ship passes through all three.

ColinFL

CEO · DevOps

Runs the company and the rack. Owns infrastructure decisions, deployment pipelines, security posture, and the long-term operational health of every bot we ship.

· Proxmox · OPNSense· Kubernetes · Harbor· Wazuh · Grafana

KiraKun

Lead Developer

Owns the architecture. Maintains our custom Discord.NET fork, designs the command pipelines, and reviews every line of C# that lands in a production bot.

· C# · .NET 10· Discord.NET (custom)· EF · Postgres · Redis

Nikon

Developer · UI

Owns what users actually see. Builds the dashboards, the React front-ends, the Avalonia tooling, and the interaction design that makes a 500-command bot feel small.

· React · Avalonia· ASP · gRPC· Interaction design

FROM IDEA TO HOST

Watch a bot come online — on our metal, through our library.