architecture decision record
At Ledd Consulting, we run 25 services coordinated by 7 specialized agents on a single VPS. When we needed to build an agent registry — the system that knows which agents exist, what they can do, and how to reach them — we had a real architectural choice to make. This is
Intelligence Brief
MetalTorque Daily Brief — 2026-03-29 Cross-Swarm Connections The Audit Gap Is Everywhere — and It's the Same Gap. The Agent Opportunities Swarm identified that zero of eight new MCP servers solve governance. The Agentic Design Swarm found that no benchmark compares autonomous agents against deterministic pipelines. The Quantum-AI Swarm caught
uptime monitoring
At Ledd Consulting, we run 25+ services on a single VPS. Seven AI agents, a marketplace API, an analytics pipeline, a newsletter platform, an MCP server, a notification router, and a fleet of scheduled timers that fire throughout the day. When we started looking at uptime monitoring, every SaaS option
portfolio automation
Every consultancy has the same dirty secret: the portfolio page is six months stale. The case studies reference last year's stack. The "projects completed" counter stopped incrementing the week it was manually typed into an HTML file. Meanwhile, your team ships code daily, publishes blog posts
Intelligence Brief
MetalTorque Daily Brief — 2026-03-25 Cross-Swarm Connections The OWASP-to-Revenue Pipeline Is One Build. The Agent Opportunities Swarm flagged OWASP's Top 10 for Agentic Applications (March 23) as a compliance mandate. The Agentic Design Swarm independently found that PISmith achieves 100% attack success against best-available prompt injection defenses and that
architecture
When you run 25 services on a single VPS, the default instinct is to wire them together with HTTP. Every service gets a port, every call gets serialized to JSON, every request traverses the full TCP stack — and nobody questions it because "that's how microservices work."
postmortem
At Ledd Consulting, we run social monitoring agents that scan developer communities for signals — new articles, forum questions, hiring posts. These monitors feed into our event bus, which fans out to notification services, an AI watcher for opportunity scoring, and a lead pipeline. On March 8th, a routine tag expansion
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
systemd timers
At Ledd Consulting, we run 25 microservices, 7 autonomous agents, and over 60 systemd timers on a single VPS. Every one of those timers matters — they scrape job boards, post to social channels, run nightly research pipelines, generate client reports, and reconcile billing data. When a timer silently dies at
architecture decision record
At Ledd Consulting, we run 25 services on a single VPS — scrapers, agent pipelines, CRM integrations, content publishers, billing webhooks, and more. Each one has something to say. A lead comes in. A bid gets approved. A blog post is ready for review. A health check fails. A cost threshold
lead scoring
Every freelancer and small agency knows the feeling: you open your inbox to 40 new job postings, 12 inbound inquiries, and a handful of marketplace notifications. By the time you've read through them all, triaged the duds, and identified the two or three worth pursuing, ninety minutes have
cost-management
At Ledd Consulting, we run 25 microservices and 7 autonomous agents on a single VPS. Our daily API bill is typically under $2. One Tuesday morning, it was $900. Here is exactly what happened, how we caught it, and the auto-capping system we built so it stays impossible for this