Open Source Elixir Software Development Software
Sort By:
Elixir Software Development Software
View 5828 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.
-
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.
-
Cloud tools for web scraping and data extractionAutomate web data collection with cloud tools that handle anti-bot measures, browser rendering, and data transformation out of the box. Extract content from any website, push to vector databases for RAG workflows, or pipe directly into your apps via API. Schedule runs, set up webhooks, and connect to your existing stack. Free tier available, then scale as you need to.
-
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
Absinthe
The GraphQL toolkit for Elixir
Absinthe is the GraphQL toolkit for Elixir, an implementation of the GraphQL specification built to suit the language's capabilities and idiomatic style. If you're new to GraphQL, we suggest you read up a bit on GraphQL's foundational principles before you dive into Absinthe. Absinthe's functionality generally falls into two broad areas. Defines the structure of data entities and the relationships between, as well as the available queries, mutations, and subscriptions, using an elegant collection of declarative macros. Absinthe schemas are defined using easy-to-read macros that build and verify their structure at compile-time, preventing runtime errors and increasing performance. The entire query processing pipeline is configurable. Add, swap out, or remove the parser, individual validations, or resolution logic at will, even on a per-document basis. Absinthe includes a number of advanced resolution features. -
3
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. -
4
Tesla
The flexible HTTP client library for Elixir
The flexible HTTP client library for Elixir, with support for middleware and multiple adapters. Tesla is an HTTP client loosely based on Faraday. It embraces the concept of middleware when processing the request/response cycle. Define module with use Tesla and choose from a variety of middleware. Tesla is built around the concept of composable middlewares. This is very similar to how Plug Router works. All HTTP functions, such as Tesla.get/3 and Tesla.post/4, can take a dynamic client as the first argument. This allows using convenient syntax for modifying the behavior in runtime. Tesla supports multiple HTTP adapter that do the actual HTTP request processing. Each piece of the stream will be encoded as JSON and sent as a new line (conforming to JSON stream format). You can set the adapter to Tesla.Mock in tests. -
AI-First Supply Chain ManagementLogility is a market-leading provider of AI-first supply chain management solutions engineered to help organizations build sustainable digital supply chains that improve people’s lives and the world we live in. The company’s approach is designed to reimagine supply chain planning by shifting away from traditional “what happened” processes to an AI-driven strategy that combines the power of humans and machines to predict and be ready for what’s coming. Logility’s fully integrated, end-to-end platform helps clients know faster, turn uncertainty into opportunity, and transform the supply chain from a cost center to an engine for growth.
-
5
Scenic
Core Scenic library
Scenic is a UI framework built directly on Elixir/Erlang/OTP for creating polished, fault-tolerant client applications. It targets both embedded/IoT and desktop scenarios, leveraging OpenGL for 2D rendering and embracing the OTP ecosystem for concurrency and reliability. -
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
Elixir
Dynamic, functional language designed for building scalable apps
Elixir is a dynamic, functional language for building scalable and maintainable applications. Elixir leverages the Erlang VM, known for running low-latency, distributed, and fault-tolerant systems. Elixir is successfully used in web development, embedded software, data ingestion, and multimedia processing, across a wide range of industries. All Elixir code runs inside lightweight threads of execution (called processes) that are isolated and exchange information via messages. Due to their lightweight nature, it is not uncommon to have hundreds of thousands of processes running concurrently in the same machine. Isolation allows processes to be garbage collected independently, reducing system-wide pauses, and using all machine resources as efficiently as possible (vertical scaling). Processes are also able to communicate with other processes running on different machines in the same network. -
8
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. -
9
Wallaby
Concurrent browser tests for your Elixir web apps
Wallaby helps you test your web applications by simulating realistic user interactions. By default, it runs each test case concurrently and manages browsers for you. Here's an example test for a simple Todo application. Because Wallaby manages multiple browsers for you, it's possible to test several users interacting with a page simultaneously. Read on to see what else Wallaby can do or check out the Official Documentation. Wallaby also requires bash to be installed. Generally, bash is widely available, but it does not come pre-installed on Alpine Linux. If you're testing a Phoenix application with Ecto and a database that supports sandbox mode, you can enable concurrent testing by adding the Phoenix.Ecto.SQL.Sandbox plug to your Endpoint. It's important that this is at the top of endpoint.ex before any other plugs. -
Nonprofit Budgeting SoftwareMartus' collaborative and easy-to-use budgeting and reporting platform will save you hundreds of hours each year. It's designed to make the entire budgeting process easier and create unlimited financial transparency.
-
10
Axon
Nx-powered Neural Networks
Nx-powered Neural Networks for Elixir. Axon consists of the following components. Functional API – A low-level API of numerical definitions (defn) of which all other APIs build on. Model Creation API – A high-level model creation API which manages model initialization and application. Optimization API – An API for creating and using first-order optimization techniques based on the Optax library. Training API – An API for quickly training models, inspired by PyTorch Ignite. Axon provides abstractions that enable easy integration while maintaining a level of separation between each component. You should be able to use any of the APIs without dependencies on others. By decoupling the APIs, Axon gives you full control over each aspect of creating and training a neural network. At the lowest-level, Axon consists of a number of modules with functional implementations of common methods in deep learning. -
11
Bumblebee
Pre-trained Neural Network models in Axon
Bumblebee provides pre-trained Neural Network models on top of Axon. It includes integration with Models, allowing anyone to download and perform Machine Learning tasks with few lines of code. The best way to get started with Bumblebee is with Livebook. Our announcement video shows how to use Livebook's Smart Cells to perform different Neural Network tasks with a few clicks. You can then tweak the code and deploy it. First, add Bumblebee and EXLA as dependencies in your mix.exs. EXLA is an optional dependency but an important one as it allows you to compile models just-in-time and run them on CPU/GPU. -
12
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. -
13
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. -
14
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. -
15
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. -
16
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. -
17
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. -
18
Pow Auth
Robust, modular, and extendable user authentication system
A robust, modular and extendable. User management solution. Pow is a complete authentication and user management library built in Elixir that works out-of-the-box for Phoenix and Plug-based applications while being fully customizable. Pow gives you out-of-the-box authentication and user management for your Phoenix or Plug-based app. Functionally built so it's fully customizable. Strong security is a core tenet of Pow's philosophy, which is why Pow by default uses short lived sessions. If your app requires stateless tokens, the authorization layer can be replaced in minutes. Pow has been used in countless production apps and is a "batteries included" library for production. The cache backend store used for session storage can be replaced with any key-value store of your choice. The built-in Mnesia cache module works both for clusters and single-machine persistence, which can auto-connect to the cluster on startup and self-heal after netsplit. -
19
Semaphore
Semaphore is an open source CI/CD platform
Semaphore is a continuous integration and delivery platform that streamlines building, testing, and deploying software with an emphasis on speed and developer experience. Pipelines are defined declaratively and support parallel jobs, dependency fan-outs, and matrix builds to exercise many environments at once. First-class Docker and Kubernetes workflows, along with layer caching and artifacts, help keep containerized builds fast and reproducible. Secrets management, environment promotion, and approvals enable robust delivery gates from pull request to production. The system integrates with popular VCS providers and chat tools, surfacing real-time status, logs, and insights so teams can diagnose failures quickly. With autoscaling workers and flexible resource types, Semaphore adapts to small projects and large monorepos alike, turning CI/CD into a reliable, low-friction part of everyday development. -
20
Cachex
A powerful caching library for Elixir with support for transactions
Cachex is a high-performance in-memory caching library for Elixir, offering a robust feature set including expirations, size limits, hooks, fallbacks, async operations, and clustering capabilities. The version 4.x release brought optimized janitor routines, modular streaming and querying, runtime cache warming, size pruning (LRW/LRU), distributed routing mechanisms, and a major documentation overhaul. It integrates seamlessly with Elixir applications via mix dependencies, supports advanced transactional use cases, and includes utilities for distributed node clusters. -
21
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. -
22
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). -
23
Pow
Robust, modular, and extendable user authentication system
Pow is a robust, modular, and extendable authentication and user management solution for Phoenix and Plug-based apps. Pow is built to be modular, and easy to configure. The configuration is passed to function calls as well as plug options, and they will take priority over any environment configuration. It's ideal in case you got an umbrella app with multiple separate user domains. The easiest way to use Pow with Phoenix is to use a :otp_app in function calls and set the app environment configuration. It will keep a persistent fallback configuration that you configure in one place. Pow ships with a session plug module. You can easily switch it out with a different one. Pow is extremely modular and fully customizable. As your platform scales, each moving part can be modified or replaced ad-hoc. Several extensions are included in Pow so you with no effort can add secure features to your app. -
24
bors-ng
A merge bot for GitHub Pull Requests
bors-ng is a GitHub merge bot that enforces an “evergreen” main branch by queueing approved pull requests, testing them together on a staging branch, and only advancing main with the exact, passing commit set. Instead of maintainers repeatedly rebasing and merging one PR at a time, bors-ng batches r+-ed PRs, triggers your existing CI (e.g., GitHub Actions), and merges automatically when the batch is green. If a batch fails, it bisects the batch into smaller runs to isolate the culprit, landing the good PRs and kicking only the failing one(s) back for fixes. The bot is implemented as a GitHub App and works alongside—rather than replacing—your CI by reporting commit statuses/checks and acting on PR comments like bors r+ or bors try. It provides a dashboard to watch queue progress, uses separate staging/trying branches for merge/test cycles, and supports both public GitHub and GitHub Enterprise endpoints. -
25
Überauth
An Elixir Authentication System for Plug-based Web Applications
Ueberauth is a two-phase authentication framework that provides a clear API, allowing for many strategies to be created and shared within the community. It is heavily inspired by Omniauth. You could call it a port but it is significantly different in operation, but almost the same concept. Huge hat tip to Intridea. Ueberauth provides only the initial authentication challenge, (initial OAuth flow, collecting the information from a login form, etc). It does not authenticate each request, that's up to your application. You could issue a token or put the result into a session for the needs of your application. Libraries like Guardian can help you with that aspect of authentication. Strategies implement the two phases and then may allow the request to flow through to your downstream plugs. Implementing the request and callback phases is optional depending on the strategies requirements. If a strategy does not redirect, the request will be decorated with Ueberauth information.
