// the find
mirego/elixir-boilerplate
⚗ The stable base upon which we build our Elixir projects at Mirego.
A production-grade Phoenix/Absinthe boilerplate from Mirego, a Montreal agency that has been shipping Elixir in production for years. It comes pre-wired with GraphQL, Ecto, Gettext, Credo, Dialyzer, Sentry, security scanning, healthchecks, and a TelemetryUI dashboard — the stuff you'd spend a week assembling yourself. Aimed at teams who want to start a serious Elixir API project without yak-shaving the toolchain.
The setup script (boilerplate-setup.sh) does a global rename across the codebase so you're not grep-replacing strings manually. AbsintheSecurity is included by default, which most GraphQL boilerplates skip entirely — it blocks query depth and complexity attacks out of the box. Security posture is better than average: MixAudit for dependency CVEs, Sobelow for static analysis, and a dedicated security plug are all wired in before you write a line of business logic. The GitHub Actions Accent workflow for automated translation sync is a nice touch that shows this is used in real multilingual production apps, not just demo projects.
It's opinionated toward GraphQL-only APIs — there's no REST scaffold, so if you want a traditional Phoenix JSON API you're ripping out Absinthe immediately. LiveView is present but minimal (a single demo live.ex), so the boilerplate doesn't give you much structure for LiveView-heavy apps. The Accent integration is a hard dependency in the workflow even if you don't need i18n — you'll have a failing CI job until you remove it. No Oban setup despite recommending it as the preferred job queue; adding async jobs to a fresh project still requires manual wiring.