carlosgrell
Recently I’ve been wondering which of these two libraries would be the most recommended for resource authorisation, regardless of the app purpose (but maybe taking into account different app sizes and structures).
I would very much like to know your thoughts about these two libraries, and what are the reasons one should choose one of them over another:
- Bodyguard: GitHub - schrockwell/bodyguard: Simple authorization conventions for Phoenix apps · GitHub - 265 stars, 18 forks, 10 contributors
- canary: GitHub - cpjk/canary: 🐣 Elixir authorization and resource-loading library for Plug applications. · GitHub - 373 stars, 45 forks, 12 contributors
At a first glance (not having used any), the best thought I can have is: the first one (Bodyguard) seems a little less invasive, simpler and easier to test, but also harder to find rules and maintain, and the latter (canary) makes authorisation more centralised (thus making its rules easier for modification and maintenance).
Thanks in advance.
Where Next?
Trending in Discussions
Other Trending Topics
Latest Phoenix Threads
Latest on Elixir Forum
Sponsor Spotlight
Error tracking, logs, APM, uptime and cron monitoring in one dev-friendly platform. Find and fix problems before your users notice.
Categories:
Sub Categories:
Forums
Popular Tags
- #ecto
- #liveview
- #troubleshooting
- #learning-elixir
- #library
- #deployment
- #erlang
- #testing
- #genserver
- #mix
- #absinthe
- #remote-other
- #otp
- #plug
- #how-to-question
- #macros
- #postgres
- #elixirconf
- #channels
- #exunit
- #discussion
- #code-sync
- #podcasts
- #javascript
- #onsite
- #dialyzer
- #docker
- #authentication
- #umbrella
- #full-time-contract
- #podcasts-by-brainlid
- #ecto-query
- #ai
- #elixirconf-us
- #blog-post
- #elixir-ls
- #phoenix_html
- #iex
- #graphql
- #genstage
- #websockets
- #supervisor
- #advent-of-code
- #distillery
- #processes
- #api
- #forms
- #elixirconf-eu
- #metaprogramming
- #hex
Our Sponsors
Build Elixir applications with speed and confidence.
Supporting innovation across the BEAM ecosystem.
Catch errors, track performance, monitor hosts and more.
Error tracking, logs, uptime, and Just Enough APM. Built for developers.
Elixir, Erlang & BEAM conferences from Code Sync - join us in 2026!
Master modern tools, write cleaner code, and tackle real-world challenges.
Producing high quality Elixir screencasts since 2017.
The deployment platform built for Elixir: PaaS ease, VPS control.
The team behind Membrane, Popcorn, LiveDebugger. Available for hire.
Courses that'll move you from confusion to "Aha, now I get it!"
Showing Posts 1 to 2- Show Best Posts
- Show All (oldest first)
- Show All (newest first)
tielur
We’ve been using GitHub - boydm/policy_wonk: Elixir authorization and resource loading in Plug form for Phoenix · GitHub and it works pretty well. I haven’t checked out bodyguard though.
OvermindDL1
I just use my own built on my permissions_ex matcher library combined with bog-standard phoenix tokens.