Rhubarb vs. Flourish: Which Data Visualization Tool Fits the Work?

The decision in one minute

Choose Flourish when you want a polished chart or story built inside a mature template system, especially when the format already exists and the team values Flourish’s editor, stories, scrollytelling, and publishing workflow. Its current Assistant can make editor changes from plain-language prompts, and its Connector can let an external LLM create Flourish charts.

Choose Rhubarb when the first question is analytical rather than visual: “What is happening in this data?”, “Which group is different?”, or “What should I show?” Rhubarb’s assistant can work across the source, data preparation, and custom visualization, then keep revising the result conversationally. The relevant data-source SQL, D3, and JavaScript remain visible and editable.

This comparison was re-checked against official product materials on August 19, 2026. The AI landscape has changed quickly; the useful distinction is no longer “AI versus no AI,” but what role the AI plays in the workflow.

What Flourish is designed to do

Flourish is a data visualization and storytelling platform built around a large catalog of responsive templates. Its strengths include polished standard visualizations, maps, stories, scrollytelling, interactive content, and a consistent editor that lets nondevelopers produce publication-ready work.

Flourish now also has a built-in Assistant powered by Claude. You can describe changes in plain language—style, layout, labels, accessibility, highlighting, and other editor actions—and the Assistant applies visible, reversible settings. Flourish also offers a Connector that lets tools such as Claude or ChatGPT create Flourish charts from a conversation.

That is a meaningful AI workflow. The important boundary is that Flourish still centers the template/editor model: the Assistant helps operate and refine Flourish, and the Connector creates Flourish visualizations that you then edit in Flourish.

What Rhubarb is designed to do

Rhubarb puts the conversation one step earlier. You can upload or connect data and ask what you want to understand before deciding on a chart type. The assistant can inspect fields, write a query, join or aggregate data, choose a useful first visual form, and then build or revise custom D3 and JavaScript.

That makes Rhubarb feel less like “AI operating a chart editor” and more like working with an AI data analyst and visualization developer in the same project. This is especially attractive to AI adopters who would rather ask “Which segments are driving the change?” than manually map fields and test several chart types first.

Rhubarb also keeps the useful result close to production: narrowed data, visible code, versions, hosting, embeds, connected refreshes, and access settings stay attached to the project. It can host visualizations that are delivered inside your own paywalled or authenticated experience.

Where Flourish is likely the better choice

The desired format already exists as a template

When the job is a familiar animated bar chart, map, story, quiz, timeline, or another supported format, Flourish can provide a shorter path from data to a polished result. The constraints of the template can be an advantage: creators do not need to design every interaction and layout rule.

A broad nontechnical team needs a standardized workflow

A template editor makes it easier to train many occasional creators and maintain consistent output. Teams can focus on data and configuration rather than reviewing code for every project.

Scrollytelling or presentation-style stories are central

Flourish explicitly positions stories and scrollytelling as core capabilities. When the narrative mechanism is a sequence of states revealed by clicks or scroll, those built-in patterns may be more efficient than engineering the experience from scratch.

You need established template behavior across many similar projects

A reusable template reduces variation and gives an organization a stable production system. This is particularly useful for recurring editorial formats with consistent data structures.

Where Rhubarb is likely the better choice

You want to explore the data before you know the chart

Rhubarb is strongest when the request begins as a question. Ask the assistant to compare groups, find changes, test a denominator, or suggest a useful visual. The analysis and visualization can evolve together instead of requiring you to settle on a template first.

The interaction does not fit a catalog

Rhubarb is designed for experiences such as unusual visual crosstabs, custom Sankey behavior, linked explanatory views, custom drilldowns, or a page that combines several visual forms around one story.

Code review is part of the requirement

Rhubarb keeps the relevant data-source SQL and visualization code visible. A technical reviewer can inspect, edit, and maintain the implementation rather than treating the normal project output as a closed template configuration.

Data querying and visualization development need one workflow

Rhubarb can separate a reusable connected source from the narrowed query used by a visualization. The assistant can help draft both query and visual code, and the connected result can refresh after publication.

Every client or research question needs a tailored result

Consultancies, researchers, and data storytellers may reuse interaction patterns without wanting every output to share one fixed template. Rhubarb favors project-specific composition and behavior.

How the authoring experience differs

Flourish can now be conversational too, but the conversation works through Flourish’s chart-and-template environment. You can use the Assistant to change settings in plain English, or use the Connector from an LLM to create charts that land in the Flourish editor.

Rhubarb’s conversation covers more of the path from source data to finished result. Ask a question about the uploaded or connected data, let the assistant write the query and choose what to visualize, then keep refining the analysis and the custom web behavior. For an AI-first user, that can remove more of the “which field goes where?” work before a useful view exists.

Neither approach is universally better. Templates trade some freedom for speed and consistency. Custom visible code trades some predictability for control and a higher ceiling.

Publishing and maintenance

Both products support hosted interactive output and embedding. Flourish also offers password-protected publishing on applicable plans. Rhubarb can host a visualization while it is presented inside your own paywalled or authenticated site, and keeps the data source, query, versions, access settings, and refresh workflow with the project.

For either product, inspect what data is delivered to the browser, test the real embed environment, and establish an owner for future updates. A hosted embed makes global updates easier, but it also means a later edit can change every placement.

Accessibility and quality review

A template platform can provide consistent baseline behavior across supported formats, but the creator still needs to review labels, color, motion, text alternatives, and the meaning of controls. A custom-code platform can implement a more tailored accessible interaction, but accessibility must be included in the specification and tested.

Do not decide based only on a desktop screenshot. Test keyboard navigation, touch, small screens, enlarged text, null data, long labels, and an empty state in the exact format you intend to publish.

Try the same real project in both tools

Use one real project and build the same minimum viable result in both tools. Do not compare a fully customized version in one product with a default template in the other. Measure:

• time to a correct first version;
• time to implement the distinctive interaction;
• analytical review effort;
• responsive and accessibility quality;
• ease of incorporating stakeholder revisions;
• ease of updating data one month later;
• whether the team can maintain the result without its original builder.

The pilot will reveal whether the project is primarily a template-selection problem or a custom-experience problem.

Bottom line

Flourish is a strong choice when you want a proven template, story, or scrollytelling workflow and AI assistance operating inside that system. Rhubarb is a strong choice when you want to begin with the data question, use AI to do more of the analytical work, and end with a custom, inspectable visualization rather than a template-bound result.

For AI adopters, the difference can feel simple: Flourish helps you work faster in Flourish; Rhubarb tries to let you work with the data itself through the assistant. Both are useful models, and the right one depends on whether the template or the analytical question should drive the workflow.

Comparison at a glance

The simplest distinction is template-led visual storytelling versus AI-assisted custom visualization work.

Decision factor	Rhubarb	Flourish
Best default fit	Bespoke interactive visualizations and tailored data products.	Template-led interactive visualizations, stories, animation, and scrollytelling.
Normal authoring model	Ask the analytical question; AI can shape/query the data and build custom code, with direct code access.	Choose or generate a Flourish template; use editor settings and the AI Assistant to refine it.
Custom development path	Project-specific data-source SQL, D3, and JavaScript are part of the ordinary workflow.	Standard work is template-led; custom reusable templates can be built with the SDK.
Built-in narrative formats	Custom narrative behavior can be built for the project.	Stories and scrollytelling are explicit built-in product strengths.
Publishing	Hosted pages and embeds, including delivery inside your own paywalled/authenticated experience; versions and connected refreshes.	Hosted responsive visualizations and embeds; password-protected publishing is available on applicable plans.
Team standardization	Standardize review patterns while allowing project-specific implementations.	Standardize output through reusable templates and a no-code editor.
Main tradeoff	AI can do more of the analysis and custom build, with more responsibility to review the result.	Very fast polished production inside a strong template system, with customization bounded by that system.
AI role	Integrated data analyst + query/code assistant across exploration and custom visualization.	Assistant operates/refines the Flourish editor; Connector lets external LLMs create Flourish charts.

Decision rule: Use Flourish when the job is best expressed as a Flourish chart or story and you want AI to speed that workflow up. Use Rhubarb when you want to start with the analytical question and let the AI help discover, query, and build the visual answer.

Frequently asked questions

Is Rhubarb a direct replacement for Flourish?

No. Flourish is excellent for template-led visual storytelling and now has meaningful AI assistance. Rhubarb is more relevant when the assistant needs to work across the analysis and a custom implementation, not only inside a template workflow.

Can Flourish create custom visualizations?

Yes. Flourish offers a developer SDK for reusable custom templates, and its 2026 AI Connector and Assistant add more AI-driven creation and editing. Rhubarb’s ordinary project workflow is still different because project-specific SQL and visualization code remain visible and editable.

Which tool is better for scrollytelling?

Flourish explicitly provides built-in stories and scrollytelling workflows. Rhubarb can build custom narrative interaction, but a ready-made Flourish story format may be faster when it matches the brief.

Official sources reviewed

Products change quickly. These are the official pages checked for the current comparison.

1. Rhubarb — product overview — Rhubarb Analytics Inc. (August 19, 2026)
2. Flourish — product overview (August 19, 2026)
3. Flourish Assistant — official product page (August 19, 2026)
4. Flourish Connector — official product page (August 19, 2026)
5. Flourish pricing — password-protected publishing (August 19, 2026)