Open Source Elixir Frameworks
Sort By:
Elixir Frameworks
View 159 business solutionsBrowse free open source Elixir Frameworks and projects below. Use the toggles on the left to filter open source Elixir Frameworks by OS, license, language, programming language, and project status.
-
Our Free Plans just got better! | Auth0You asked, we delivered! Auth0 is excited to expand our Free and Paid plans to include more options so you can focus on building, deploying, and scaling applications without having to worry about your security. Auth0 now, thank yourself later.
-
MyQ Print Management SoftwareBoost your digital or traditional workplace with MyQ’s secure print and scan solutions that respect your time and help you focus on what you do best.
-
1
Pinchflat
Your next YouTube media manager
Pinchflat is a self-hosted YouTube media manager that automates downloading videos from channels or playlists using yt-dlp. It runs as a lightweight, containerized app and is ideal for archiving or feeding media center setups like Plex, Jellyfin, or Kodi. -
2
Phoenix Framework
Peace of mind from prototype to production
Phoenix is a high-performance, productive web development framework written in Elixir. It runs on the Erlang VM (BEAM). It is designed to support both traditional request/response web applications. It also supports real-time, soft-real-time applications via WebSockets, channels, PubSub, and presence features. Phoenix emphasizes fault tolerance, scalability, and developer productivity. It provides tools like code generators, LiveView integration, templating, routing, and a flexible plug pipeline. Phoenix runs on the Erlang VM with the ability to handle millions of WebSocket connections alongside Elixir's tooling for building robust systems. Know who is connected right now, across one or dozens of nodes, by using our built-in Presence. No dependency required. -
3
Live Svelte
Svelte inside Phoenix LiveView with seamless end-to-end reactivity
live_svelte bridges Phoenix LiveView with Svelte components, letting you blend server-driven UIs and client-side interactivity in a single application. It mounts Svelte components from HEEx templates and wires props and events through a small interop layer, so data flows cleanly between LiveView assigns and Svelte state. The integration supports dispatching client events back to LiveView and pushing updates down to the component without writing custom glue for every case. This makes it straightforward to adopt Svelte for isolated, highly interactive widgets—charts, editors, complex form controls—without abandoning LiveView’s real-time model. The project aims to keep build tooling minimal and predictable, so teams can continue using familiar Phoenix asset pipelines. By enabling “islands” of Svelte within LiveView pages, live_svelte offers a pragmatic path to richer UX while preserving Elixir’s server-centric simplicity. -
4
Desktop
Building Local-First apps for Windows, MacOS, Linux, iOS and Android
desktop enables building cross-platform desktop applications with Elixir by pairing a Phoenix/LiveView UI with a native webview shell. The approach keeps application logic on the BEAM—supervised, fault-tolerant, and hot-reload-friendly—while rendering an HTML/CSS/JS interface inside the system’s embedded browser engine. It offers conveniences for packaging and distribution on Windows, macOS, and Linux, including app metadata, icons, and startup integration. The library exposes desktop-specific affordances such as system tray menus, window management, and notifications, so applications feel native rather than like generic web wrappers. Because LiveView drives the UI, state lives on the server process, enabling real-time updates without heavy client frameworks. The result is a productive stack for tools, dashboards, and utilities where Elixir’s concurrency and resilience shine on the desktop. Teams get to reuse their Phoenix skills and still ship a polished native app experience. -
D&B Hoovers is Your Sales AcceleratorSpeed up sales prospecting with the rich audience targeting capabilities of D&B Hoovers so you can spend more sales time closing.
-
5
Membrane Core
The core of Membrane Framework, multimedia processing framework
membrane_core is the foundation of the Membrane multimedia framework for Elixir, providing the abstractions and runtime needed to build real-time audio and video pipelines. It models media processing as a graph of lightweight, supervised OTP processes—elements connected by links—so work is isolated, fault-tolerant, and easy to scale or reconfigure at runtime. The core defines a clear lifecycle and callback API for elements, plus concepts like buffers, events, and capabilities/format negotiation to keep components interoperable and type-safe. Back-pressure, scheduling, and time synchronization are handled by the framework, enabling low-latency streaming and precise playback control without ad-hoc concurrency code. Developers compose pipelines from reusable building blocks and can dynamically add, remove, or switch elements while the system is running. -
6
Ash
A declarative, extensible framework for building Elixir applications
Ash is a declarative framework for building resource-oriented apps in Elixir. It emphasizes composability, DSL-driven definitions of resources/actions/relationships, and extensibility through plugins for API, database, and UI layers. -
7
Broadway
Concurrent and multi-stage data ingestion and data processing
Broadway is a data processing library for Elixir designed to handle high-throughput, concurrent workloads with ease. It provides an abstraction for defining pipelines that consume data from sources like RabbitMQ, Kafka, Amazon SQS, or custom producers. Each pipeline is fault-tolerant and backpressure-aware, ensuring stable throughput even under load. The library integrates seamlessly with GenStage and OTP supervision trees, making it highly resilient in production. Developers can enrich pipelines with batching, concurrency control, and metrics reporting, simplifying the management of complex data ingestion and processing systems. Broadway is often used for event processing, stream handling, and background jobs, offering both performance and clarity in Elixir’s functional style. -
8
Cog
Bringing the power of the command line to chat
Cog brings the power of the command line to the place you collaborate with your team all the time, your chat window. Powerful access control means you can collaborate around even the most sensitive tasks with confidence. A focus on extensibility and adaptability means that you can respond quickly to the unexpected, without your team losing visibility. Use Cog to manage your infrastructure, support peer learning, and conduct collaborative research at the same time, right from chat. Cog is easy to install and simple to operate while remaining powerful enough to handle complex enterprise workflows. Cog brings the power of the command line to the place you collaborate with your team all the time, your chat window. Powerful access control means you can collaborate around even the most sensitive tasks with confidence. A focus on extensibility and adaptability means that you can respond quickly to the unexpected, without your team losing visibility. -
9
Commanded
Use Commanded to build Elixir CQRS/ES applications
Commanded is an Elixir framework for implementing CQRS (Command Query Responsibility Segregation) and Event Sourcing patterns. It provides domain-driven design tools—aggregates, commands, events, and projections—backed by an event store (e.g. PostgreSQL). -
Financial reporting cloud-based software.The software is cloud based and automates complexities around consolidating and reporting for groups with multiple year ends, currencies and ERP systems with a slice and dice approach to reporting. While retaining the structure, control and validation needed in a financial reporting tool, we’ve managed to keep things flexible.
-
10
Dialyxir
Mix tasks to simplify use of Dialyzer in Elixir projects
Mix tasks to simplify use of Dialyzer in Elixir projects. Elixir 1.6 is required, to support the new pretty printing feature. If your project is not yet on 1.6, continue to specify 0.5 in your mix deps. Warning messages have been greatly improved, but are filtered through the legacy formatter to support your existing ignore files. You can optionally use the new Elixir term format for ignore files. You may want to use the --format short argument in your CI pipelines. There are several formats, also there is a new explain feature - for details see CLI options. If you are planning to use Dialyzer with an application built with the Phoenix Framework, check out the Quickstart wiki. Use dialyxir from the directory of the mix project you want to analyze; a PLT file will be created or updated if required and the project will be automatically compiled. -
11
ExAdmin
ExAdmin is an auto administration package for Elixir
ExAdmin is an auto-administration package for Elixir and the Phoenix Framework. This version has been updated to support both Ecto 1.1 and Ecto 2.0. ExAdmin is an auto-administration package for Elixir and the Phoenix Framework, a port/inspiration of ActiveAdmin for Ruby on Rails. Checkout the Live Demo. The source code can be found at ExAdmin Demo. Checkout this Additional Live Demo for examples of many-to-many relationships, nested attributes, and authentication. ExAdmin is an add on for an application using the Phoenix Framework to create a CRUD administration tool with little or no code. By running a few mix tasks to define which Ecto Models you want to administer, you will have something that works with no additional code. ExAdmin will use your schema's changesets. By default we call the changeset function on your schema, although you can configure the changeset we use for update and create separately. -
12
Kitto
Kitto is a framework for interactive dashboards written in Elixir
Kitto is a framework for interactive dashboards written in Elixir. The source for the demo dashboards can be found at: kittoframework/demo. Jobs are supervised processes running concurrently. Widgets are coded in the popular React library. Uses a modern asset tool-chain, Webpack. Allows streaming SSE to numerous clients concurrently with low memory/CPU footprint. Easy to deploy using the provided Docker images, Heroku (guide) or Distillery (guide). Can serve assets in production. Keeps stats about defined jobs and comes with a dashboard to monitor them (demo). Can apply exponential back-offs to failing jobs. Reloads code upon change in development. Kitto is a framework to help you create dashboards, written in Elixir / React. Widgets live in widgets/ are compiled using Webpack and are automatically loaded in the dashboards. Assets are rebuilt upon a change in development but have to be compiled for production. -
13
Maru
Elixir RESTful Framework
Maru is a DSL for building HTTP/REST APIs in Elixir that emphasizes concise routing, parameter validation, and versioning. Inspired by Ruby’s Grape, it lets you describe endpoints declaratively—paths, verbs, and nested scopes—while composing reusable middleware via Plug. Strong parameter parsing and validators help keep controllers clean by moving input checking and coercion into the route layer. Built-in support for namespacing and API versioning simplifies rolling changes or maintaining multiple client generations side by side. Error handling, helpers, and content negotiation are wired into the DSL, so common cross-cutting concerns are consistent across endpoints. Because Maru sits on Plug and Cowboy, it retains Elixir’s performance and concurrency while making API development fast and readable. -
14
Nebulex
In-memory and distributed caching toolkit for Elixir
Nebulex provides support for transparently adding caching into an existing Elixir application. Similar to Ecto, the caching abstraction allows consistent use of various caching solutions with minimal impact on the code. Nebulex cache abstraction shields developers from directly dealing with the underlying caching implementations, such as Redis, Memcached, or even other Elixir cache implementations like Cachex. Additionally, it provides totally out-of-box features such as cache usage patterns, declarative annotation-based caching, and distributed cache topologies, among others. For intensive workloads, you may want to use :shards as the backend for the local adapter and having partitioned tables. In such a case, you have to add :shards to the dependency list. For enabling the usage of declarative annotation-based caching via decorators, you have to add :decorator to the dependency list. -
15
Phoenix LiveView
Rich, real-time user experiences with server-rendered HTML
Phoenix LiveView is an Elixir library that enables rich, real-time user experiences by using server-rendered HTML over WebSockets, providing seamless dynamic interactivity without needing front-end JavaScript frameworks. It integrates deeply with Phoenix and ships by default in new Phoenix applications. LiveView brings a unified experience to building web applications. You no longer have to split work between client and server, across different toolings, layers, and abstractions. Instead, LiveView enriches the server with a declarative and powerful model while keeping your code closer to your data (and ultimately your source of truth). -
16
Sobelow
Security-focused static analysis for the Phoenix Framework
Sobelow is a security-focused static analysis tool for the Phoenix framework. For security researchers, it is a useful tool for getting a quick view of points-of-interest. For project maintainers, it can be used to prevent the introduction of a number of common vulnerabilities. Potential vulnerabilities are flagged in different colors according to confidence in their insecurity. High confidence is red, medium confidence is yellow, and low confidence is green. A finding is typically marked "low confidence" if it looks like a function could be used insecurely, but it cannot reliably be determined if the function accepts user-supplied input. That is to say, if a finding is marked green, it may be critically insecure, but it will require greater manual validation. This project is in constant development, and additional vulnerabilities will be flagged as time goes on. If you encounter a bug, or would like to request additional features or security checks, please open an issue! -
17
Standard Webhooks
The Standard Webhooks specification
Standard Webhooks is a community-driven specification and set of open-source tools designed to make webhooks consistent, secure, and interoperable across providers. The project defines strict guidelines covering aspects like signature formats, headers, timestamps, replay protection, and forward compatibility. It includes reference implementations for signature verification and signing across multiple languages such as Python, JavaScript/TypeScript, Go, Rust, Ruby, PHP, C#, Java, and Elixir, along with additional community SDKs. The initiative is guided by a technical steering committee with members from companies like Zapier, Twilio, Mux, ngrok, Supabase, Svix, and Kong. Standard Webhooks matters because it eliminates the fragmentation of webhook implementations, reducing consumer effort and enabling seamless verification in apps or even directly in API gateways. By unifying best practices, it improves developer experience, enhances security, and enables new ecosystem tools. -
18
Surface
A server-side rendering component library for Phoenix
Surface is a component-based UI library for Phoenix LiveView that brings a declarative, template-driven approach to building interactive interfaces. Inspired by frameworks like React, it introduces components with typed properties, slots, and macros to simplify complex UIs. Developers can create reusable, encapsulated components that integrate seamlessly with LiveView’s server-rendered real-time model. Surface emphasizes readability, making templates feel closer to HTML while retaining Elixir’s functional power. It also provides form helpers, event bindings, and a growing ecosystem of ready-to-use UI components. By combining the productivity of declarative components with LiveView’s real-time updates, Surface enables rich, interactive apps without requiring a separate frontend framework like React or Vue. -
19
gRPC Elixir
An Elixir implementation of gRPC
The Gun library doesn't have a full 2.0 release yet, so we depend on :grcp_gun 2.0.1 for now. This is the same as :gun 2.0.0-rc.2, but Hex doesn't let us depend on RC versions for releases. Generate Elixir code from the proto file as protobuf-elixir shows(especially the gRPC Support section). Implement the server-side code and remember to return the expected message types. You can start the gRPC server as a supervised process. First, add GRPC.Server.Supervisor to your supervision tree.
- Previous
- You're on page 1
- Next
