Skip to content

SYSTEM Cited by 1 source

Phoenix (Elixir web framework)

Phoenix is the dominant web framework for Elixir. Created by Chris McCord, it runs on BEAM and centres on real-time / collaborative applications built around Channels (WebSocket abstraction), Presence (distributed presence tracking), and LiveView (server-rendered real-time UI with seamless live reload).

Role on this wiki

Phoenix appears on this wiki primarily as:

  • The framework Phoenix.new is tuned for — the 2025-06-20 Fly.io post frames the agent as "batteries-included fully-online coding agent tailored to Elixir and Phoenix" and demonstrates it building LiveView apps end-to-end (Presence + Channels + Ecto + real databases) as a concrete concepts/vibe-coding target.
  • The "real-time collaborative applications" design target McCord names as the reason an agent benefits from a full browser: LiveView's live-reload semantics make the agent's edit → build → verify loop natural across a WebSocket-driven page.
  • A load-bearing ecosystem piece on the BEAM stack adjacent to Livebook and FLAME on Fly.io.

Key architectural properties (as cited by Phoenix.new context)

  • Channels / WebSockets — Phoenix's native transport for real-time bidirectional messaging between browser and server, built on BEAM processes per connection.
  • Presence — distributed-state CRDT-adjacent primitive for tracking which users / processes are currently connected, integrating with Channels.
  • LiveView — server-rendered UIs that push partial DOM updates over Channels, giving "seamless live reload" the agent can observe through its own driven browser when verifying changes.
  • Ecto — the database wrapper Phoenix.new can model against live schemas in a pre-existing Postgres/MySQL database.
  • Mix — the build tool (mix phx.server, mix test, mix deps.get) the agent uses inside the Phoenix.new VM.

Seen in

Last updated · 200 distilled / 1,178 read