I know that Rails devs will immediately think of Active Admin, administrate, and other similar projects, and I want to mention that Avo is not them. We also provide technical support for enterprise-like customers.
You get access to partials, controller, action, params, and anything else you need to bring your own logic into the UI on every level (field, resource, tool).Īvo has a free Community version that features the powerful CRUD UI, and a paid Pro version for those who need more power and custom content. It enables the developer to extend it even further using regular Rails code.
The Custom Content part is the secret sauce of Avo. The Dashboards are a light layer on top of chartkick where one can query the data from the DB or an endpoint and quickly show the data in metrics, charts, or custom partials. It features about 30 fields with more advanced ones like (one-liner) file uploads, WYSIWYG, and key-value fields.
Instead, it's a familiar Ruby DSL that's easy to extend with Rails code if you need to break away from it. The CRUD UI is not something generated that takes maintenance in the long run. Now, in just an hour, a developer can build production-ready applications that with traditional coding techniques take a few days, if not weeks.Īvo is suited to agencies that build a lot of products for their clients and need to move fast and have a beautiful and robust UI, indie developers trying to test out their ideas fast, technical teams in companies of all sizes that need to build internal tools based on Ruby, and start-ups.Īvo runs on top of Ruby on Rails, which is a powerhouse of a framework and uses the most modern tech stack (Hotwire, TailwindCSS, esbuild).Īvo has three main parts that you can choose from: I took those patterns and applied them to Avo.
After a while, you start to notice patterns and extract functionality away to make the job easier. For more than ten years, I built countless admin panels and back-offices for all types of apps. I'm Adrian, an indie developer and creator of Avo. I do see an ecosystem of third-party services that integrate with SaaS kits emerging, such as rapid ways to deploy, analytics services, etc. What will end up costing money is tech support. My thinking on the economics of this is the Opencore stuff will be a race to the bottom in terms of pricing towards free or a nominal fee (I guess $250/year is that). should be modeled, it opens up the door for a set of APIs and plugins that will make creating SaaS products even easier.
If the community agrees on how users, authorization, subscriptions, etc. I'm hoping enough people converge around any one of these products where we end up with something as high quality as Rails. I started to piece on together for my own projects at, which will be open source, $0, and MIT licensed. Some of the libraries I'm noticing that seem "settled" include: I've even started to piece on together for my own projects at, which will be open source, $0, and MIT licensed.
I've started to look into full stack starter-kit frameworks that goes beyond the admin panel and here's what's out there these days. It's great to see folks building frameworks on top of frameworks.