No isolation
AgentForge keeps consumer state under projects. Platform purity by design.
Platform · Module
Orchestration
without contamination
Generic agent orchestration: workflows, policy, and project-isolated consumer state. The OS layer of NLT Agent Stack.
Proof beats promises
portfolio.nltlabs.ai ↗Every claim routes to a live URL, not a slide.
Consumer logic in the platform tree is how fleets rot.
SDK-only stacks
A raw model SDK is not an orchestration OS. You still need workflows, audit, and bridges.
Operator blind spots
Console and workflows give operators a surface, not a black box.
Competitive advantage vs raw SDKs and DIY glue
- Project isolation keeps every team's special case out of the shared platform tree.
- Workflows, policy, approvals, and transactions are productized. An SDK still leaves that to you.
- HTTP-clean bridges to memory and tools that security can actually review.
- Reference consumers in production. Watch Scout and Portfolio Engine run on it.
How to picture it
Project isolation lanes
Consumer logic never contaminates the platform tree.
Stack context
AgentForge is the OS layer under Memory and Report Studio.
Product surface
How it works
- 01
Define
Agents and workflows as first-class objects.
- 02
Run
WorkflowEngine executes with policy and isolation.
- 03
Bridge
Memory and tools stay HTTP-clean at the boundary.
What's included
- Workflow engine and CLI runner
- Project-isolated consumer state
- Operator console
- Eval against your orchestration needs
Questions buyers ask
Why not just the Claude Agent SDK?
A platform beats a raw SDK when you need fleet discipline: workflows, policy, and isolation that survive more than one team.
Where is the ROI?
Lower platform TCO and fewer reinvented orchestration layers. Full ROI framing lives on the Platform page.
AgentForge
One conversation. Honest fit. We'll tell you if this isn't the right path.