← Complete project index

Infrastructure & Operations / Built / deployed

Infrastructure Operations Platform

Central service, deployment, policy, storage and execution control plane with RBAC, audit events, read-only command views and guarded host execution.

STATUSBuilt / deployed
AREAInfrastructure & Operations
STACK6 documented technologies
INTEGRATIONS5 connected / bounded services
01

OVERVIEW

What I built.

Central service, deployment, policy, storage and execution control plane with RBAC, audit events, read-only command views and guarded host execution.

01

Built a central operations portal for services, deployments, policy, storage, documentation and reviewed execution jobs.

02

Added local users, Argon2id authentication, RBAC, audit events and read-only command/fleet views.

03

Separated the web application from privileged host execution through a reviewed job catalog and runner.

02

SYSTEM ARCHITECTURE

How the system is divided.

01
Architecture boundary

Browser -> authenticated portal/API -> PostgreSQL operational state.

02
Architecture boundary

Reviewed Git job definitions -> independent host runner -> controlled execution.

03
Architecture boundary

Command Center and Fleet Center are read-only views; mutations remain in audited/operator paths.

03

NETWORK / DATA FLOW

What talks to what.

04

TECHNOLOGY STACK

The technical surface.

01Linux
02Docker
03PostgreSQL
04RBAC
05Python
06Caddy
05

IMPLEMENTATION

How it works in practice.

  1. 01

    Browser -> authenticated portal/API -> PostgreSQL operational state.

  2. 02

    Reviewed Git job definitions -> independent host runner -> controlled execution.

  3. 03

    Command Center and Fleet Center are read-only views; mutations remain in audited/operator paths.

06

TESTING & VALIDATION

How I know it works.

TEST 01

API/read-only dashboard failure visibility

TEST 02

Reviewed low-risk posture/health jobs

TEST 03

RBAC/session behavior

TEST 04

Catalog synchronization

TEST 05

Execution runner validation against reviewed job definitions

TEST 06

Audit-event inspection

07

EXTERNAL SERVICES & DEPENDENCIES

What sits outside the core.

COREInfrastructure Operations Platform
08

ENGINEERING EVIDENCE

Artifacts behind the claims.

01Command Center
02Fleet Center
03Service/deployment registry
04Audit log
05Storage inventory
06Execution catalog
07Network map
09

BOUNDARIES / CONSTRAINTS

What the project does not pretend to solve.

Web container has no Docker socket

No arbitrary host command execution from the browser

Read-only dashboards cannot mutate production

10

RESULT / CURRENT STATE

What this produced.

A centralized control plane that makes a multi-service home/production lab understandable and operable without handing arbitrary host execution to the web UI.

DEEP CASE STUDY AVAILABLE

Failure modes, investigation path and engineering evidence.

Open full case study →