Pricing

Internal tools you can stop worrying about

With Avo, your Rails app is your company's command center, whether that means a support desk, patient records, an inventory app, or all three. Support, ops, and finance ask it questions and get answers, not tickets, from the app, the AI chat, MCP, or the CLI.

You stay in control: permissions decide who sees what, nothing changes until someone clicks Confirm, and every change leaves an audit trail.

Free to start. Unlimited users. No per-seat fees.

01

the app behind the app

You don't build one app, you build two.

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 the second app from scratch and you carry two apps. Build it on Avo and most of it is already there.

02

"just have the agent build it"

Your agent can build the admin. Don't make it start from zero.

Start from a blank app and the agent spends the session, and your tokens, building the same foundation every admin needs: tables, forms, pagination, search, auth wiring, permissions. On the next app it builds that foundation again, a little differently, and each version is new code to review and trust from zero. The speed is real. The foundation shouldn't be new every time.

03

where Avo comes in

Most of the second app is already built.

It's already built, reviewed by the Avo team, and running in hundreds of apps. Select-all that means the whole query, not just the visible page. Confirmation on the actions that deserve it. One authorization layer, down to the field, that holds in the UI, over MCP, and through the API. The stack decisions are made and still yours to override, and the gem ships skills your agent reads, so what it writes is a short Ruby resource you can review.

The same foundation in every app, and one app to maintain instead of two.

Read the full story

What you don't have to build

Every admin needs the same foundation. With Avo it comes built, reviewed, and maintained, including the authorization layer the assistant answers to.

The same foundation in every app

Your agents don't generate a new admin for each project. Every app starts from Avo, so what you reviewed and trusted in the last one carries into the next.

Tokens, time, and focus go to your product

An Avo resource is a short Ruby file, not a stack of generated controllers, views, and tables. Your agent spends fewer tokens, finishes sooner, and you spend your attention steering it on your business logic instead of on the admin underneath.

Your data stays correct

Validations, associations, and the edge cases that only show up across many apps are already handled, for every Rails association type, not just the happy path.

One authorization layer, every surface

Write a permission rule once and it holds in the CRUD UI, over the MCP server, and through the API. Scope the records a role can see and the attributes it can't, and no surface, human or agent, gets around it.

Know who changed what

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.

Vetted by hundreds of customers, better every release

We use AI to move faster too, and every release is designed and reviewed by the Avo core team, then exercised across hundreds of real apps before it reaches yours. Upgrades arrive with bundle update, and the resources your agents wrote keep working.

In their own words

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.

David Teren
David Teren
Rails developer

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.

Stanislav (Stas) Katkov
Stanislav (Stas) Katkov
Author of Posh TUI

Avo has allowed the RubyGems.org team to build internal tools incredibly quickly, which is especially important due to our limited resources

André Arko
André Arko
Gem.coop co-founder

I can't believe I just learned about Avo! After trying it for 10 minutes, it was the easiest purchase ever. I used RailsAdmin before and had so many upgrading issues. Besides that, Avo is so much simpler to configure and build.

Michael Koper
Michael Koper
Founder of nusii.com

We are migrating from ActiveAdmin to Avo and both in terms of Developer experience and User experience, it is a game changer!

Adrien Poly
Adrien Poly
CTO, Plume

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!

Bram Janssen
Bram Janssen
Rails World Conference App Developer

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

Tom Coates
Tom Coates
Head of Engineering, BBC Maestro

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.

Iain Beeston
Iain Beeston
CTO, Thrivve Partners

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.

Paul Werther
Paul Werther
CTO, greenhats GmbH

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.

John Bannister
John Bannister
Rails developer, Exlibris RPG

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

Mike Eyrikh
Mike Eyrikh
Tech Lead, Guestit

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.

Amanda B. Perino
Amanda B. Perino
Rails Foundation Executive Director

I just wanted to say I love working with Avo in RubyGems.org

Maciej Mensfeld
Maciej Mensfeld
RubyGems.org Security

Adding Avo to my project was like adding multiple developers to my team - and that's before I even purchased a license!

Caleb Harrison
Caleb Harrison
Ruby and Crystal Developer

Product news and updates

Sign up for our newsletter.

We care about your data. Read our privacy policy.

Latest release

Avo v4.3.0 released 4 days ago.

Active Storage image optimization at scale-ish: lessons from 1,916 conference photos

Active Storage tutorials stop at `resize_to_limit`. Here is what happens at 1,916 photos: variants generated inside the Puma request, `preprocessed:` enqueuing 17,250 jobs, an N+1 that only appears once you move to a CDN, and a CDN that never considered your images cacheable in the first place. All measured on a gallery that is live and open source.

Adrian Marin

Adrian Marin

Author & CEO

Avo 4 Open Beta

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

Adrian Marin

Build internal tools
on RailsIcons/pause solid

Whatever your team needs next, it's screens over models you already have. Pick one and have it running this afternoon.

It's your models, your repo, your servers. Free to start.