Skip to main content

​
The problem with managed agent platforms

Managed agent platforms charge per run, per node execution, and per seat. Costs scale linearly with usage and become unpredictable as your agents handle more traffic. Beyond cost, there are structural trade-offs:
  • Data leaves your infrastructure. Agent state, conversation history, and tool outputs are stored on third-party servers. You have no control over data residency or retention.
  • Tracing is locked to one vendor. You can only send traces to the platform’s own observability tool. Switching or adding a second backend is not supported.
  • No database access. You cannot query, back up, or migrate the underlying database. The platform owns it.
  • Authentication is platform-managed. You configure auth through a dashboard, not in your own code.
These are reasonable trade-offs for prototyping. They become problems at production scale.

​
What Aegra gives you

  • Same SDK, zero code changes. Use the LangGraph SDK you already know. Your graph code, client calls, and Agent Protocol frontends work without modification.
  • Your infrastructure, your data. Run on your own servers with your own PostgreSQL database. Nothing leaves your network.
  • No per-run costs. No seat fees, no per-execution charges, no node pricing. You pay only for your own compute and database.
  • Flexible authentication. Write auth handlers in Python — JWT, OAuth, Firebase, or any custom scheme. Configured in aegra.json, not a dashboard.
  • Open tracing. Fan-out traces via OpenTelemetry to Langfuse, Arize Phoenix, Jaeger, Honeycomb, Datadog, or any OTLP-compatible backend. Run multiple at once.
  • Agent Protocol compliant. Works out of the box with Agent Chat UI, LangGraph Studio, and CopilotKit.
  • Apache 2.0 licensed. Inspect, modify, and contribute. No proprietary dependencies.

​
Cost comparison

LangSmith DeploymentsAegra
Deploy agentsLocal dev only (Free), paid cloud (Plus)Free, unlimited
Custom authNot available (Free), available (Plus)Python handlers (JWT/OAuth/Firebase)
Self-hostedEnterprise only (license key required)Always (Apache 2.0)
Own databaseManaged only (Free/Plus), bring your own (Enterprise)Bring your own Postgres
TracingLangSmith onlyAny OTLP backend (Langfuse, Phoenix, etc.)
Data residencyLangChain cloud (Free/Plus), your infrastructure (Enterprise)Your infrastructure
SDKLangGraph SDKSame LangGraph SDK
Based on LangChain pricing as of February 2026. An enterprise tier with self-hosting is also available at custom pricing. Aegra’s infrastructure cost is whatever you pay for PostgreSQL and compute. A single $5/month VPS can run the server, database, and multiple agents.

​
What we support today

Aegra covers the core capabilities needed for production agent deployments: assistants, threads, streaming, human-in-the-loop, persistent state, key-value and semantic storage, auth, observability, and deployment to Docker, PaaS, or Kubernetes. See the full breakdown on the feature support page.

Streaming

8 SSE stream modes with automatic reconnection.

Human-in-the-loop

Approval gates and user intervention points.

Authentication

JWT, OAuth, Firebase, or custom auth handlers.

Observability

Fan-out tracing to multiple OTLP backends.

​
Next steps

Quickstart

Get a running server in under 5 minutes.

Migrate from LangSmith

Step-by-step guide to switching from LangSmith Deployments.

Feature support

Full matrix of supported, planned, and upcoming features.