Open Source Elixir System Software

Fast Elixir is a curated collection of performance-focused best practices, idioms, and code snippets for writing efficient Elixir programs. The project documents common patterns in Elixir and compares their relative performance using benchmarks to guide developers toward faster and more memory-friendly code. By showcasing side-by-side examples, it highlights not only which approaches are faster but also why certain functions or techniques should be preferred in different scenarios. The repository is designed as a practical reference for developers who want to optimize Elixir applications without diving into premature micro-optimizations. Its goal is not just speed but also clarity, ensuring that performance improvements do not come at the cost of readability and maintainability. With continuously updated examples, Fast Elixir helps both beginners and experienced Elixir programmers adopt better habits and avoid slow patterns.

The operating system and all related software that runs on FarmBot's Raspberry Pi. The FarmBot OS release page has moved to my.farm.bot/os. Old versions of FarmBot OS can still be found. Get configured over WiFi, mitigating the need to plug in a mouse, keyboard, or screen. Communicate with the web application over WiFi or ethernet so that it can synchronize (download) sequences, regimens, farm designs, events, and more; upload logs and sensor data; and accept real-time commands. Communicate with the Farmduino to send G and F commands and receive sensor and encoder data. Take photos with a USB or Raspberry Pi camera, and upload the photos to the web application. You must use a .img writing tool to write FarmBot OS onto the microSD card. We recommend downloading and installing balenaEtcher for this purpose.

Comeonin is the long-standing password-security library for Elixir that standardizes secure hashing and verification practices in Phoenix and Plug applications. It provides a uniform interface for modern algorithms such as Argon2, Bcrypt, and PBKDF2 (implemented in companion packages), along with guidance for salts, cost factors, and timing-safe comparisons. The library’s helpers make it straightforward to add registration and login flows that resist brute-force and side-channel attacks. Migration paths and checks are included so you can upgrade algorithms or work factors over time without breaking existing credentials. Its focus on practical ergonomics—clear APIs, sensible defaults, and good docs—has made it the de facto choice for password handling in Elixir. By centralizing hashing concerns, Comeonin helps teams avoid subtle security mistakes while keeping authentication code terse and testable.

Coherence is a full-featured, configurable authentication and user management system for Phoenix applications. Comparable to Devise in the Ruby/Rails ecosystem, it offers modular authentication modules like registration, confirmation, password recovery, session tracking, locking, remember-me, and invitations. It also supports token and HTTP Basic authentication and fits into Phoenix via plugs and routes.

Guardian is a token based authentication library for use with Elixir applications. Guardian remains a functional system. It integrates with Plug but can be used outside of it. If you're implementing a TCP/UDP protocol directly or want to utilize your authentication via channels in Phoenix, Guardian can work for you. The core currency of authentication in Guardian is the token. By default JSON Web Tokens are supported out of the box but you can use any token that Has the concept of a key-value payload, is tamper-proof, can serialize to a String, or that has a supporting module that implements the Guardian.Token behavior. You can use Guardian tokens to authenticate web endpoints (Plug/Phoenix/X), channels/Sockets (Phoenix - optional), and any other system you can imagine. If you can attach an authentication token you can authenticate it.

Anoma is a next-generation blockchain protocol focused on intent-centric architecture, enabling privacy-preserving, composable transactions across multiple applications and chains. Unlike traditional account-based or UTXO models, Anoma introduces intents as the fundamental units of interaction, allowing participants to express what they want without specifying how it must be achieved. The protocol is designed with privacy, interoperability, and decentralization at its core, and is built using Rust and zero-knowledge cryptography tools. It aims to serve decentralized finance, identity, and coordination systems in a novel and user-centric way.

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.

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.

libcluster provides automatic cluster formation and node discovery for Erlang/Elixir applications, removing the manual steps typically required to connect distributed nodes. It ships with multiple pluggable strategies—such as DNS polling, Kubernetes integration, EC2 metadata/tag discovery, UDP gossip, and EPMD helpers—so you can adapt clustering to your runtime environment. The library supervises a topology process that continually discovers peers and joins or prunes nodes as they become available or disappear. Its design embraces OTP principles: strategies implement a behavior, can be composed, and run under supervision for resilience. libcluster also emits events on nodeup/nodedown, allowing applications to react (for example, rebalance work or update registries) when membership changes. Because it relies on the BEAM’s native distribution, it integrates cleanly with Phoenix PubSub, Horde, Oban, or any other distributed Elixir tooling.

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.