node.js
The Pain Point You're running 25+ microservices. Business is evolving fast — new product funnels, new intake forms, new checkout flows. Every feature request turns into the same conversation: "Should this be a new service?" If you say yes every time, you end up with a sprawl
infrastructure
The Pattern — Catalog-Driven Infrastructure One JSON file declares every service, health check, automation, and process in your infrastructure. Every other artifact — documentation, health dashboards, drift reports, reconciliation scripts — is derived from that single manifest. Nothing is hand-maintained downstream. At Ledd Consulting, we run 26 health-checked services, 19 recurring automations, and
stripe
The Pain Point You have a productized service. A customer pays. Now what? If you're like most small teams, the answer is: someone gets an email, someone remembers to run the thing, someone exports the report, someone sends it to the customer. Maybe that takes an hour. Maybe
postmortem
Summary On March 25, 2026, we added a second system user to our single-VPS infrastructure running 25 AI microservices at Ledd Consulting. Within hours, the event bus started silently dropping events, the automation state database threw SQLITE_BUSY errors under load, and two JSON state files were truncated to zero
autonomous-agents
When you run 25 microservices, 7 autonomous agents, and 60+ scheduled timers on a single VPS, mornings become a problem. We wake up to a system that has been busy — scraping job listings, running research pipelines, extracting actions, building knowledge bases, checking for hallucinations — all between 1 AM and 7