Frequently asked questions

Yes. Sign-ups are open publicly. Anyone can start a trial to start using Avo 4 today.

Yes. Each license can start one 14-day trial of the add-ons and bundles you pick on the pricing page. No card is needed to start. Add a payment method before the trial ends to keep the add-ons; without one, they stop when the trial does. The Community edition is free and needs no payment details at all.

Absolutely. It's a common situation and we believe that website owners should also own their Avo license. If you're planning to get an yearly subscription, then we recommend your customer to purchase it.

Avo is packaged as a Ruby gem which you can install into your own Rails app. This makes for a better update experience where you don't have merge conflicts between your app and the underlying updates.

The Community version is free to use in as many apps as you want. Each paid Avo 4 license covers one production app, with unlimited users. You don't need extra licenses for staging, preview, or testing URLs of the same app, only separate, customer-facing apps need their own. Read the full details or book a call for more advanced licensing needs.

No. Avo 4's paid add-ons are a monthly or yearly subscription per app, and they stop working when the subscription ends. The perpetual fallback was an Avo 3 policy, where you could keep the version you were on after you stopped renewing. Read the full details.

Our only "per-seat" pricing is per app or URL, so we check at runtime which URL Avo runs on to keep the license valid. The check runs on the first request and then once a day with a 5 second timeout, and if it fails the app keeps running for three more days and retries hourly, after which the admin pauses until a check succeeds. Read the full details.

Yes. You can change the URLs of your license at any time. The URLs must belong to the same app. The removed URLs should not use Avo anymore.

Yes. It's designed to be easily added in new apps and existing ones.

Every paid license comes with Community support. You have free access to our Slack/Discord server where the community can share feedback and offer support.

We offer a few flavours of paid support as well.

We'd rather you be sure before you pay than ask for a refund after. That's why we let you start a free trial first, so you can run Avo 4 in your own app and make sure it's a fit. If you still have questions, book a call with us before purchasing and we'll be happy to help.

We moved away from two rigid tiers. Every feature is an add-on you can pick on its own, since no two apps need the same set, and some features matter more to you than others. We also grouped related add-ons into bundles at a discount versus buying them separately. Most teams start with the essentials bundle and add from there. If you want the full package, the "Everything" bundle includes every feature.

Because each feature takes ongoing work to build, maintain, secure, and improve. We do the work upfront and you pay in installments, like every other SaaS product.

Same reasoning. It's not a one-time deliverable. It's continuously maintained, kept secure, and improved over time.

It's more than code. It's the thinking, architecting, iterating through bad decisions, collecting feedback, maintenance, and security audits behind it. And because it lives where your app lives, you get to take control. Override partials, CSS, JS, and Ruby business logic in ways you simply can't with a cloud product.

Yes we do. Please book a call and I will get back to you really soon.

Avo is the foundation your agents build on. Point Claude Code, Cursor, or Codex at your app and they write short Ruby resources on top of Avo, which is already secure and maintained, instead of generating a new admin from scratch in every app.

1. Every app starts from the same foundation. The stack decisions (Hotwire, ViewComponent, Tailwind, Pundit, your auth) are already made and still yours to override, so your agents don't make them again, a little differently, each time.
2. Your agent's tokens, and your time and focus, go to your business logic, not to rebuilding and steering tables, forms, search, and permissions. What it ships is a small diff you can review.
3. It's a foundation of trust. Write a permission rule once and Avo enforces it on every surface: the CRUD UI, the MCP server, and the API. Scope the records a role can see and the attributes it can't, and an agent acting on your data is bound by the same rule your team is.
4. Your agent knows the Avo you run. rails g avo:skills installs the agent skills that ship inside the gem, pinned to your installed version. Read the agentic engineering guide.
5. You get the three T's: ship in an afternoon instead of a sprint (time), build on human-reviewed code running in hundreds of apps (trust), and a UI that behaves like a considered product in every app (taste).

Yes. About 50 teams have been testing it across many different configurations, and only a handful of issues surfaced. Avo is now stable and ready for production use.

Go on your project page, click "Try Avo 4" and follow the instructions.

Enrollment is now closed. Accounts that were enrolled can keep using Avo 4 on that enrollment until August 1st, 2026, but will then need to purchase a subscription to continue.

Yes. The docs now default to Avo 4, and search is scoped per version. Search inside the Avo 4 section and you'll only get Avo 4 results (same for Avo 2 and 3).

No. Keep using Avo 3 and jump to 4 whenever you're ready.

Yes. We plan to support Avo 3 for a long time with security updates and critical bugfixes. As long as you keep an active subscription, you get access to updates.

There are some DSL changes, which are breaking changes. We only touched the APIs that genuinely needed improving. They're all documented in the upgrade guide.

Yes, Avo 4 has a full redesign with a modern look, color scheme support (light and dark modes), and neutral and accent color customization. The UI stack is Tailwind CSS 4, with CSS variables mapping colors, spacing, and layout. A skilled front-end dev, or an LLM, can reshape it into whatever they want.

Yes. We reworked many screens and variations so everything is tighter on smaller screens.

Accessibility (a11y) was a goal from the start, since many of our customers work under strict regulations. We're committing to WCAG 2.2 going forward.

Avo 4 is almost VIM-mode now. A few examples:

• Shift + T: focus the table/grid, then browse with arrow keys
• J / K: navigate records without focusing
• Return: visit a record · E: edit · D: delete · B: back
• A: open the Actions dropdown (then arrow-navigate)
• Command + Return: save
• Shift + N / Shift + A / Shift + M: cycle neutral colors / accent color / color scheme

Hit Shift + ? to see all the shortcuts.

Kanban boards, custom forms, an HTTP resource, automatic API endpoints, notifications, reactive fields, collaboration chat, improved global and resource search, and a redesigned summarizable feature that works under associations, with filters applied, and has its own dedicated page. Plus hundreds of smaller improvements across Dashboards, Dynamic Filters, Nested Records, Menu, and Custom controls.

Avo 4 requires Ruby 3.2 or greater and Rails 6.1 or greater.