r/elixir • • 21h ago

Web development with Nova, Kura, Shigoto and Arizona

Thumbnail novaframework.github.io
2 Upvotes

r/elixir • • 23h ago

Continuum v0.9.3 — durable workflows for Elixir, now with SQLite, transactional scheduling, and interval backfills

17 Upvotes

Last time I posted about Continuum here, it was at v0.8.5. Since then I’ve added a SQLite backend and a couple of scheduling features for situations that come up in real apps: saving a record that needs work later, and catching up after downtime.

Quick recap: Continuum is an OTP-native durable execution engine for Elixir. You write a workflow as ordinary Elixir and put external side effects in activities. Continuum records their results, so if the process dies or the node restarts, it can replay the workflow and pick up where it left off.

SQLite support landed in v0.9.0. You can now run durable workflows, activities, timers, signals, and recurring schedules in a single-node app without running a Postgres server. Observer and the replay tools work with SQLite too. Postgres is still the backend for clustered deployments.

Transactional scheduling builds on Continuum.Multi.enqueue/5 from the last release. Say you’re creating an invoice and want to send a reminder three days later. With Continuum.Multi.schedule_at/6, the invoice and its reminder go in the same Ecto.Multi. If the invoice rolls back, the reminder rolls back too. If the transaction commits and your app crashes on the next line, the schedule is already there for the runner to pick up.

Interval backfills solve a different problem. Suppose your nightly reconciliation uses missed: :skip. After a few days of downtime, you decide you actually need Tuesday’s and Wednesday’s runs. Continuum.Schedules.backfill/4 lets you preview that range, see which slots already exist, and pass execute: true to queue the missing ones. It respects the overlap policy, retrying the request won’t create duplicate runs, and tonight’s schedule stays where it was.

A couple of smaller changes: you can filter runs by parent or continuation chain, and pass an expected namespace when inspecting, cancelling, or pausing schedules. Both scheduling features work on Postgres and SQLite. If you’re already on v0.9.x, there’s no database migration.

Feedback is welcome, especially from anyone trying it on an existing workflow.


r/elixir • • 1d ago

BEAM FOSDEM Devroom CFP until 3 DEC

2 Upvotes

The BEAM FOSDEM Devroom needs you! CFP is open until 3 DEC. See https://beam-fosdem.dev/call-for-talks/ for all the details.


r/elixir • • 1d ago

How do you blink an LED faster than the BEAM can time it?

16 Upvotes

Blinking an LED in Nerves takes one call, Circuits.GPIO.write. Soft real time is fine at 1 Hz, but it stops being enough once you're dimming, sending Morse code or driving NeoPixels. Frank Hunleth went through the options that don't need a separate chip:

  • Circuits.GPIO timestamps inputs when the interrupt reaches the kernel
  • The 900-LED Yggdrasil tree at Goatmire encoded NeoPixel pulse widths into an SPI stream
  • Hardware PWM through Linux drivers
  • Delux compiles LED patterns that a kernel driver then plays back

Once you reach those limits, a companion microcontroller takes over, and you supervise it with a GenServer like any other process.

https://youtu.be/Wfl9Vp-jdN8


r/elixir • • 2d ago

Announcing Tune: evals, evolutionary search, and prompt optimization for Elixir

22 Upvotes

I'm excited to share my newest package in the ReqLLM family: Tune

Tune measures and improves Elixir code, including LLM prompts. You give it a function or an LLM program, some labeled examples, and a score. It runs your code, searches for a better setting or prompt, and then checks the winner against your current version on examples the search didn’t see.

The same small API covers three jobs:

  • Evals: score live code, saved answers, tool calls, or transcripts, and gate a release on a paired comparison.
  • Evolution: grid or genetic search over any Elixir value.
  • Prompt optimization: strategies modeled on DSPy and GEPA, in native Elixir with no Python.

Model calls go through ReqLLM. Learned values export as plain JSON you can load at runtime.

Tune.new(%{review_at: 50}, run: &MyApp.Router.route/2)
|> Tune.data(validation: validation, test: test)
|> Tune.score(:accuracy, fn row, out -> if out == row.expected, do: 1, else: 0 end)
|> Tune.vary(review_at: [50, 60, 70])
|> Tune.search(:grid)
|> Tune.tune()

I will be deprecating `jido_eval` and `jido_evolve`, with guidance that they will be replaced with Tune. While Tune will be part of my Jido Ecosystem, it doesn't require Jido at all and sits closer to ReqLLM and LLM DB.

Appreciate any feedback!


r/elixir • • 3d ago

VulnCheck — Function-level reachability vulnerability scanner for Elixir, Erlang & Gleam (govulncheck for the BEAM, zero runtime deps)

6 Upvotes

Hi everyone,

I’ve released VulnCheck (v1.0.1), an open-source vulnerability scanner for Elixir (mix.lock / Umbrella), Erlang (rebar.lock), and Gleam (manifest.toml) that pairs OSV.dev + EEF CNA CVE 5.1 programRoutines with post-macro .beam call graphs and OTP supervision semantics.

  • GitHub: https://github.com/Voskan/vulncheck
  • Hex.pm: https://hex.pm/packages/vulncheck
  • HexDocs: https://vulncheck.hexdocs.pm/readme.html

Motivation

With the EEF CNA publishing structured CVE 5.1 advisories for Hex packages, most advisories now include exact programRoutines MFAs (e.g. 'Elixir.Plug.Conn.Query':decode/4 or 'Elixir.Ash.Actions.Aggregate':run/4). Package-level scanners flag the entire dependency regardless of whether your release ever loads that module or calls that function.

However, building govulncheck for the BEAM requires modeling OTP execution semantics so we never produce silent false negatives:

  1. Post-macro .beam :abstract_code walking — inspects code after use Phoenix.Router, plug Plug.Parsers, parsers: [:json], Ash, and Oban.Worker expand, keeping exact file:line call sites.
  2. OTP supervision & framework entrypoints — models .app boot trees, active network daemons (Bandit, :cowboy, :ranch, ThousandIsland, Phoenix.PubSub), protocol client receive paths (Mint, :gun, Finch), consolidated protocols, and configured adapters (Tesla, Swoosh, Ecto).
  3. Sound three-tier verdicts:
    • REACHABLE — shortest concrete file:line call trace from an entrypoint or active daemon handler (call_chain_proven / daemon_call_chain).
    • POTENTIALLY_REACHABLE — active daemon stack without static path, unresolved apply/3, stripped .beam without debug info, or advisory without symbol granularity.
    • UNREACHABLE — proven function_not_called, module_not_loaded, adapter_not_configured, otp_app_not_started, non_prod_dependency (including runtime: false), or otp_version_unaffected.

Engineering properties

  • 0 runtime dependencies (pure Elixir 1.18+ & OTP stdlib, including a full CVSS v4.0 + v3.x calculator).
  • 0 dynamic atoms created from advisories, lockfiles, or config files (binary_to_term with :safe on a SHA-256 beam-v4 summary cache; ~120 ms warm scan on an 80-package project).
  • CI & compliance outputs: Terminal, JSON, Markdown, SARIF 2.1.0 (codeFlows), GitHub Actions (Voskan/vulncheck@v1.0.1), GitLab Code Quality, CycloneDX 1.6 SBOM, OpenVEX v0.2.0, time-bounded .vulncheck.ignore with --forbid-new-suppressions, and offline air-gapped --bundle archives.

Quick try

{:vulncheck, "~> 1.0", only: [:dev, :test], runtime: false}
MIX_ENV=prod mix compile
mix vulncheck

We also published our ground-truth validation harness and current false-positive boundaries in docs/VALIDATION.md. Would love feedback from teams running large Phoenix / Ash / Umbrella monorepos!


r/elixir • • 3d ago

Potential tutorials on how to implement Video Chat with Phoenix Backend and React Frontend

12 Upvotes

Hello, I was wondering if there are any good tutorials online that talk about how to implement webRTC voice chat with Phoenix as the backend signalling server, and React as the frontend UI.

This is oddly specific, but I would like a tutorial with at least one of the components listed above if that's possible

Any help would be appreciated !


r/elixir • • 4d ago

Fuzz testing for Elixir is here

Post image
72 Upvotes

ExFuzz is a coverage-guided fuzzer for Elixir, and I just launched v0.1.0!

It is well-integrated with ExUnit, so your fuzz tests can run alongside your regular tests and use the seed corpus as an ever-growing regression suite. It is built on top of LibAFL as the underlying mutation engine.

Given the amount of critical software infrastructure built on Elixir, I really wanted to focus on an out-of-the-box Go-like developer experience to reduce adoption friction (would really appreciate feedback here).

I have many plans for v0.2.0:

  • Typed generators.
  • More Elixir-aware coverage analysis.
  • Concurrent and continuous fuzzing.
  • Improved performance (execs per second).

Looking for early feedback from the community. I am planning to take it for a test drive around the ecosystem and will let you all know how that goes!


r/elixir • • 5d ago

Cloud SDKs

2 Upvotes

I’m planning on building a tool for mapping cloud environments. I’ll be working with a lot of graphs and trees as well as spinning off many async tasks. I previously built a (failed) startup in elixir and I really like the language but everything points me to using something like Go because it has the most cloud provider sdks. Can anyone let me know how the libraries for interacting with AWS, Azure, GCP and k8s are for elixir?


r/elixir • • 5d ago

I published a Twilio SDK for Elixir, generated from Twilio's OpenAPI spec

7 Upvotes

I've been building Infusion, a generator that turns OpenAPI specs into Elixir SDKs, and the first SDK I've published with it is for Twilio's core REST API: https://hex.pm/packages/twilio

```elixir

{:ok, message} =

Twilio.Messages.create(to: "+15558675310", from: "+15017122661", body: "Hello from Elixir")

```

Why: Twilio has no official Elixir SDK. ex_twilio has served the community for years, but its last release was in April 2024, and since it's written by hand, new endpoints arrive only when someone adds them. This one is generated, so it covers all 197 operations of the 2010-04-01 API, and a GitHub Action regenerates it from Twilio's spec every day and opens a PR when the API changes.

What's in it:

- Docs and typespecs on every function, structs for every response

- The account SID from config, and `account_sid:` on any call for subaccounts

- `list_all` functions that stream every page lazily

- Typed errors with Twilio's error code; retries on connection errors, 429 and 5xx

- `Twilio.Webhook.valid?/4` for `X-Twilio-Signature`, checked against twilio-python on 2,000 random requests and on real webhooks

- `Twilio.AccessToken` for the Voice, Video and Conversations client SDKs

- Built on Req, so `Req.Test` works for stubbing

Not covered yet: Verify, Conversations, Messaging Services and Twilio's other product APIs, which are separate specs. If you use Twilio from Elixir, which one would you want next?

Bug reports and naming complaints welcome: https://github.com/mandar1045/twilio


r/elixir • • 5d ago

Built a low-level systems programming language from scratch to crush concurrency bottlenecks—benchmarks inside.

Post image
7 Upvotes

r/elixir • • 6d ago

State of Elixir 2026 is open

18 Upvotes

For the fourth year in a row, we’re running the State of Elixir survey.

https://elixir-hub.com/surveys/2026/take

We want it to be a reference point for decision-makers, developers, and hobbyists on where Elixir and its ecosystem should go next.

The survey takes about 10 minutes and is open until November 30. As every year, we’ll publish the results on Elixir Hub.

Know other Elixir developers? Forward them this link. Every answer makes the results more useful for the whole community.


r/elixir • • 6d ago

Macro Mayhem 009 - Safer Releases, Better Tools, and Getting Hired

32 Upvotes

Hi r/elixir 👋

Peter Ullrich and Gus Workman here. We haven't introduced ourselves here on Reddit before, so we wanted to take a minute to share our latest episode of the Macro Mayhem podcast.

A bit of background about us - after the legendary Thinking Elixir show ended, we decided to fill that hole in our hearts with our own take on a Elixir and BEAM ecosystem news show. We record roughly every other week, highlighting important releases, ecosystem news, blog posts, interesting projects, and more. (side note - if you write a blog post, and would like to see it featured in our blog posts section, ping us! We can't guarantee it will be featured but we can guarantee we will read it 🙂)

We also have a small discussion section where the two of us just discuss a topic of our choosing - a wide ranging set of topics such as security in the dev environment, Goatmire conference recap, eMudhra impact for BEAM ecosystem, deployment tooling, and so much more.

This week Peter did a solo episode, covering the news (big hex.pm security updates, big package releases/announcements, and more!) a bunch of blog posts, followed up by discussion on the hiring market and tips for getting hired as an Elixir dev in 2026.

We hope you enjoy and give it a listen wherever you get your podcasts! You can find a browser player and links to all the popular podcast apps on our website: https://macromayhem.fm

- Peter and Gus


r/elixir • • 7d ago

Infusion - generates elixir SDKs from openapi specs, would love feedback

19 Upvotes

hey all, been working on this for a bit and finally put it on hex so figured i'd share.

it's called infusion. you give it an openapi spec and it writes a full elixir SDK for that API. structs for the schemas, a function per endpoint, retries, pagination, streaming, all that.

reason i started is pretty simple. most API companies generate their SDKs with stainless or fern or speakeasy now and none of them do elixir, so whenever a new API comes out we get nothing and end up writing http calls by hand. i tried the two elixir generators that already exist on openai's spec first and one crashed and the other turned union types into empty structs, so yeah.

using it looks like this:

{:infusion, "~> 0.2", only: :dev, runtime: false}

mix infusion.gen https://raw.githubusercontent.com/github/rest-api-description/main/descriptions/api.github.com/api.github.com.json --name GitHub

that gives you the whole github api (around 1300 endpoints) in like 16 seconds, and then you can just do

{:ok, repo} = GitHub.Repos.get("elixir-lang", "elixir")

and get a proper struct back. this is it hitting the real github api:

list endpoints also get an `_all` version that pages lazily, so you can just Enum over every repo in an org without thinking about pages:

streaming was honestly the most fun part. here it's reading wikimedia's live feed of wikipedia edits through a generated SDK:

so far i've tested it on openai, stripe, github, twilio and cloudflare's specs and they all compile with zero warnings (cloudflare's is huge, almost 3800 endpoints). github and wikimedia are tested against the real APIs, the rest only against stubs for now since i don't have keys for everything.

0.2 came out yesterday and the main thing is the names now match the official SDKs, so it's `OpenAI.Chat.Completions.create` like in their python one, not some weird generated name.

still rough in places. some nested objects come back as plain maps instead of structs, and there's no config file yet for renaming stuff. next thing i want to do is publish an actual SDK on hex, probably twilio since the current elixir client hasn't been updated in a while.

if you try it on a spec and it breaks please open an issue with the spec, that helps a ton. also curious which API you'd want an elixir SDK for first.

github: https://github.com/mandar1045/infusion

hex: https://hex.pm/packages/infusion


r/elixir • • 7d ago

Ash Typescript — Torkild Kjevik | AshConf 2026

Thumbnail
youtu.be
10 Upvotes

r/elixir • • 8d ago

Is a CSRF token needed in this circumstance

1 Upvotes

I have frontend React, backend Elixir + Phoenix. For authorization I use JWT tokens, is it worth it to add csrf still? If yes, what is the right way since most tutorials online only really show how to do it with liveview


r/elixir • • 8d ago

whiff 0.4.0 — file sniffing for Elixir, now on Rust whiff 0.8.0

4 Upvotes

whiff 0.4.0 is on Hex. It wraps the Rust whiff crate and returns a string-keyed whiff/1 report (format, hashes, security/privacy signals, content, format metadata) for a path or binary. You can also register Elixir extractors/analyzers that run in BEAM processes and merge into the native report. What's new vs 0.3.0: • Upstream Rust whiff 0.6.0 → 0.8.0 (common feature; schema id still whiff/1) • Stricter options and validated plugin modules • Native concurrency limiter that fails with :overloaded instead of running open • Safer merge/privacy/plugin error handling • stage: :local still available for slow/NFS paths; reports now describe the original file • Plugins no longer take down the caller if they crash Install: {:whiff, "~> 0.4.0"} Hex: https://hex.pm/packages/whiff Docs: https://hexdocs.pm/whiff GitHub: https://github.com/SinAnima/whiff-elixir Feedback welcome — especially on format coverage gaps you fill with custom Whiffers.


r/elixir • • 9d ago

What does an Ash developer get from Jido on day one?

0 Upvotes

Ash Jido exposes Ash resource actions as tools that an agent can call, and the authorization policies stay in place. In Mike Hostetler's model, LLM-driven behaviour runs in a "less trusted space", while Ash holds the business rules that every agent action still has to pass. Ash AI has also moved to ReqLLM, so both projects now share the same LLM client.
Mike also has an observation about coding agents: they write Spark DSL code noticeably better than imperative Elixir. Other topics include hibernating idle agents to a database, ReqLLM's 11 providers and 665 models, and how to get started with jido.run and its Livebooks.

https://youtu.be/OTZezdLLuqU


r/elixir • • 9d ago

Build a Fully Featured Ash Admin Dashboard in Minutes with Phoenix LiveView (Mishka Gervaz 0.0.7)

Thumbnail
mishka.tools
14 Upvotes

Mishka Gervaz is an Ash-powered toolkit for building fully featured admin dashboards with Phoenix LiveView. Turn your Ash resources into complete tables and forms with filtering, bulk actions, and more in just a few minutes. It's also the foundation behind the entire Mishka CMS dashboard. Fully customizable, from UI to functionality, with no unnecessary limitations.


r/elixir • • 10d ago

ElixirConf EU 2027 (Lisbon, 22-23 April): Call for Talks and Call for Training are open

Post image
2 Upvotes

r/elixir • • 10d ago

ElixirConf EU 2027 (Lisbon, 22-23 April): Call for Talks and Call for Training are open

Post image
3 Upvotes

Hi all!

ElixirConf EU is coming to Lisbon (and online) on 22-23 April 2027, with a training day on 21 April. Both calls are open until 15 December.

Call for Talks: two tracks, 20- and 40-minute slots with optional Q&A. Whether you are a core team member or new to Elixir, if you have something to share, we would love to hear from you. Proposals go through Sessionize: https://sessionize.com/elixirconf-eu-2027/

Call for Training: we are looking for people to teach a full-day Elixir or BEAM training on 21 April in Lisbon: https://forms.gle/YY3cJJpt9fYaMPQ46

More about the event: https://www.elixirconf.eu/

Happy to answer questions in the comments. And if you know someone who has a great talk in them but would never submit, please tell them about the call.


r/elixir • • 10d ago

Mishka CMS now imports your WordPress site

Thumbnail
mishka.tools
10 Upvotes

We built Mishka CMS Migration, an open-source extension that moves a WordPress site into Mishka CMS on Phoenix LiveView: posts, pages with their Elementor layouts, menus, media, comments and Polylang or WPML translations.

A dry run reads the whole site first and writes nothing, and every old WordPress address is planned as a 301 redirect, so existing links keep working. When two answers make sense, like a page that already exists at that address, the item waits for your decision.


r/elixir • • 11d ago

F3 file format for Beam languages

13 Upvotes

I've started following the F3 project. F3? It's a columnar research file format: the file stores columns, and a footer at the end holds an Arrow schema plus where those columns live. A file can also embed a Wasm decoder next to the data. The spec is still a prototype. This library speaks wire version 0.1 only.

I published f3 0.1.0 so you can open one of those files from Elixir, print the schema and footer, and read or write rows when the native decoder is loaded. Wasm stays off unless a read passes wasm: :sandbox, which runs that embedded module in a Wasmtime sandbox. A Hex install downloads precompiled builds for Apple silicon and Linux x86_64.

The longer version is in my write-up. The API is on Hexdocs, and the code is on GitHub.


r/elixir • • 12d ago

Stampede 1.4: 40,000 users on a Phoenix chat app with a real Postgres (100M messages), plus a LiveDashboard tab and a Livebook smart cell

19 Upvotes

After my 2 million users post, a lot of you asked the fair question: what happens with a real database? So I tested that.

The app is a plain mix phx.new chat app with Ecto's default pool of 10. Postgres 17 with default settings runs on its own machine, seeded with 1 million users, 10,000 rooms and 100 million messages. Each user joins a room, which reads the latest 50 messages, then every 30 to 60 seconds sends a message that's written to Postgres before the reply comes back.

Results:

20,000 users: join p95 4.58ms, send p95 3.20ms, 0 errors

40,000 users: join p95 6.31ms, send p95 178ms, 0 errors

Past 40,000 it hit three limits at once: the app's schedulers at 96%, queries waiting for the pool of 10, and Postgres waiting to write its log to disk.

That led to the main feature in 1.4: --probe now watches your database (pool wait, Postgres commits, writes and wait events), and the find-limit verdict tells you which part gave out.

Also new:

- a Stampede tab for your app's own Phoenix LiveDashboard, showing probed runs live

- a Load test smart cell for Livebook

- a new look for the dashboard and HTML report, and mix stampede.report to re-render any saved run

Everything to rerun it (app, seed, scripts, logs) is in the repo: https://github.com/mandar1045/stampede