Phoenix
Web framework for the Elixir language, built on the Erlang BEAM VM.
HN commenters praise Phoenix as an enjoyable Elixir web framework, with one calling it the best they have used,12 and value the BEAM/OTP reliability it builds on.3 The main caveat is complexity: one commenter found it harder to get things done in than Rails,4 and another positions it for enterprise complexity rather than minimal apps.5
Why people recommend it
Developer experience · 2
Commenters describe using Phoenix as amazing, and one calls it the best web framework they have used.
“has Phoenix, the best web framework I've ever used”
“We use Elixir and Phoenix for our application, which is quite an amazing experience.”
BEAM/OTP reliability · 1
One builder chose Elixir and Phoenix because BEAM/OTP solved their agent orchestration challenges more reliably and elegantly.
“the BEAM/OTP capabilities genuinely worked more reliably and elegantly to solve our orchestrator challenges”
Contexts structure · 1
One commenter has AI coding tools use Phoenix Contexts to push them toward following BDD.
“My go-to for forcing AI to at least attempt to follow BDD has been to demand that it use Phoenix Contexts.”
Caveats and dissent
Productivity vs Rails · 1
One former Rails user found Phoenix a lot more difficult to get things done in and doesn't understand the hype.
“I used Rails and then i tried Phoenix and it was lot more difficult to get things done.”
Complexity · 1
The author of a competing minimalist framework describes Phoenix as the choice for enterprise complexity.
“Not for enterprise complexity – that's what Phoenix is for.”
Often compared with
Who recommends it in their own words
Threads where it came up
- PHP2Shell: AI uncovers critical RCE in PHP 1 mention
- Gleam doesn't compile to Erlang source anymore 1 mention
- Ask HN: Show your micro-SaaS 1 mention
- My practical approach to surfing the web safely 1 mention
- Does anyone run Postgres without PgBouncer? 1 mention
- Yadda 3.0.0: BDD in the Age of AI Agents 1 mention
Data: phoenix.json. Quotes are verbatim; the verdict and theme labels are written by a model from these comments, and every clause links to its sources.
All comments 14
“I slopcoded my own forum software in Elixir/Phoenix recently”
“has Phoenix, the best web framework I've ever used”
“We use Elixir and Phoenix for our application, which is quite an amazing experience.”
“anybody using firefox should consider the patches by celenity at https://codeberg.org/celenity/Phoenix”
“I use the Ecto connection pool when using Elixir/Phoenix.”
“My go-to for forcing AI to at least attempt to follow BDD has been to demand that it use Phoenix Contexts.”
“I do use elixir / phoenix”
“the BEAM/OTP capabilities genuinely worked more reliably and elegantly to solve our orchestrator challenges”
“Backend is in Elixir (Phoenix/Absinthe/Postgres) hosted on GCP”
“On my Mac I use a combination of Phoenix and Hyperkey to capture capslock + key combinations”
“I used Rails and then i tried Phoenix and it was lot more difficult to get things done.”
“Not for enterprise complexity – that's what Phoenix is for.”
“this might make a good alternative to Xwayland though, which can be exciting.”
“building with Elixir and Phoenix”