Chartio

Overview

Chartio tried to make business data explorable by people who did not write SQL. It connected to company databases and cloud sources, translated visual choices into queries, and rendered interactive charts and dashboards in a browser. Founder Dave Fowler described it as a translator between databases and humans.

The company survived a difficult start, found paying customers across more than 25 countries, and spent a decade pursuing self-service business intelligence. Atlassian acquired Chartio in February 2021 for about $45.6 million, then retired the standalone service in March 2022 so the team and technology could become an analytics layer across Atlassian products. Atlassian Atlassian annual report

Founding Story

Fowler began writing Chartio in 2010 because inspecting a database was needlessly indirect. He had to write a query, export results, or connect a charting library before he could see what the data meant. He wanted charts to be interactive starting points for exploration, not static answers assembled by specialists.

The path to launch was uneven. Fowler's own account lists Y Combinator, choosing not to raise at first, parting with a cofounder, running out of money, working alone for ten months, raising $20,000, recruiting another cofounder, and disappointing early customers before the product improved. Chartio moved from private beta to a general launch in November 2012, more than two years after the first code. Chartio

This history matters because the eventual product looked simple. A user connected a source, selected fields, added filters, and built a dashboard. Behind that interface, Chartio had to understand several SQL dialects, generate valid analytical queries, combine results, manage credentials, and keep dashboards responsive. Ease of use was the output of substantial hidden work.

Timeline

• 2010: Fowler begins building Chartio and enters Y Combinator's Summer batch.
• 2011: Chartio raises a reported $3.15 million Series A led by Avalon Ventures, with Bullpen Capital participating.
• 2012: The company opens its private beta and launches Chartio publicly in November.
• 2013: Chartio reports 500,000 charts per week and paying customers in more than 25 countries. Chartio
• 2014: It raises another $2.2 million and adds data blending, formulas, and analytics services. Chartio
• 2021: Atlassian acquires Chartio. The company reports 10.5 million charts, 540,000 dashboards, 280,000 users, and more than 100,000 connected data sources. Chartio
• 2022: The standalone Chartio service ends on March 1 while its team builds analytics for Atlassian.

What They Built

Chartio was a cloud business-intelligence product. It connected to transactional databases and analytical systems including MySQL, PostgreSQL, SQL Server, Redshift, BigQuery, Salesforce, and CSV files. Its visual query builder let users select columns, joins, filters, groupings, and calculations. Chartio generated the source-specific SQL and returned a visualization.

Dashboards supported interactive filters, scheduled email reports, tables, and a proprietary charting library. Data blending combined results from multiple sources without requiring a customer to create a warehouse first. The company also added professional services for customers who wanted analyst and database expertise alongside the software.

The product's central promise was broader access, not the elimination of data teams. Analysts could prepare schemas and trusted dashboards; business users could ask follow-up questions without entering a ticket queue for every chart. That promise required guardrails because direct database access also creates permission, performance, and metric-consistency risks.

Market Position

Target Customers

Chartio initially appealed to startups and internet businesses with cloud databases but small data teams. Its self-service onboarding and free trial contrasted with enterprise BI sales that began with a demo request. Public customers included Indiegogo, Mozilla, Ancestry.com, and the Dallas Museum of Art. Over time, the buyer could be a data leader, operations team, product team, or executive seeking shared dashboards.

Market Size

Business intelligence is a broad software category because nearly every growing organization accumulates operational, customer, and financial data. Chartio addressed the portion willing to connect cloud sources to a hosted tool and let non-analysts explore them. The opportunity expanded as Redshift, BigQuery, and managed databases made analytical data easier to centralize.

Competition

Tableau had made visual analysis more approachable, while Looker, GoodData, Birst, Mode, Periscope Data, and later many warehouse-native tools competed for cloud customers. Spreadsheet exports and internal dashboards remained substitutes. Chartio's differentiation was a browser-first visual query experience with direct connections and fast trial adoption. Its risk was category compression: warehouses added visualization, BI vendors added self-service, and application platforms embedded their own analytics.

Business Model

Chartio sold recurring subscriptions to its hosted product. Pricing could scale with users, features, support, and database needs. The free-trial entry reduced sales friction for smaller teams; services addressed customers that needed implementation work or analyst capacity.

Public usage figures show that customers created and viewed many artifacts, but Chartio did not publish audited revenue, margins, retention, or profitability. Atlassian's filing provides the clearest financial endpoint: about $45.6 million in purchase consideration, consisting of $45.0 million cash and $0.6 million equity, plus $4.5 million in restricted shares for key employees tied to future service. Atlassian annual report

Traction

One year after public launch, Chartio said it generated 500,000 charts per week and had paying customers in more than 25 countries. At acquisition, it reported 10.5 million charts on 540,000 dashboards for 280,000 users pulling from more than 100,000 sources. These figures came from the company, but they describe years of real product use and connected data.

Atlassian's willingness to buy the company and retire the standalone service also identifies the strategic asset. Chartio's technology could become a common visualization engine across Jira and other Atlassian products, where large volumes of work data already lived.

Post-Mortem

Chartio was acquired rather than failing through a sudden collapse. Atlassian bought all outstanding equity on February 26, 2021. The price was meaningful relative to the public funding amounts, but the available records do not show the capitalization table or individual returns. It is fair to call this an exit; it is not possible to calculate who did well.

The customer outcome was less continuous. Atlassian wanted Chartio's team and technology for cross-product analytics, not a permanently separate BI vendor. Chartio warned customers that the product would go away on March 1, 2022 and provided migration guidance. The acquisition preserved the technical work while ending the service customers had bought.

Why did independence end? Chartio competed in a crowded market where connector breadth, governance, semantic consistency, and enterprise distribution all demand sustained investment. Atlassian already owned a large installed base and a rich set of work data. For the buyer, Chartio could be more valuable embedded across that base than sold as one more general BI tool. For Chartio, joining converted a long competitive campaign into a defined transaction and a larger deployment surface.

The case separates three kinds of success. The company survived for more than ten years, reached extensive usage, and sold for a disclosed sum. The standalone product still closed. Acquisition can reward shareholders and continue technology while forcing customers to leave.

Key Lessons

1. Simple interfaces hide difficult systems work. Visual querying required dialect translation, credentials, performance controls, and understandable errors.
2. Self-service changes the buying motion. A free trial let users prove value before a traditional enterprise process.
3. Artifact counts are not company economics. Dashboards and charts showed engagement but did not disclose retention, revenue, or margins.
4. Embedded distribution can outweigh standalone breadth. Chartio's engine had a clearer strategic role across Atlassian's products than as an independent BI suite.
5. An acquisition can end a useful product. Teams, technology, and shareholder value may continue even when customers must migrate.

Sources

• Atlassian acquisition announcement
• Atlassian FY2021 annual report
• Chartio acquisition post
• Chartio launch story
• One year after launch
• Chartio 2014 funding and product update
• Chartio service closure notice
• Chartio state-of-company post