Fault-tolerant by design
Supervisors restart what fails, so one bad request never takes the whole system down.
The Elixir in production directory
From chat at global scale to pharmacy point-of-sale in Belém, teams choose the BEAM for systems that stay up. Explore who's building with it, and how.
children = [ {Company, name: "Discord"}, {Company, name: "Pinterest"}, {Company, name: "Remote"}, {Company, name: "CyberFruit Lab"}, # ...345 more ] Supervisor.start_link(children, strategy: :one_for_one)
Why teams pick Elixir
Elixir runs on the Erlang VM, the BEAM, originally built to keep phone switches online. Modern syntax, battle-tested runtime.
Supervisors restart what fails, so one bad request never takes the whole system down.
Millions of lightweight processes spread across every core, and across machines, without locks.
Phoenix Channels and LiveView ship interactive, live-updating apps with far less JavaScript.
Immutable data, pattern matching and first-class tooling keep large codebases readable for years.
Browse by industry
In their words
“We are 100% Elixir and we use it to build large-scale distributed systems.”
“The patient and doctor services run on Elixir and Phoenix LiveView, alongside React and native mobile apps.”
“A cloud-native geographic information system (GIS) platform for building maps, apps, and dashboards. Powered by Elixir and Phoenix.”
Listed companies by country
Every listing is a single Markdown file. Open a pull request and help show the world Elixir is ready for production.
src/content/companies/you.mdHelp me add my company to Elixir Companies (https://elixir-companies.com), a directory of companies using Elixir in production. The site is an Astro project at https://github.com/beam-community/elixir-companies, and each company is a single Markdown file. Your goal is to open one pull request that adds one file. 1. Ask me for anything below that you don't know: company name, website, how the company uses Elixir, city/state/country, and optionally GitHub org, blog, and careers page URLs. Only use facts I give you or that you can verify on the company's own website. Never invent details. 2. Fork and clone the repository, then create a branch named add-<company-slug>. 3. Check for duplicates: search src/content/companies/ for the company name and website domain. If the company is already listed, stop and tell me instead of adding a new file. 4. Create src/content/companies/<company_slug>.md, where the slug is the lowercase company name with spaces replaced by underscores (for example, "Acme Labs" becomes acme_labs.md). Use exactly this format: --- name: "Acme Labs" website: "https://acme.example" github: "https://github.com/acme" blog: "https://acme.example/blog" jobs: "https://acme.example/careers" industry: - "Information Technology" location: city: "Lisbon" state: "" country: "Portugal" lastChangedOn: 2026-01-31 --- One or two short paragraphs, in the third person, describing what the company does and specifically how it uses Elixir. Rules: - industry is a list of 1 to 3 values, copied exactly from: Agriculture & Food, Communication Services, Consumer Discretionary, Consumer Staples, Education, Energy, Financials, Government & Non-Profit, Health Care, Industrials, Information Technology, Materials, Media & Entertainment, Professional Services, Real Estate, Transportation, Utilities. - github, blog, and jobs are optional (jobs shows a "Hiring" badge). Remove any that don't apply instead of leaving them empty. - All URLs are full https:// links that resolve. - Use the country's full English name. Leave state as "" if it doesn't apply. - lastChangedOn is today's date in YYYY-MM-DD format. - The description must mention Elixir usage. Keep it factual: no marketing superlatives, emoji, or tracking parameters in links. - Do not change any other files. 5. Validate: run npm ci and then npm run build (requires Node.js 22.23.4 or newer). The build checks the frontmatter against the schema, so fix any errors it reports. 6. Commit only the new file with the message "Add <Company Name>", push the branch to my fork, and open a pull request against main titled "Add <Company Name>". Fill in the pull request template checklist. 7. Reply with the pull request URL.