Agentic development tools, audited.

Use this map to understand what each tool category does, where overlap appears, and how to budget from pilot mode to scaled production.

Visual ecosystem grid

Think in layers: code surface, runtime framework, platform infrastructure, and orchestration logic. Gaps usually happen between layers, not inside one tool.

IDEs

Where developers co-build with code-generation and inline reasoning.

• Cursor — from $20/mo per seat. AI-native editing and agent tasks.
• Windsurf — from $15/mo per seat. Fast task-oriented coding loops.
• VS Code + extensions — free core + add-on costs. Flexible and team-friendly baseline.

Frameworks

Runtime primitives for memory, planning, and multi-agent orchestration.

• OpenClaw — open source + infra. Custom governance and audit depth.
• LangGraph — open source + infra. Deterministic graph workflows.
• CrewAI — open source + cloud options. Role-based crew execution.

Platforms

Hosted model APIs, observability, and deployment surfaces.

• OpenAI Platform — usage-based. Model API, evals, and tool calling.
• Anthropic API — usage-based. Long-context reasoning and guardrails.
• Vercel + serverless stack — free to enterprise. Fast app delivery and hosting.

Orchestration

Cross-system automation for handoffs, approvals, and event triggers.

• Temporal — open source + cloud tiers. Durable workflow execution.
• Trigger.dev — free to usage tiers. Event workflows for JS runtimes.
• n8n — free self-hosted + cloud tiers. Low-code ops integration hub.

Pricing bands for planning

Use pricing bands as planning anchors, then validate against real event volume, token usage, and seat counts.

Frequently asked

What category first?

Start with one IDE and one framework around a single production use case. Add orchestration only after human review and measurement are stable.

How do I estimate monthly spend?

Model cost is usually usage-driven; IDE and orchestration costs are seat- or event-based. Build forecasts from workload volume, not feature count.

When is a platform-heavy stack worth it?

As soon as uptime, observability, and governance risks exceed the cost of managed infrastructure. That usually lands once workflows touch revenue or compliance.

How do teams avoid tool sprawl?

One owner per stack layer, deprecate low-use tools quarterly, and tie every paid tool to a measurable workflow outcome.