Custom sections where fields aren't enough
Embed fully custom UI inside a resource's views, so the one exotic screen doesn't force the whole admin off the framework.
You could build it yourself. But the cost isn't writing the first version, it's owning it forever. Avo takes that off your plate, so your team can focus on the product your customers actually pay for.
Free trial available, no credit card. Works with any Rails app.
01 · the app behind the app
The first app is the product people pay for. The second is the internal tooling behind it: the admin panels, dashboards, and CRUD screens your team lives in. It's never finished, and no company ever won its market because the admin panel was great. Build it yourself and you carry two apps forever. Let Avo own the second one and you maintain a single app instead.
02 · "just have the LLM build it"
Yes, an LLM can generate your admin panel. Then you own every line of it.
The first draft looks great in the demo. But generating the code isn't the expensive part, owning it is: the security holes you can't see, the correctness that looks right and isn't, the maintenance debt, and the guardrails an LLM never knows to add. When the model writes every line, someone still has to be the security reviewer, the QA, and the maintainer. That someone is you.
03 · where Avo comes in
Avo is the pre-LLM alternative where these decisions are already made, tested in production, and hardened across hundreds of teams. Select-all that means the whole query, not just the visible page. Confirmation on the actions that deserve it. The hundred small taste decisions that keep an admin safe to use. You're not hardening slop, you're building on a foundation.
You maintain one app instead of two.
Read the full storyYou could build all of this yourself. The question was never the first version, it's the years of owning it. Here's what you hand off instead.
Validations, associations, and the edge cases a first-pass build quietly skips are already handled, across every Rails association type, not just the happy path.
Authorization, permissions, and the hardening around full data access are built in. The riskiest thing in your stack stops being auth you wrote in a hurry.
You offload the upkeep as Rails and Avo evolve. One app to maintain instead of two, and never a maintenance cycle spent on the admin.
No company ever won its market because the admin panel was great. Every hour you don't spend on internal tools is an hour on the part people actually pay for.
Every create, update, and delete is recorded, so when a record looks wrong you can see who touched it and when. Answer the "what happened here?" questions in seconds instead of guessing.
We use AI to move faster too, but every line is read by humans and exercised across hundreds of real apps. You're building on a foundation, not hardening slop.
Our customers love Avo
It was my first time using Avo, and I was impressed by how easy it was to get started and how good the user experience was. The benefits were clear right away, without needing a lot of setup. Avo supports developers in making the most out of Rails as a one-person framework!
When I added Avo to the project I was not expecting much. Just another admin panel gem...
But the more I use it, the more crucial it became. I've been building very complicated data dashboards with it at the speed of light.
I only now understand, even in the age of LLMs, it's a sick project! Saves a lot of time.
I would never build a custom admin panel in the future.
We wasted too much money and could not focus on our main business.
Avo has allowed us to develop and release apps rapidly even with very few developers working on them. We can focus our efforts on domain logic and custom design where it really matters. Every other Rails CMS is difficult to style or scale or add custom fields, but Avo has been a dream throughout. It's been a game-changer for us.
I've spent time looking into solutions that complement a sensible modern stack that gets you to the point of focussing on the product you're building sooner and does not induce conceptual compression along the way.
Avo fits nicely into that stack.
We are migrating from ActiveAdmin to Avo and both in terms of Developer experience and User experience, it is a game changer!
Avo just worked great. We were able to plug things together really easily, and it's given us the flexibility we needed to build out a really rich product
We are heavily used Avo Pro in order to build a new "admin first" platform that can be managed by our non-tech team with ease.
The interface is extremely intuitive and can be extended fast with custom actions.
I just wanted to say I love working with Avo in RubyGems.org
I often think of it as... just having in-house designer, a front end, and a full stack. And AVO just gives you this with a very nice DSL where you just save time. So that's what's nice about it. Every time you use it, you save time
Avo has let me push further on the features my users benefit from most whilst trusting I am giving volunteer curators a backend experience I can still be proud of.
It's a real multiplier on the project and adopting it was undoubtedly the best technical decision we've made.
We have used Avo as the admin dashboard for our event app to manage speakers and sessions for years. We work with early career devs on this app and Avo has saved them hours of work so they could focus on what's most important: the user experience.
Adding Avo to my project was like adding multiple developers to my team - and that's before I even purchased a license!
Avo has allowed the RubyGems.org team to build internal tools incredibly quickly, which is especially important due to our limited resources
Sign up for our newsletter.
New themable UI, dark mode, keyboard navigation, and a wave of new addons. Unbundled pricing so you pick exactly what you need. Start a trial and have it running today.
Adrian Marin
The Avo 4 Open Beta is here. Try the new UI4 visual style, new features like Collaboration, Forms, Kanban, HTTP Resources, REST API, and Reactive Fields — plus a comprehensive upgrade guide to help you migrate from Avo 3.
Adrian Marin
Build the admin once, let Avo own the upkeep, and put your team back on the product only you can build.