๐ŸŽ‰ BIG NEWS ๐ŸŽ‰  โœฆ  Avo 4 has officially SHIPPED  โœฆ  ๐Ÿš€ the beta is over, 4.0 is here  โœฆ  ๐Ÿ› ๏ธ build admin panels, dashboards & internal tools at light speed  โœฆ  โญ you are visitor #1,136,501  โœฆ  ๐ŸŽŠ tell a friend  โœฆ  best viewed in Ruby on Rails  โœฆ  ๐Ÿ‘‰ click here to see what’s new  โœฆ 

Back to pricing
Gemfile

Visualize and manage workflows with drag-and-drop boards. Perfect for order processing, content pipelines, and task management.

# $20/mo

1 gem "avo-kanban"

Give your team a board where work moves by dragging it, not by editing a status field one record at a time. Kanban turns any Avo resource into cards you can drag between columns, and every move writes straight back to the database: each board tracks one property on your records, the columns are that property's values (Backlog, In Progress, Done), and dropping a card in a new column updates the record and remembers its position.

A column connects to your models polymorphically, so one board can hold more than one resource type at once, the way GitHub Projects mixes issues and pull requests. You pick which resources a board accepts with the allowed_resources setting, add cards through the resource's own search, and reorder columns and items with drag-and-drop backed by acts_as_list. A board view, the persistence, the drag interactions, and the authorization hooks are a fair amount of moving parts to build and keep working: here you add a gem and run one generator instead.

What you get

  • Move work by dragging it instead of editing a status field one record at a time: drag cards between columns, with positions persisted via acts_as_list
  • Trust the board to match the data: each board tracks one record property, so a drop into a new column updates that property and remembers the card's place
  • Run one board across more than one kind of record, the way GitHub Projects mixes issues and pull requests, with polymorphic columns
  • A running board from one command: rails generate avo:kanban install scaffolds the board, column, and item resources, controllers, and migration
  • Decide what belongs on a board with the allowed_resources setting, then add cards from each resource's own search, with exclude_duplicates to keep a record from landing on the board twice
  • Make cards look like your domain, not a generic tile, by ejecting Avo::Kanban::Items::ItemComponent
  • Keep each board and action to the right people with Avo::Kanban::BoardPolicy (show?, edit?, add_column?, add_item?, manage_column?)

Why it pays off

  • Ship a working board this afternoon instead of speccing the drag interactions, the position bookkeeping, and the polymorphic data model over a sprint.
  • The reordering, persistence, and authorization are the parts that break quietly later, here they are written, reviewed, and maintained by us, not bolted onto your admin alone.
  • Every Avo release makes it better: the board, drag-and-drop, and columns keep working through upgrades, without your board getting stranded or you patching it.
  • One less internal tool for your team to build, document, and support, keeping your developers on your product.

# included in

# ready to ship?

You ship it this afternoon. We keep it solid for years.