None of this is client work. It's our own company, running on agents we built: 166 on one platform, wired into 36 production workflows, and they've run nearly twelve thousand times. The count isn't the point. We've already hit the problems you'd hit in month three. Figures read live off the platform on 7 August 2026.
166
agents on the platform
36
production workflows
11,826
agent runs to date
7
live projects, one platform
Agent Stack · platform
AgentForge
The runtime everything else registers into, with its own library of expert reviewers for code, security, architecture and observability. A request gets matched to an agent, composed into a system prompt, and executed under a budget cap and an explicit tool grant.
Enterprise platform teams · hosts all 166 agents · 45 expert reviewers · v4.59.1
Agent Stack · platform
NLT Memory
Cross-session recall with hive propagation and a knowledge graph, reached over HTTP rather than embedded inside each consumer. Without a memory authority every agent starts from zero on every run. We built it because we hit that wall ourselves.
Engineering orgs running agents at scale · shared memory authority · 1,301 commits
Agent Stack · platform
Report Studio
Agents that write documents. Our technical deep dives are built by it, from repo source, on a template. Nothing gets hand-assembled in a design tool, so a forty-page reference rebuilds itself when the code underneath it changes.
Teams whose docs go stale on arrival · document kernel · 359 commits
Portfolio Suite · products
NLT Portfolio Engine
Our biggest fleet: thirty-nine agents behind a capital gate. An intake doc runs an 11-step evaluation covering market, feasibility, financial model, regulatory exposure and a devil's advocate pass, and comes out as FUND, PASS or DIG DEEPER. On FUND, a 22-step workflow builds and deploys it.
Teams that start building before anyone decided to · 39 agents · 6 workflows
Portfolio Suite · products
NLT Scout
Fourteen intake pipelines, one per source: Reddit, YouTube, Hacker News, Product Hunt, Indie Hackers, Flippa, public procurement records and the open web. Seven agents do the work and get reconfigured per source, which is the whole trick.
Teams drowning in ideas with no way to rank them · 7 agents · 14 workflows
Reference build · not sold as a product
Web-Store-DNA
A whole storefront operation, broken into five jobs a small business actually recognises. First commit was 28 July 2026, and by 5 August the same kit was running a second, independent storefront. That gap, eight days, is the honest answer to whether this transfers.
Catalog and listings
Probes the live storefront, extracts product data, drafts the listing copy and writes it back to the store.
listing-pipeline · 12 steps
Multi-channel marketing
Pulls social signal, plans a calendar, drafts the posts, then checks each for originality and disclosure before it publishes.
content-calendar · 10 steps
Customer service
Reads the ticket queue and drafts replies, holding every one behind a judge before a customer sees it.
cx-inbox · 12 steps
Analytics and anomalies
Pulls orders, ad spend and site analytics, correlates them, then explains what moved instead of just charting it.
store-health · 14 steps
Go-live gate
Scores whether an agent is fit to run at all. Nothing reaches a customer without clearing it first.
agent-readiness · 9 steps
Nine of the thirty agents do nothing but check the other twenty-one. Five judges cover claims, disclosure, originality, replies and visuals, three domain experts cover brand, commerce and compliance, and one scans for prompt injection. Roughly a third of the fleet exists to catch the rest, and that's what makes it safe to point at a live storefront.
Small commerce teams · 30 agents · 5 workflows · 57 steps · running on 2 storefront projects · v0.1.0 · in development