Open Source Elixir Software Development Software - Page 2
Sort By:
Elixir Software Development Software
View 5737 business solutionsBrowse free open source Elixir Software Development Software and projects below. Use the toggles on the left to filter open source Elixir Software Development Software by OS, license, language, programming language, and project status.
-
Gen AI apps are built with MongoDB AtlasMongoDB Atlas is the developer-friendly database used to build, scale, and run gen AI and LLM-powered apps—without needing a separate vector database. Atlas offers built-in vector search, global availability across 115+ regions, and flexible document modeling. Start building AI apps faster, all in one place.
-
Build Securely on Azure with Proven FrameworksMoving to the cloud brings new challenges. How can you manage a larger attack surface while ensuring great network performance? Turn to Fortinet’s Tested Reference Architectures, blueprints for designing and securing cloud environments built by cybersecurity experts. Learn more and explore use cases in this white paper.
-
1
Changelog.com
Changelog makes world-class developer pods
This is the open-source codebase for Changelog, a popular podcast and media site for software developers. Built with Elixir and the Phoenix framework, it serves as a real-world example of a production-grade Phoenix application. The app powers the site’s content publishing, episode distribution, and user interactions, including subscriptions and comments. It emphasizes maintainability and transparency, with clear code structure, tests, and CI/CD workflows. Because the repository is open, developers can study its architecture to learn how Phoenix is used in practice for a high-traffic, media-centric website. It also showcases integration with external services for things like audio hosting, search, and analytics, making it an instructive case study for full-stack Elixir development. -
2
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. -
3
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). -
4
Credo
A static code analysis tool for the Elixir language
Credo is a static code analysis and linting tool for the Elixir language, with an emphasis on promoting code consistency, teaching best practices, and helping developers identify refactoring opportunities, style inconsistencies, and potentially problematic code patterns. Elixir plugin for JetBrains IDEs (IntelliJ IDEA, Rubymine, PHPStorm, PyCharm, etc). Checks your code from style to security, duplication, complexity, and also integrates with coverage. -
Build Securely on AWS with Proven FrameworksMoving to the cloud brings new challenges. How can you manage a larger attack surface while ensuring great network performance? Turn to Fortinet’s Tested Reference Architectures, blueprints for designing and securing cloud environments built by cybersecurity experts. Learn more and explore use cases in this white paper.
-
5
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. -
6
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. -
7
Distillery
Simplify deployments in Elixir with OTP releases
Distillery is a release manager for Elixir applications, designed to package apps into self-contained, deployable artifacts. It automates the process of building OTP releases, handling steps like compilation, dependency bundling, and generating start/stop scripts. Releases built with Distillery include everything needed to run an Elixir app in production, even on machines without Elixir or Erlang installed. It also supports features like configuration providers, hot upgrades, and customizable release pipelines. By managing environment-specific settings, it simplifies deploying the same app to different systems without manual reconfiguration. Distillery has historically been a key tool for production Elixir deployments before Elixir added built-in release functionality, and it remains valuable for teams seeking flexibility in their deployment workflows. -
8
Elchemy
Write Elixir code using statically-typed Elm-like syntax
Elchemy lets you write simple, fast, and quality-type safe code while leveraging both the Elm's safety and Elixir's ecosystem. Elchemy is a set of tools and frameworks, designed to provide a language and an environment as close to Elm programming language as possible, to build server applications in a DSL-like manner for Erlang VM platform, with a readable and efficient Elixir code as an output. ML-like syntax maximizes expressiveness with additional readability and simplicity constraints. Tagged union types and type aliases with type parameters (aka generic types). Powerful type inference means you rarely have to annotate types. Everything gets checked for you by the compiler. The produced code is idiomatic, performant and can be easily read and analyzed without taking a single look at the original source. Elchemy's type system eliminates almost all runtime errors. . -
9
Elixir Companies
A list of companies currently using Elixir in production
elixir-companies is a community-maintained directory of organizations that use Elixir in production. It serves both as a discovery tool for developers curious about who is adopting the language and as a hiring signal for companies wishing to reach the Elixir community. The site categorizes entries by region, industry, and hiring status, making it easy to browse or filter by interests and location. Contributions are handled publicly via pull requests, with maintainers reviewing updates to ensure accuracy and consistency. Beyond simple listings, the project highlights the breadth of Elixir usage—from startups to large enterprises—and helps newcomers see real-world adoption. The codebase itself is an example Phoenix application, offering a transparent, collaborative model for community content. Over time, the directory has become a reference point frequently cited when assessing Elixir’s ecosystem health and job market. -
Photo and Video Editing APIs and SDKsUnlock Picsart's full editing suite by embedding our Editor SDK directly into your platform. Offer your users the power of a full design suite without leaving your site.
-
10
Elixir Language Server
A frontend-independent IDE "smartness" server for Elixir
Implementing features such as auto-complete or go-to-definition for a programming language is not trivial. Traditionally, this work had to be repeated for each development tool and it required a mix of expertise in both the targeted programming language and the programming language internally used by the development tool of choice. The Elixir Language Server (ElixirLS) provides a server that runs in the background, providing IDEs, editors, and other tools with information about Elixir Mix projects. It adheres to the LSP, a standard for frontend-independent IDE support. Debugger integration is accomplished through a similar VS Code Debug Protocol. These pages contain all the information needed to configure your favorite text editor or IDE and to work with the ElixirLS. You will also find instructions on how to configure the server to recognize the structure of your projects and to troubleshoot your installation when things do not work as expected. -
11
ElixirScript
Converts Elixir to JavaScript
The goal is to convert a subset (or full set) of Elixir code to JavaScript, providing the ability to write JavaScript in Elixir. This is done by taking the Elixir AST and converting it into JavaScript AST and then to JavaScript code. This is done using the Elixir-ESTree library. This release includes one major addition and a number of important changes. ElixirScript.Test ElixirScript.Test is a framework for testing Elixir modules that interact with JavaScript via the FFI. For all other modules, ExUnit is still recommended. ElixirScript.Test’s API is similar to ExUnit’s API. ElixirScript.Test files must be placed in a folder named test_elixir_script. Tests are compiled and then are executed using node.js. ElixirScript can now take a path to compile. This is to support the compilation of modules defined in .exs files For more information regarding changes, please check the changelog. -
12
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. -
13
Exq
Job processing library for Elixir - compatible with Resque / Sidekiq
Exq is a job processing library compatible with Resque / Sidekiq for the Elixir language. Exq uses Redis as a store for background processing jobs. Exq handles concurrency, job persistence, job retries, reliable queueing and tracking so you don't have to. Jobs are persistent so they would survive across node restarts. You can use multiple Erlang nodes to process from the same pool of jobs. Exq uses a format that is Resque/Sidekiq compatible. This means you can use it to integrate with existing Rails / Django projects that also use a background job that's Resque compatible - typically with little or no changes needed to your existing apps. However, you can also use Exq standalone. You can also use the Sidekiq UI to view job statuses, as Exq is compatible with the Sidekiq stats format. You can run both Exq and Toniq in the same app for different workers. Exq supports uncapped amount of jobs running, or also allows a max limit per queue. -
14
GraphQL Elixir
GraphQL Elixir
An Elixir implementation of Facebook's GraphQL. This is the core GraphQL query parsing and execution engine whose goal is to be transport, server and datastore agnostic. In order to setup an HTTP server (ie Phoenix) to handle GraphQL queries you will need plug_graphql. Examples for Phoenix can be found at hello_graphql_phoenix, so look here for a starting point for writing your own schemas. Other ways of handling queries will be added in due course. Tokenization is done with leex and parsing with yecc. Both very useful Erlang tools for parsing. Yecc in particular is used by Elixir itself. -
15
Horde
Horde is a distributed Supervisor and Registry
Horde provides a distributed, fault-tolerant Registry and DynamicSupervisor for Elixir applications, letting you run and manage processes across clustered nodes as if they lived on a single machine. It relies on conflict-free replicated data types (CRDTs) to converge membership and process ownership without a central leader, so cluster topology can change freely as nodes join or leave. With Horde.Registry you register processes globally and look them up anywhere, while Horde.DynamicSupervisor starts and migrates children across nodes, rebalancing as capacity or health changes. Because everything runs under OTP supervision, failures are isolated and recoveries are automatic, even during network partitions or rolling deploys. It integrates naturally with common clustering tools and plays well with PubSub, job systems, and presence tracking. The result is predictable, configuration-driven distribution that removes a lot of custom glue typically needed for multi-node Elixir systems. -
16
IElixir
Jupyter's kernel for Elixir programming language
Jupyter's kernel for Elixir. You can manage your packages in runtime with Boyle. Name of the package honours remarkable chemist, Robert Boyle. This package allows you to manage your Elixir virtual enviromnent without need of restarting erlang virtual machine. Boyle installs environment into ./envs/you_new_environment directory and creates new mix project there with requested dependencies. It keeps takes care of fetching, compiling and loading/unloading modules from dependencies list of that environment. -
17
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. -
18
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. -
19
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. -
20
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. -
21
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. -
22
Nerves
Craft and deploy bulletproof embedded software in Elixir
Nerves is the open-source platform and infrastructure you need to build, deploy, and securely manage your fleet of IoT devices at speed and scale. Nerves is written in Elixir, but you don’t have to rewrite everything in Elixir to get the advantages of Nerves, simply bring your own code (like C, C++, Python, Rust, and more) and scale up. Nerves use the Erlang runtime system, known for being distributed, fault-tolerant, soft real-time, and highly available. Nerves has the tools you need to manage every stage of your IoT project, the Nerves Project to build and customize, and NervesHub to deploy and manage your fleets of devices. Avoid hidden bugs and vulnerabilities with Nerves' secure opt-in approach to building. Nerves start minimal and guide you towards security best practices. Nerves helps you bring the principles of agile development to your IoT development cycle. Because Nerves runtime is immutable, Nerves also brings agility to long-term maintenance. -
23
Nostrum
Elixir Discord Library
An Elixir library for the Discord API. Nostrum supports clean REST API implementation and rate-limiting, and automatic, configurable maintenance of local caches of Discord data, with extensive query support and cache swapping functionality. -
24
Oban
Robust job processing in Elixir, backed by modern PostgreSQL
Oban is a robust and flexible background job processing library for Elixir, built on top of PostgreSQL and Ecto; it focuses on delivering reliability, consistency, observability, and historical insight into job execution, making it well-suited for fault-tolerant, production-grade workloads. Oban is a powerful and flexible library that can handle a wide range of background job use cases, and it is well-suited for systems of any size. It provides a simple and consistent API for scheduling and performing jobs, and it is built to be fault-tolerant and easy to monitor. Oban is fundamentally different from other background job processing tools because it retains job data for historic metrics and inspection. You can leave your application running indefinitely without worrying about jobs being lost or orphaned due to crashes. -
25
Plug
Compose web applications with functions
Plug is a specification and set of utilities for building composable modules in Elixir web applications. It defines a standard connection interface, allowing developers to create “plugs” that act as middleware for handling requests and responses. Examples include parsing parameters, managing sessions, logging, or authentication, all of which can be plugged into a pipeline. Plug serves as the foundation for the Phoenix framework, which builds on it to deliver a full-featured web stack. The library supports both synchronous and streaming responses, making it adaptable to various web scenarios. Its modularity and composability promote clean, reusable code while remaining lightweight enough for microservices and APIs outside of Phoenix.
