// the take
RailsAdmin auto-generates a CRUD admin interface for your ActiveRecord or Mongoid models by introspecting your schema, instead of you writing admin views and controllers by hand. It's for Rails teams who need an internal data-management UI (support staff, ops, content editors) without building one from scratch.
Plugs into Devise for auth and CanCanCan/Pundit for authorization rather than inventing its own, so it fits into whatever access control you already have. The adapter layer cleanly separates ActiveRecord and Mongoid specifics, which is why it's survived as one of the few Rails admin gems to support both. It's been maintained continuously for over a decade, still tracks current Rails/Ruby versions (3.4, JRuby) and runs CodeQL plus a real CI matrix via Appraisals across multiple Rails versions.
The UI is generated from your schema by default, which means every column and association on a model is visible and editable in the admin unless you explicitly lock it down in the per-model config block — it's easy to accidentally expose a sensitive field. The per-model `rails_admin do ... end` DSL doesn't scale gracefully; once you need custom actions, computed fields, or non-trivial polymorphic/nested associations, you're writing nearly as much Ruby as a bespoke admin controller would take. Mongoid support exists but gets far less real-world exercise than the ActiveRecord path, so edge cases there are more likely to be rough. It's also squarely an internal-tool pattern — there's no built-in rate limiting or audit-by-default (PaperTrail is opt-in), so exposing it beyond a trusted internal network needs deliberate hardening.
We read the README, the directory tree and a key source file in October 2026. Nobody pays to be listed. How we judge →