Kofi E. Ampaabeng

Selected Work

20 systems I have architected, built and run: enterprise platforms, consumer apps, and the tools and infrastructure behind them. 20+ years across regulated banking, data platforms and applied ML.

20
systems
6
enterprise
7
ML · LLM
20+
years

17 · Service catalog, live health

Estate catalog and status

A catalog no one keeps by hand: built from what is published.

A developer portal whose catalog is generated from the manifests that publish the services, with docs assembled from each repo behind a redaction gate, and a collector that reads container health and disk from outside the portal.

  • Infrastructure

Surfaces

  • Web
  • API
  1. 01Generated, not maintained — the catalog is built from the publishing manifest on every run.
  2. 02What runs where — every component depends on its host; hosts are resources under one infrastructure system.
  3. 03Drift warnings — an unmapped service, or a mapping to a service that is gone, is reported on every run.
  4. 04Honest status — the collector reads each host from outside; a host it cannot reach shows unknown, never up.
  5. 05Disk alerts that outlive the portal — per-host thresholds, emailed on breach and on recovery.
  • 112 catalog components
  • 28 systems
  • 30 collector tests
SurfacesWebAPI
SOURCESBUILDSTOREPORTALdocsstatusdisk breachService manifestSystem mapsRepo docsCatalog generatorDocs assemblerredaction gateStatus collectorevery 60 sCatalogStatus feedDeveloper portalDisk alertsemail
Architecture, drawn from the codeServiceStoreModel usedModel trained hereFeedback
  • Backstage
  • TechDocs
  • PostgreSQL
  • Python
  • Node 22
  • Docker Compose