I would say that the Community version (free) covers most of what Active Admin does. The search is paid with Avo (and included in AA). The Pro users are those

I would say that the Community version (free) covers most of what Active Admin does. The search is paid with Avo (and included in AA). The Pro users are those who need to build upon Avo. They need custom content (fields, resource tools, custom pages), and they need to make it look the same as the rest of the app. Avo provides view components that help with that. This way you create a seamless UI for your users. I think of Avo as more than just and admin panel framework (although power tool sounds great), but the place where you build your app. It becomes the app your users see. Regarding API based apps, yeah, that's something I'd loke to support soon. Offer HTTP adapters where you coudl hook in your Stripe/Shopify/Intercom/Custom API endpoints. Regarding complexity, I tried to cram as much as I could (whenever I push out a new feature, I add it) to the demo site[0]. One of the biggest apps I've seen has about 41 resources, 431 fields, and quite some complexity because it's a multi tenancy app that serves three marketplace platforms. There's a lot of complex scoping applied to the data to match the accounts and views. But, yeah, I'd love to see an app that size. I think the project is still young (about two years. version 2.0 three months old) and these kinds of projects tend to get built out with time. I can't imagine there are a lot of teams with an app that size you mentioned that are in a hurry to rip out everything they have to replace it with Avo (or any other package or app) in such a short time. Even our customers above are slowly switching from their homegrown admin panel to Avo. Right now, the UI customization wasn't our main concern. I do want it to look amazing so I work a lot (alongside the designer) to keep it looking excellent. This being Rails, you can always override the partials and view components to add your own and tweak Avo's. The first iteration of UI customization will be to enable the developer to change the colors of the UI. Regarding general customization, you can already plug in Avo on multiple levels. One can add new fields, sections on resource pages, totally new custom pages, etc. Avo is ready for customization complexity. [0] https://avodemo.herokuapp.com/ https://avodemo.herokuapp.com/