Open Source Elixir Software for ChromeOS
Sort By:
Elixir Software for ChromeOS
Browse free open source Elixir Software for ChromeOS and projects below. Use the toggles on the left to filter open source Elixir Software for ChromeOS by OS, license, language, programming language, and project status.
-
MongoDB Atlas runs apps anywhereMongoDB Atlas gives you the freedom to build and run modern applications anywhere—across AWS, Azure, and Google Cloud. With global availability in over 115 regions, Atlas lets you deploy close to your users, meet compliance needs, and scale with confidence across any geography.
-
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.
-
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
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. -
3
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). -
4
30 Days of Elixir
A walk through the Elixir language in 30 exercises
30-days-of-elixir is an educational repository created by Josh Adams (seven1m) designed to teach the fundamentals of the Elixir programming language through a structured, daily learning approach. The project provides a series of exercises and examples meant to guide learners from the basics of Elixir syntax to more advanced functional programming concepts. Each day introduces new material in a concise and practical format, encouraging hands-on experimentation and gradual mastery of the language. The content covers essential topics such as pattern matching, recursion, data structures, processes, and message passing—core principles that define Elixir’s design. This incremental learning format allows developers to build confidence and understanding while maintaining consistent progress. As one of the early and influential resources in the Elixir community, 30-days-of-elixir remains a valuable guide for self-learners and newcomers to the functional programming paradigm. -
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.
-
5
Algora TV
Open source Twitch for developers
Algora TV is an open source Elixir/Phoenix application developed by Algora.io that powers Live Billboards—a platform for embedding in-video ads during livestreams. The project enables developers to monetize their live content while providing devtools companies a dynamic and non-intrusive way to reach audiences in real time. Built on top of the Phoenix framework, it leverages Elixir’s concurrency and scalability to handle streaming, ad management, and user interactions seamlessly. The system integrates with GitHub for authentication and uses Tigris for media storage and delivery, with optional support for services like FFmpeg, ImageMagick, and OBS Studio for livestream testing and video processing. The repository includes all setup instructions, from environment configuration to database initialization, making it accessible for developers to self-host or experiment locally. -
6
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). -
7
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. -
8
Elixir Koans
Elixir learning exercises
Elixir Koans is an interactive learning project designed to teach the fundamentals of the Elixir programming language through a series of self-guided coding exercises. Inspired by the style of koans used in other programming communities, it provides incomplete code snippets and failing tests that learners must solve to progress. Each exercise builds on the previous one, gradually introducing core concepts such as pattern matching, recursion, processes, and concurrency in Elixir. By debugging and filling in missing pieces, users gain practical, hands-on experience while reinforcing theoretical knowledge. The project is ideal for both complete beginners and developers transitioning from other languages who want to learn Elixir in a structured, exploratory way. Its design emphasizes discovery, experimentation, and reflection, making it a powerful tool for deepening understanding of Elixir’s unique paradigms. -
9
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. -
Get the most trusted enterprise browserDefend against security incidents with Chrome Enterprise. Create customizable controls, manage extensions and set proactive alerts to keep your data and employees protected without slowing down productivity.
-
10
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. -
11
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. -
12
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. -
13
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. -
14
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. -
15
Elixir Code Smells
Catalog of Elixir-specific code smells
Elixir-Code-Smells is a research-driven catalog of code smells specific to the Elixir programming language. Unlike generic code smell lists, this project identifies issues emerging from Elixir’s functional, concurrent, and process-based nature. Initially compiled via grey literature (blogs, talks, forums), the catalog now includes 23 Elixir-specific smells plus 12 traditional smells adapted to Elixir. Each entry documents the name, category, problem, example, refactoring strategy, and step-by-step treatments. The smells are grouped into two categories: design-related (coarse-grained, harder to detect, affecting architecture/processes) and low-level concerns (fine-grained, often readability and maintainability issues). The catalog evolves with community feedback and contributions, aiming to help developers recognize harmful patterns and apply disciplined refactoring to improve maintainability, testability, and performance in Elixir systems. -
16
GenStage
Producer and consumer actors with back-pressure for Elixir
GenStage is a specification and set of behaviours for building demand-driven data pipelines on the BEAM. It formalizes the roles of producers, consumers, and producer-consumers, using back-pressure so that fast producers don’t overwhelm downstream stages. Developers implement callbacks like handle_demand and handle_events to control how items are emitted, transformed, and consumed across asynchronous boundaries. Because stages are OTP processes, you gain fault tolerance, supervised restarts, and concurrency tuned via configurable demand and partitioning. GenStage underpins higher-level libraries like Flow and Broadway, but it can also be used directly for custom pipelines where timing and throughput matter. Its clear separation of concerns encourages testable, composable stages that can be rearranged as requirements evolve. In production, this leads to predictable, resilient dataflows for event ingestion, batching, and parallel processing. -
17
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. -
18
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. -
19
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. -
20
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. -
21
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. -
22
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. -
23
Poison
An incredibly fast, pure Elixir JSON library
Poison is a fast and lightweight JSON library for Elixir focused on performance and idiomatic APIs. It provides straightforward encode and decode functions, along with a protocol-based encoder that lets you customize how your structs become JSON. Developers can derive or implement Poison.Encoder for domain types, control which fields are included, and map complex values into JSON-friendly forms. On the decoding side, it supports options for key handling and flexible parsing of JSON into Elixir maps, lists, and primitive values. Internally it uses optimized binary processing to keep allocations low and throughput high, which is why it became a popular choice in early Elixir ecosystems. The API is intentionally small and unsurprising, making it easy to drop into controllers, background jobs, or data pipelines. Many codebases still rely on Poison for its speed and simplicity, even as alternative JSON libraries exist in the community. -
24
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. -
25
Swarm
Easy clustering, registration, and distribution of worker processes
Swarm is a distributed process registry for Elixir/Erlang that lets you register and discover processes across a cluster as if they were on a single node. It focuses on automatic distribution and rebalancing, so when nodes join or leave, Swarm can move work and hand off state to keep the system stable. The library offers a global name registry, conflict resolution for name ownership, and hooks for reacting to membership changes. Its design embraces OTP principles, using supervised processes and fault-tolerant messaging to keep the registry resilient under failures. Developers can co-locate Swarm with their existing supervision trees to scale workers horizontally without writing custom clustering code. Typical use cases include globally unique workers, sharded consumers, and presence-like coordination where node churn is expected. By turning registry and handoff into configuration and callbacks, Swarm reduces the complexity of multi-node deployments.