This product was not featured by Product Hunt yet. It will not be visible on their landing page and won't be ranked (cannot win product of the day regardless of upvotes).
Phelix
Zero-downtime deploys for Go & Rust, with MCP for AI agents
Phelix is a single-binary deployment tool for Go and Rust apps that runs on your own servers. Build,version, and deploy with zero downtime, health-check-gated traffic switching, encrypted environment snapshots, and instant rollback. Use blue-green, rolling, or canary rollouts with or without Docker. Built-in MCP support lets coding agents inspect services and prepare deployment plans through Phelix's existing authorization and approval pipeline. An optional dashboard adds multi-server monitoring
Hey Product Hunt! I'm Mohammad, the solo developer behind Phelix.
I built Phelix because deploying services on my own servers kept turning into the same routine: build the app, replace the running process, check whether it came back, and hope I had a rollback path if something went wrong.
Kubernetes felt like more infrastructure than I needed for a small fleet of services. But a collection of shell scripts wasn't the deployment workflow I wanted either.
So I built Phelix as a single binary for Go and Rust applications. It versions builds on disk, keeps the current version running until the new one passes its health checks, snapshots encrypted environment variables per version, and makes rollback a deliberate, repeatable operation.
Since v1.0.0, I've continued improving the deployment workflow. Phelix is now at v1.1.2, and one of the biggest additions is built-in MCP support for coding agents.
Why MCP?
AI agents are getting better at writing code, but shipping that code safely is a different problem.
Phelix gives compatible agents such as Claude Code and Codex a controlled way to inspect application context, create deployment or rollback plans, and apply plans through Phelix's existing execution pipeline.
Plans are immutable and content-addressed. Execution remains behind the authorization boundary, and deployments can require explicit human approval. MCP doesn't introduce a separate deployment engine or bypass the existing safeguards.
The MCP server runs locally over stdio, without opening a network listener. The goal is simple: let agents help with deployment work without making production changes an unreviewed side effect of a prompt.
Phelix is still a solo-built project, and I'm building it around real backend workloads rather than claiming it has been battle-tested everywhere.
I'd love your feedback on two things:
1. How do you currently deploy Go or Rust services on your own servers? 2. Would you let a coding agent prepare a deployment plan if you could inspect and approve the exact plan before execution?
Thanks for checking out Phelix. I'm happy to answer technical questions and hear what you'd change.
No comment highlights available yet. Please check back later!
About Phelix on Product Hunt
“Zero-downtime deploys for Go & Rust, with MCP for AI agents”
Phelix was submitted on Product Hunt and earned 0 upvotes and 1 comments, placing #34 on the daily leaderboard. Phelix is a single-binary deployment tool for Go and Rust apps that runs on your own servers. Build,version, and deploy with zero downtime, health-check-gated traffic switching, encrypted environment snapshots, and instant rollback. Use blue-green, rolling, or canary rollouts with or without Docker. Built-in MCP support lets coding agents inspect services and prepare deployment plans through Phelix's existing authorization and approval pipeline. An optional dashboard adds multi-server monitoring
Phelix was featured in Productivity (663.6k followers), Developer Tools (521.5k followers) and GitHub (41.4k followers) on Product Hunt. Together, these topics include over 291.9k products, making this a competitive space to launch in.
Who hunted Phelix?
Phelix was hunted by Mohammad Abdorrahmani. A “hunter” on Product Hunt is the community member who submits a product to the platform — uploading the images, the link, and tagging the makers behind it. Hunters typically write the first comment explaining why a product is worth attention, and their followers are notified the moment they post. Around 79% of featured launches on Product Hunt are self-hunted by their makers, but a well-known hunter still acts as a signal of quality to the rest of the community. See the full all-time top hunters leaderboard to discover who is shaping the Product Hunt ecosystem.
Want to see how Phelix stacked up against nearby launches in real time? Check out the live launch dashboard for upvote speed charts, proximity comparisons, and more analytics.
Mohammad Abdorrahmani
Hey Product Hunt! I'm Mohammad, the solo developer behind Phelix.
I built Phelix because deploying services on my own servers kept turning into the same routine: build the app, replace the running process, check whether it came back, and hope I had a rollback path if something went wrong.
Kubernetes felt like more infrastructure than I needed for a small fleet of services. But a collection of shell scripts wasn't the deployment workflow I wanted either.
So I built Phelix as a single binary for Go and Rust applications. It versions builds on disk, keeps the current version running until the new one passes its health checks, snapshots encrypted environment variables per version, and makes rollback a deliberate, repeatable operation.
Since v1.0.0, I've continued improving the deployment workflow. Phelix is now at v1.1.2, and one of the biggest additions is built-in MCP support for coding agents.
Why MCP?
AI agents are getting better at writing code, but shipping that code safely is a different problem.
Phelix gives compatible agents such as Claude Code and Codex a controlled way to inspect application context, create deployment or rollback plans, and apply plans through Phelix's existing execution pipeline.
Plans are immutable and content-addressed. Execution remains behind the authorization boundary, and deployments can require explicit human approval. MCP doesn't introduce a separate deployment engine or bypass the existing safeguards.
The MCP server runs locally over stdio, without opening a network listener. The goal is simple: let agents help with deployment work without making production changes an unreviewed side effect of a prompt.
Phelix is still a solo-built project, and I'm building it around real backend workloads rather than claiming it has been battle-tested everywhere.
I'd love your feedback on two things:
1. How do you currently deploy Go or Rust services on your own servers?
2. Would you let a coding agent prepare a deployment plan if you could inspect and approve the exact plan before execution?
Thanks for checking out Phelix. I'm happy to answer technical questions and hear what you'd change.