Hey Product Hunt, I'm Caio, the founder of Hangar. I started Hangar because my own deploy loop had turned into copy and paste. My coding agent would write the change, I would push it, something would break in production, and then I'd copy logs from a dashboard back into the chat so the agent could guess what went wrong. So Hangar gives the agent the same view you have. Over MCP it can create the project, add a Postgres, deploy, wait for the build, then read the build log, the error logs, the failing requests and their traces, and the CPU and memory of the service. When a deploy fails it reads why, fixes the code, pushes and deploys again. You approve, it does the legwork. If you don't use an agent, it works the way you'd expect: connect a GitHub, GitLab or Bitbucket repo and every push deploys. A few things we cared about: - Railpack builds (the builder Railway uses), plus Dockerfile and buildpacks, so most repos deploy unchanged - Postgres, MySQL, MariaDB, MongoDB, Redis and libSQL on a private network next to your app, with scheduled backups to your own S3 - Preview environments per pull request, custom domains with HTTPS - Usage billing, and spend limits per organization and per project that can pause services instead of only sending an email - Billing in your local currency where we have a market (Brazil today) Honest caveats: Hangar is new, there's no CLI yet (dashboard, Git and MCP), and the template catalog is small. To try the agent path, connect the MCP server at https://mcp.tryhangar.io/mcp in Claude Code or Cursor and ask it to deploy the repo you have open. I'll be here all day. I'd really like to hear where it broke for you or what felt harder than it should.

Hangar

Deploy from your AI agent. Or just git push.

Deploy from your AI agent. Or just git push.