Think inside your AI world.

Heroku through Unl

Apps, dynos and Postgres internals, read straight from the CLI Heroku already trusts, then checked against the release rule you ratified.

Heroku through Unl reads app, dyno and Postgres state against the release criteria you have ratified, so 'can this app promote' comes back held, not blocked, with the condition it hasn't met.

What Heroku holds

Heroku through Unl reads what the platform already tracks:

  • Lists every app on the account, filterable by personal, collaborator, team or space
  • Reads detailed app configuration, dynos and attached add-ons
  • Pulls application logs for a named app
  • Inspects Postgres database info, active queries and locks currently held
  • Lists pipelines and their stage-by-stage promotion detail

What the naked read gives you

Ask Heroku's own MCP server what's running on an app and it answers in the same terms the CLI always has: dyno count, attached add-ons, the latest log lines, the Postgres locks currently held. It's a literal, dependable account of platform state, reachable now in conversation rather than a terminal.

The frame judges the data it is given; it does not verify the source’s accuracy.

What changes when Heroku is read measured

A release manager ratified that no app promotes through the pipeline while a Postgres lock is blocking another query — a blocked migration once sat unnoticed for six hours during a promotion window.

'Can this app promote to production?' returns, measured: held, not blocked, because Heroku's own lock data shows an active hold still waiting on the target database. Heroku supplied the lock reading; your ratified rule supplied the promotion gate.

And back again

Unl doesn't let that answer close with the chat window: the app, the lock reading and the promotion rule sit together as one entry, so tomorrow's version of the same question starts from what was already found rather than from nothing.

The answer comes back measured against what you already decided, and why.

The lane is live and open to this tool today: one box, paste anything. If it speaks MCP, Unl can reach it. Readings arrive unprompted, the data beside the criterion; Unl is a courier, not a warehouse, and keeps only your keys and the frame.

Questions people ask

What clears an app to promote after a hold?

A fresh lock reading with nothing blocking the target database. Once Heroku's own pg_locks data shows the hold has released, the same question returns cleared instead of held - the promotion gate hasn't moved, the database has.

How do I connect Heroku to Claude?

Install the official heroku-mcp-server, either as a Heroku CLI plugin or via the remote MCP endpoint, authenticate it against your Heroku account, and add it as an MCP connector in Claude Code or Claude Desktop. Its app, dyno, add-on and Postgres tools then become read sources Unl can query.

Does Unl change anything in my Heroku apps?

No. The connection only reads - app configuration, logs, dynos, Postgres internals. Nothing is redeployed, scaled or restarted as a result of a measured answer.

What this is

Think inside your AI world — you stay in command

Unlimitless (Unl to friends) holds what you've settled, reads what your tools are showing, and catches what's changed out in the world — and hands your AI whatever bears on the work, the moment it's needed, without you asking. The right thing, in front of the model, unprompted, with you in command of the call. So you keep moving toward what you set out to build, on top of everything you've already decided.

It plugs into Claude, Claude Code, ChatGPT and Cursor as an MCP connector. Quick to connect, in a couple of steps.

Unlimitless is open now to invited Alpha. Apply for the Beta waitlist to come in ahead of the full launch:

Alpha is invite-only · free at launch.