Features
A source of truth for deploys and releases, with native MCP for Claude Code and claude.ai.
Native MCP
i3deploy exposes your deploys and releases as MCP tools, readable and writable by Claude Code and claude.ai directly — no copy-paste, no context switching. Ask Claude "what's in production?" or "cut a release for project X" and it talks to i3deploy natively. The MCP connector works both as a remote connector in claude.ai and as a local server in Claude Code.
Automatic changelog
Release notes are derived from real deploy events rather than written by hand. When services deploy, i3deploy records the event; when you bundle a project release, it assembles those events into a curated changelog. Open-source client packages (like django-i3version) consume the public GCS manifest to surface an in-app changelog to your users — no manual publishing step required.
Open-core, zero lock-in
The server writes a stable, public JSON manifest to a GCS bucket on every state change. That schema is the contract between i3deploy and the rest of the ecosystem: open-source clients read it, third-party integrations can build on it, and you can always export your data. The server is closed/paid; the client libraries and the bucket contract are open-source and permanently free.
Scale-to-zero
i3deploy runs on Cloud Run with scale-to-zero economics: when nobody is hitting the API, it costs nothing. This lets us price from a few euros a month for small teams — not because we're cutting corners, but because the infra genuinely costs that little. Keeping your deploy tracker running should be a rounding error on your bill, not a budget line.
Ready to try it?
Early access is free. Join the waitlist and we'll let you know when it's your turn.
No spam, just launch news.