Core
Automation lives on Kubuntu.
Workflows, files, scripts, and credentials remain close to the operating system they control.
Local-first automation layer
Quiet systems. Fast execution.
SAGI runs private infrastructure from a local machine, exposed through a minimal Cloudflare edge. No noise. No dashboards for show. Just clean, controlled automation.
View system ↓Stack
One machine. Many doors. Only the right ones open.
Local services stay local. Public routes are intentionally mapped, protected, and reversible.
Edge
Cloudflare is the front door.
A tunnel reflects selected localhost ports to stable public hostnames without exposing the router.
Private
Access before interface.
Internal tools should sit behind identity, not naked on the public web.
Public
Static when possible.
The main site is intentionally simple: HTML, CSS, a tiny server, and smooth edges.
Control
Rollback remains easy.
Each service is separated, named, logged, and controlled by systemd.
Flow
The web sees polish. The machine keeps control.
Public routes are just reflections of local intent.
sagi.systems
n8n.sagi.systems
localhost:8090
localhost:5678
Cloudflare Tunnel
Signal
Designed to stay understated.
No pitch. No fake product language. Just a living front page for a system that actually runs.
Status
01clean public surface
status.sagi.systems links to the public status surface when the route is enabled.