Escalation Host vs Heroku

Escalation Host vs Heroku — which to pick

Heroku is the platform that taught the industry what "12-factor app" looks like. It still runs a lot of mid-size Rails / Django / Node apps and there's no particular reason to move those if they're working. Escalation Host exposes the same kinds of long-running runtimes (Node, Python, PHP, static) but through an agent-native interface — MCP server, scoped keys for AI agents, persistent agent notes, magic-link recovery. Here's how to think about it.

Feature comparison

Feature	Escalation Host	Heroku	Note
Long-running Node / Python / PHP / Laravel	✅ all four	✅ all four (Ruby + Java + Go too)	Heroku's runtime breadth is wider; we cover the most common four well.
Static / SPA	✅ first-class	⚠ via Node buildpack	Heroku wasn't designed for static; we serve it natively.
Built for AI agents (MCP)	✅ first-class MCP + REST	❌ no MCP	Heroku has a great CLI for humans. There is no agent interface.
Scoped agent keys	✅ 11 scopes + approval gates	⚠ API key (single scope)	Heroku API keys grant full account access; ours are per-action.
Magic-link recovery for agents	✅	❌	When your AI loses context, you re-grant in two clicks.
Persistent agent notes	✅ cross-session memory	❌	Built-in.
Incident surface for agents	✅ structured	⚠ logs/metrics dashboard for humans	Same data, agent-shaped on our side.
Sealed-box transport encryption	✅	❌	Useful for the agent's pre-auth signup call.
Add-ons marketplace (databases, etc)	⚠ BYO external (Neon/PlanetScale/Supabase)	✅ rich marketplace	Heroku's add-ons are still a strong selling point. Native managed DBs are on our roadmap.
Custom domain + TLS	✅	✅ paid plans	Standard on both.
Pricing entry	$25/mo Builder	Eco $5/mo (sleeps); Basic $7/mo	Heroku's entry tier is cheaper; their Eco dynos sleep when idle, which can surprise people.
Lock-in	Standard Docker runtimes	Buildpacks (portable but ecosystem-specific)	Both reasonably portable; Heroku's buildpacks have a long tail of vendor-specific behavior.

Feature

Escalation Host

Heroku

Note

Long-running Node / Python / PHP / Laravel

✅ all four

✅ all four (Ruby + Java + Go too)

Heroku's runtime breadth is wider; we cover the most common four well.

Static / SPA

✅ first-class

⚠ via Node buildpack

Heroku wasn't designed for static; we serve it natively.

Built for AI agents (MCP)

✅ first-class MCP + REST

❌ no MCP

Heroku has a great CLI for humans. There is no agent interface.

Scoped agent keys

✅ 11 scopes + approval gates

⚠ API key (single scope)

Heroku API keys grant full account access; ours are per-action.

Magic-link recovery for agents

✅

❌

When your AI loses context, you re-grant in two clicks.

Persistent agent notes

✅ cross-session memory

❌

Built-in.

Incident surface for agents

✅ structured

⚠ logs/metrics dashboard for humans

Same data, agent-shaped on our side.

Sealed-box transport encryption

✅

❌

Useful for the agent's pre-auth signup call.

Add-ons marketplace (databases, etc)

⚠ BYO external (Neon/PlanetScale/Supabase)

✅ rich marketplace

Heroku's add-ons are still a strong selling point. Native managed DBs are on our roadmap.

Custom domain + TLS

✅

✅ paid plans

Standard on both.

Pricing entry

$25/mo Builder

Eco $5/mo (sleeps); Basic $7/mo

Heroku's entry tier is cheaper; their Eco dynos sleep when idle, which can surprise people.

Lock-in

Standard Docker runtimes

Buildpacks (portable but ecosystem-specific)

Both reasonably portable; Heroku's buildpacks have a long tail of vendor-specific behavior.

When to pick each

Pick Heroku if

You already run a mid-size Rails / Django / Node app on Heroku and it works
You depend on add-ons in their marketplace (Postgres, Redis, etc) that they bill on your behalf
You want Ruby or Java or Go support — we don't have those yet
You're a developer comfortable with their CLI and don't need an AI in the loop

Pick Escalation Host if

Your AI is the operator, not you
You want per-action scoped keys instead of an all-powerful API token
You want magic-link recovery when a new AI session needs access
You want the AI to read structured incident signals and proactively fix things
You're happy bringing your own managed database (Neon, Supabase, PlanetScale) via env vars

The bottom line

Heroku is the right pick if you have an existing app running there and the buildpack ecosystem is working for you. We're the right pick if your interaction model with the runtime is "tell my AI what I want and let it deploy" — and you want the platform to treat that AI as a real first-class operator rather than a person holding an API key.