Peace of mind from prototype to production
23.1k
Stars
3.1k
Forks
43
Open issues
30
Contributors
AI Analysis
Phoenix is a web framework for Elixir that emphasizes real-time capabilities, distributed systems, and production reliability. It serves developers building APIs, real-time applications, and web services who value concurrent programming and fault-tolerant architectures. Phoenix is general-purpose and widely adopted, benefiting teams of all sizes from startups to enterprises.
Inferred from signals mentioned in the README (tests, CI, type safety) — not a review of the actual code.
AI's overall editorial judgment — not an average of the bars above, can weigh other factors too.
Phoenix: Elixir's mature web framework powering high-concurrency production apps since 2014
Phoenix is the primary web framework for the Elixir language, built on the Erlang VM (BEAM). It solves the problem of building scalable, fault-tolerant web applications with low latency and high concurrency. Its audience is primarily Elixir developers building APIs, real-time features, and full-stack web products. Phoenix LiveView (a companion library) enables server-rendered interactive UIs without JavaScript frameworks. It is the de facto standard in the Elixir ecosystem and is used in production by companies such as Discord, Bleacher Report, and Changelog.
Created by Chris McCord in January 2014, Phoenix drew early inspiration from Ruby on Rails but was designed from the start around Elixir and the BEAM's concurrency model. It reached v1.0 in 2015 and has since shipped major features like Channels (WebSockets), LiveView, and PubSub.
Growth was driven by the broader adoption of Elixir, particularly after high-profile endorsements (Discord's millions of concurrent connections story) and the launch of Phoenix LiveView in 2019, which attracted frontend developers seeking alternatives to SPA complexity. Star growth has plateaued at a slow pace (4 stars in 7 days as of mid-2026), reflecting that it is a mature, established project rather than a trending newcomer. The Elixir ecosystem remains relatively niche, capping the addressable audience.
Well-documented production usage: Discord (millions of concurrent users), Bleacher Report, Changelog, and numerous Elixir-first startups. Hex.pm download statistics (not directly visible here) are publicly available and consistently place Phoenix among the most-downloaded Elixir packages. Production adoption is verified and substantial within the Elixir ecosystem.
Likely follows a layered MVC architecture with pluggable middleware (Plug), a router, controllers, views/templates (HEEx), and a real-time layer (Channels/PubSub). Appears to ship with a generator CLI (phx.new), asset pipeline integration, and first-class WebSocket support. The installer and core are maintained as separate components within the monorepo.
CI badge is present and points to GitHub Actions workflows, suggesting automated testing is active. Specific coverage percentage not documented in README.
Last push was June 17, 2026 — 7 days before evaluation date. This indicates active, ongoing development. With 23K stars, 3K forks, and continuous commits over 12 years, the project shows strong long-term maintenance health. The core team appears stable and commercially supported through DockYard sponsorship.
ADOPT IF: you are committed to Elixir, need high concurrency or real-time features, and want a mature, well-documented framework with strong production precedent. AVOID IF: your team has no Elixir experience and the cost of language adoption outweighs the concurrency benefits, or if you need a wider third-party library ecosystem. MONITOR IF: you are evaluating Elixir for your stack and want to track LiveView's evolution as an alternative to React/Vue-based SPAs.
Independent dimensions
Mainstream potential
4/10
Technical importance
9/10
Adoption evidence
8/10
- Elixir's relatively small developer pool creates hiring and staffing risk for teams not already invested in the language.
- The broader ecosystem of third-party libraries and integrations is significantly smaller than Rails, Django, or Node, requiring more custom implementation at the edges.
- Despite strong technical merits, Phoenix's mainstream growth is constrained by the niche status of Elixir; this is unlikely to change dramatically.
- Tight coupling to BEAM-specific paradigms (processes, OTP) means skills and patterns do not transfer to other language ecosystems easily.
- DockYard is a named sponsor; commercial sponsorship changes could theoretically affect core team continuity, though the project has shown resilience over 12 years.
Phoenix will remain the stable, dominant framework within the Elixir ecosystem for the foreseeable future. LiveView will continue to be its primary growth driver. Overall ecosystem size is unlikely to grow dramatically, but the existing user base will remain loyal and the project will continue to mature.
Newsletter
Get analyses like this every Monday
Free weekly digest of the most interesting open-source discoveries.
Languages
Information
- Website
- https://www.phoenixframework.org
- Language
- Elixir
- License
- MIT
- Last updated
- 1d ago
- Created
- 152mo ago
- Analyzed with
- anthropic/claude-haiku-4-5
Stars over time
Contributors over time
Top 100 contributors only — repos with more will plateau at 100.
Top contributors
Recent releases
Similar repos
phoenixframework/phoenix_live_view
Phoenix LiveView is a server-rendered web framework for Elixir that enables...
phoenixframework/phoenix_live_dashboard
Phoenix LiveDashboard provides real-time performance monitoring and debugging...
| Repository | Stars | Week Δ | Language | Score | Updated |
|---|---|---|---|---|---|
|
phoenixframework/phoenix
this
|
23.1k | +16 | Elixir | 9/10 | 1d ago |
|
phoenixframework/phoenix_live_view
|
6.8k | — | Elixir | 9/10 | 1w ago |
|
phoenixframework/phoenix_live_dashboard
|
2.2k | — | Elixir | 8/10 | 2mo ago |
 phcode-dev/phoenix
|
2.9k | — | JavaScript | 7/10 | 3d ago |
|
phoenixframework/flame
|
1.2k | — | Elixir | 8/10 | 7mo ago |
 mirego/elixir-boilerplate
|
1.2k | — | Elixir | 8/10 | 3mo ago |
Rails targets a broader developer base with a larger ecosystem and hiring pool. Phoenix offers better concurrency and fault tolerance via BEAM, but requires learning Elixir, which limits adoption.
Django has a much larger community and library ecosystem. Phoenix's concurrency model is superior for real-time workloads; Django requires additional infrastructure (Celery, Redis) for comparable async behavior.
Node handles async I/O well but lacks Phoenix's process isolation, fault tolerance, and the LiveView paradigm. Phoenix's BEAM underpinning provides stronger reliability guarantees out of the box.
Plug is Phoenix's foundation. Using Plug directly gives more control but requires assembling everything manually. Phoenix provides a full-featured, opinionated layer on top with generators and conventions.
LiveView is not a competitor but a major extension that differentiates Phoenix from all other frameworks by enabling stateful server-rendered UIs — a significant reason developers choose Phoenix today.
