Glitter infrastructure, structured overview.
A clear view of how glitter.kr is organized: edge routing, microservices, DNS, mail, and the underlying host.
A personal cloud with structured layers.
All traffic enters through Nginx and is routed to focused FastAPI services. DNS and mail are operated as self-owned layers, forming a trust base fully controlled by the operator. This page shows the system structure at a glance.
Receives HTTPS, terminates TLS, serves static assets, and routes traffic to the correct FastAPI backend. No external proxy is placed in front of it.
glitter.kr for the main console, glitter.bz and glitter.im for checks and status, msg.glitter.kr for messaging, and captcha.glitter.kr for in-house captcha.
BIND with DNSSEC signs the zones, while SMTP and IMAP services handle mail delivery for glitter domains.
All of this runs on a Self-hosted physical server, with volumes organized for code, logs, and service data, forming a quiet, operator-owned cloud.