Top 30 Business Intelligence & Analytics Platforms 2027

This report forms part of The Economy Rankings’ Artificial Intelligence & Data portfolio. Technology Ranking 2027 | Artificial Intelligence & Data | Business Intelligence & Analytics Platforms

Business intelligence becomes dependable when users can ask useful questions and understand the definitions behind the answers. Attractive dashboards are part of that experience, but shared metrics, governed access and maintained analytical content determine whether the same information remains trustworthy across departments, applications and changing business requirements.

Business Intelligence & Analytics Platforms compares 30 named products spanning enterprise reporting, semantic modeling, self-service exploration and embedded analytics. Each supplies an actual analytical experience. Data warehouses without BI and consultancy-only reporting assignments fall outside the scope, even when they support the same business decisions.

The 2027 edition draws on product research conducted in October 2026. It evaluates documented functionality and inspectable operating workflows. The assessments do not represent a common usability trial, an independent security audit or measured productivity gains across every product. Vendor awards and customer logos do not establish technical superiority.

Tier I identifies the strongest overall results against the weighted editorial criteria. Tier II and Tier III contain substantial eligible platforms with different technical emphases. The leading five are numbered; the remaining bands are alphabetical. Placement should inform a requirements-led evaluation rather than replace it.

Market Overview

The market increasingly joins semantic definitions with several consumption interfaces. A metric may appear in a dashboard, embedded application or conversational interaction. The important question is whether those experiences preserve its meaning and permissions. Adding another interface does not, by itself, create a reliable analytical foundation.

Deployment patterns also differ. Some platforms maintain analytical models in code, others emphasize visual authoring, and many combine both. These choices affect who can change logic, how revisions are reviewed and what happens to dependent content. Self-service works best when responsibility for shared definitions remains explicit.

Embedded analytics adds an application boundary. Temporary tokens, consumer identities, dataset permissions and tenant data layout can matter as much as chart features. An integration should be evaluated through the actual identity and storage arrangement, because two products can display similar dashboards while assigning very different work to developers.

Governance depends on effective access rather than role names alone. Owners and administrators can have exceptions to ordinary row filters. Content permissions, model rights and underlying database access may form separate layers. A realistic evaluation traces the consumer through all of them, including routes used outside the main dashboard.

Corporate consolidation changes the product map without necessarily ending a maintained analytical offering. The profiles identify current operators and consolidate overlapping acquired brands. Provider founding dates are kept distinct from product launches, rebrands and group formation; accurately labeled offices or business bases are used where a conventional headquarters claim would overstate the evidence.

Industry Trend — 2027

These developments frame analytical platform choices for 2027. They describe current engineering and procurement considerations, rather than claiming observed future outcomes.

2027 market development	Current evidence and direction	Implication for the sector
Shared semantic definitions	Metrics increasingly serve dashboards, exploration and AI-assisted interfaces.	Test whether the same definition and access rules survive each consumption path.
Analytics as maintained code	Git workflows and validators bring model changes into existing development practices.	Include a field rename or metric revision in the pilot and inspect dependent content.
Embedded consumer identity	Application analytics relies on scoped sessions, permissions and tenant-aware data design.	Evaluate the actual storage layout and token lifecycle with representative customer identities.
Guided and open exploration	Story-oriented consumption and flexible authoring address different analytical tasks.	Choose through realistic user questions, rather than assuming one interface suits every audience.
Explicit administrative exceptions	Owners and privileged roles may bypass restrictions applied to ordinary consumers.	Test effective access for readers, authors and administrators separately.
More consequential model reuse	Shared models and extensions distribute analytical logic across teams.	Confirm where local overrides are allowed and who maintains the resulting business meaning.

A strong pilot follows a business question from its source data through model, visualization and permissions, then repeats the exercise after a controlled change.

Methodology — Core Eligibility Criteria

The ranking uses an evidence-based editorial assessment tailored to this technical market. Candidates were required to satisfy the following core conditions:

• The entry must be a current named platform providing dashboards, analytical exploration, reporting or decision-support workflows.
• A maintained analytical product must be documented; consultancy-only reports and warehouse storage without BI do not qualify.
• First-party product or technical references must establish current functionality and the relevant consumer or authoring workflow.
• Current ownership, material acquisitions and absorbed products must be identified, with one consolidated placement per provider group.
• Provider origins and headquarters or accurately scoped company-office information must remain distinguishable from product release dates.
• Deployment, edition and launch-stage limits must be identified when they materially affect a described capability.
• Material comparative claims require appropriate evidence; vendor demonstrations are not relabeled as independent tests.
• Selection, scoring and tie decisions remain independent of licensing, promotion and recognition purchases.

Methodology — Ranking Factors

• Analysis and semantic capability — 30%: Exploration, dashboards, calculations, reusable definitions and decision-support workflows. The assessment considers analytical depth and consistency rather than the visual appearance of a demonstration alone.
• Usability and operational evidence — 25%: Inspectable authoring, consumer and maintenance workflows, with attributable deployments or tests where relevant. Documented functional provision supports editorial judgment without implying a common controlled usability study.
• Governance and reliability — 20%: Semantic consistency, model and content permissions, refresh dependencies and controlled distribution. Effective access and lifecycle behavior matter alongside the existence of individual security features.
• Data and application integration — 15%: Sources, embedding, APIs and maintainable developer or administrative workflows. Integration is assessed through supported arrangements rather than connector totals or general ecosystem reputation.
• Technical transparency — 10%: Public help, release information, feature boundaries and documented constraints. Clear disclosure of administrative exceptions and edition requirements strengthens the evidence available for evaluation.

The five criteria carry weights of 30%, 25%, 20%, 15% and 10%, respectively. The private research record documents criterion-level editorial assessments and supporting sources. These are judgments about the documented offering, not scores from laboratory tests performed by The Economy Rankings. Missing material evidence is pursued before selection rather than silently treated as average performance. Licensing, sponsorship and likelihood of purchasing recognition do not influence eligibility, scores or tier placement.

Company Profiles and Further Reference

Names appearing in this ranking are linked to their corresponding organizational profiles in The Economy Wiki, where available. These profiles provide further background on principal activities, technology capabilities, product and service portfolios, market positioning and related rankings and analysis across The Economy Network.

Where an entry identifies a product or service line, its provider or operator is identified so that the scope of the organizational profile is clear. The Economy Wiki profiles are maintained as editorial reference pages and may be updated as new public information becomes available.

---

Tier I — Leading Business Intelligence & Analytics Platforms

1. Microsoft Power BI

• Provider / operator: Microsoft
• Headquarters: Redmond, Washington, United States
• Provider origins: 1975

Microsoft Power BI combines visual reporting with a semantic modeling environment built around relationships, reusable measures and explicit storage choices. Its strength is the connection between business-facing analysis and a model that can carry shared definitions across many reports. A dashboard is therefore one consumer of the analytical model, rather than the only place where an organization defines its calculations.

Model designers can use DAX, calculation groups and relationship management, while administrators configure and validate role-based row filters. Integration extends through XMLA, REST and model metadata interfaces. Microsoft also documents limits: layering another semantic model beneath a DirectQuery model can produce incorrect calculations and is generally unsupported. That warning makes integration semantics a material engineering consideration.

Power BI leads the assessment through analytical depth and broad, inspectable integration. It suits enterprises prepared to manage models as maintained assets. A useful implementation review traces a measure from its definition to each report and tests effective permissions under the consumer's actual workspace role, rather than assuming that every access context applies identical restrictions.

2. Looker

• Provider / operator: Google
• Headquarters: Mountain View, California, United States
• Provider origins: 1998

Looker organizes business intelligence around LookML models and Explores that translate underlying data into reusable analytical definitions. This provides a structured foundation for dashboards, exploration and embedded data applications. Its strongest case is an organization that wants business metrics governed through a maintained model, with developers taking explicit responsibility for how users navigate relationships and analytical fields.

Content validation checks references used by saved analysis and dashboards when model definitions change. LookML validation addresses another part of the development workflow. Access grants use user attributes to restrict structures including Explores, joins, views and fields. The distinction between model privileges and content permissions is important: a developer can repair references under conditions that do not simply mirror ordinary dashboard-edit access.

Tier I reflects unusually clear semantic governance and technical transparency. Looker is especially relevant where analytical definitions need controlled evolution across many consumers. Evaluation should include a realistic field rename, an access-policy change and dependent content validation, demonstrating how the model remains usable as business logic develops rather than judging only the initial dashboard.

3. Tableau

• Provider / operator: Tableau / Salesforce
• Provider headquarters: San Francisco, California, United States
• Provider origins: 1999

Tableau places interactive visual exploration at the center of its analytical experience. Users can build views, refine questions and organize results into workbooks, while shared data sources and preparation workflows supply a more durable foundation than isolated charts. Its inclusion evaluates this maintained analytical platform, with Salesforce identified as the current corporate owner rather than granted an additional independent placement.

Worked documentation shows how a view evolves during exploration. On the governance side, virtual connections can centralize credentials and apply row-level data policies to dependent workbooks, data sources and flows. A virtual connection need not contain a policy, however, and the functionality has specific Data Management scope. Organizations must distinguish an available shared connection from an actively governed analytical access path.

Tableau earns Tier I through strong analytical authoring and documented governance provision. It is particularly suited to teams that value visual investigation while maintaining shared data definitions. A representative evaluation should examine how exploratory work becomes reusable content, then verify that preparation, publication and connection-level policies preserve the intended consumer experience as underlying information changes.

4. Sigma

• Provider / operator: Sigma Computing
• Company base: San Francisco, California, United States
• Provider origins: 2014

Sigma brings spreadsheet-oriented interaction to analytical workbooks and reusable data models. The product is relevant where business users need an approachable authoring environment without separating their analysis from governed cloud data. Its contribution is the connection between familiar analytical interaction, shared modeling and a maintained workbook lifecycle, rather than a claim that a spreadsheet-like interface automatically removes the need for data engineering.

Version history gives authors an inspectable record of workbook changes. Row- and column-level controls provide another layer of administration, including rules based on viewer attributes and, where configured, inherited platform policies. The documentation explicitly warns against using mutable control elements as row-security mechanisms because downstream parameters can change them. That distinction separates presentation interactivity from an effective authorization boundary.

Tier I recognizes a strong combination of analysis, lifecycle evidence and technical candor. Sigma fits organizations connecting business authoring with managed analytical data. A pilot should test reuse of a shared model, workbook revision and restricted consumer access together, ensuring that the convenience of interaction rests on dependable definitions and correctly implemented permissions.

5. Qlik Cloud Analytics

• Provider / operator: Qlik
• Provider headquarters: King of Prussia, Pennsylvania, United States (Qlik headquarters)
• Provider origins: 1993

Qlik Cloud Analytics combines analytical applications, reusable data assets and managed collaboration spaces. Its current cloud scope continues the Qlik Sense analytical lineage without treating cloud and Windows editions as separate providers. The platform is relevant to organizations that want users to explore connected business information while retaining explicit responsibilities for loading, ownership and publication of analytical applications.

Reload monitoring and space troubleshooting make those responsibilities concrete. An application can depend on a source in another space, and losing access there can cause reload or access failures. Ownership transitions and changes to space roles also require attention. Shared and managed spaces therefore provide useful organizational controls while leaving administrators with real dependencies to maintain across the analytical lifecycle.

Qlik takes Tier I through balanced analytical capability, governance and operational documentation. Its strongest fit is a collaborative estate in which applications and data sources are actively administered. Evaluation should include an ownership handover and a source-access change alongside normal exploration, testing whether the organization's operating model keeps published analysis dependable after the original author moves on.

---

Tier II — Established Business Intelligence & Analytics Platforms

(Alphabetical order)

GoodData Cloud

• Provider / operator: GoodData.AI
• Company headquarters / US base: San Francisco, California, United States
• Provider origins: 2007 (GoodData company origins)

GoodData Cloud organizes analytical applications around logical data models, reusable metrics and workspaces. The model describes business-facing datasets and relationships above the physical database, giving developers a foundation for consistent reporting and embedded consumption. The provider now presents its broader business as GoodData.AI; this placement evaluates the cloud BI offering rather than transferring every adjacent agent capability into its analytical assessment.

Current release documentation describes maintained permission controls, including column-level restrictions, and distinguishes earlier beta stages from generally available provision. Workspace hierarchies provide a way to reuse definitions across related environments. APIs and embedding extend that model into applications, but the relationship between inherited definitions, workspace permissions and customer-specific configuration still needs an explicit design rather than an assumption of automatic tenant isolation.

Tier II reflects strong semantics, governance and application integration. It is particularly relevant where a team wants to build repeatable analytical experiences over shared business definitions. Evaluation should trace a metric and its permissions through related workspaces, confirming how the intended consumer sees both ordinary and restricted information.

Holistics

• Provider / operator: Holistics
• Company-declared headquarters: Central Business District, Singapore
• Provider origins: 2015

Holistics approaches business intelligence through reusable analytical definitions and datasets maintained with software-development practices. Analysts can define logic once and apply it across reports, while business users explore prepared data. That combination is useful when an organization wants self-service consumption to depend on reviewed analytical code rather than repeated manual calculations hidden inside separately maintained dashboards.

The platform keeps an internal Git repository and can mirror analytics code into supported external repositories. This enables existing review and deployment workflows, including CI/CD-driven publication. Row-level permissions and user attributes provide a separate data-consumption boundary. Documentation also identifies practical limits, including plan scope for external Git and verification requirements for custom Git domains, rather than presenting every repository arrangement as immediately interchangeable.

Tier II recognizes particularly coherent analytics engineering and governance. Holistics fits teams willing to treat shared business logic as a maintained codebase. A useful evaluation changes a metric through review, publishes it and checks dependent reports under different user attributes, demonstrating consistency between the development process and the business-facing result.

IBM Cognos Analytics

• Provider / operator: IBM
• Headquarters: Armonk, New York, United States
• Provider origins: 1911

IBM Cognos Analytics combines reporting and dashboards within an enterprise environment governed by explicit capabilities and content rights. Its relevance is strongest where analytical distribution involves different classes of authors, explorers, viewers and administrators. The assessment concerns Cognos Analytics itself, with IBM's provider identity used for the fact box rather than treating its entire software portfolio as one analytical product.

Capability tables describe permissions such as read, write, execute, traverse and policy administration. These distinctions help explain why access to a folder, a dashboard feature and an underlying analytical operation may require different rights. Documentation also separates capability configuration from defaults associated with license roles. Purchasing or assigning a role is therefore only part of establishing the intended effective analytical access.

Tier II recognizes substantial enterprise analysis and detailed administrative control. Cognos is particularly relevant to organizations maintaining governed reporting alongside interactive exploration. A practical review should follow representative authors and consumers through content navigation, execution and policy changes, confirming that the configured capabilities match real responsibilities rather than relying on role names alone.

Oracle Analytics Cloud

• Provider / operator: Oracle
• Provider headquarters: Austin, Texas, United States
• Provider origins: 1977

Oracle Analytics Cloud provides semantic modeling and analytical workbooks for enterprise reporting and exploration. Shared models give business calculations and relationships a reusable foundation, while workbooks supply a consumer-facing analytical experience. This makes the platform relevant where organizations need to maintain business definitions over time instead of rebuilding meaning separately for each report or relying only on warehouse schemas.

Model collaboration has distinct supported arrangements. Permission-based sharing gives users defined access levels but permits one developer at a time to work on the model. Git-based sharing follows a different path, and the documentation specifies how those choices interact. This is a useful operational distinction: a permission to edit does not, by itself, imply simultaneous collaborative development or the same lifecycle as version-controlled model work.

Tier II reflects deep semantic capability and practical governance documentation. Oracle Analytics Cloud suits enterprises connecting managed model development with recurring analytical consumption. Evaluation should use the intended sharing arrangement, exercise a model revision and verify dependent workbooks, ensuring that the development process fits the team's actual review and release responsibilities.

Pyramid Analytics

• Provider / operator: Pyramid Analytics / ServiceNow
• Pyramid corporate base: Amsterdam, Netherlands
• Pyramid business origins: 2008 (company-declared business origins)

Pyramid Analytics brings together modeling, data preparation and business-facing analysis within a unified platform. ServiceNow completed its acquisition on March 10, 2026, and the profile identifies that current ownership while retaining the product's analytical identity. Its inclusion is grounded in a maintained decision-support platform, rather than an expectation that future integration announcements already represent delivered functionality across another vendor's entire portfolio.

Technical documentation explains how semantic relationships connect tables for analytical use. It distinguishes those relationships from joins used in an ETL data flow and from changes to a source database's physical schema. That distinction is consequential: the logical model instructs analysis without necessarily rewriting the original database. Users and administrators need to understand which layer owns the meaning of a relationship and its resulting calculations.

Tier II reflects broad analytical scope with substantial model-oriented depth. Pyramid is relevant when preparation, semantics and consumption must form a coherent workflow. Evaluation should follow a realistic relationship change through analysis and governed distribution, separating documented current provision from prospective capabilities associated with its new parent.

SAP Analytics Cloud

• Provider / operator: SAP
• Provider headquarters: Walldorf, Germany
• Provider origins: 1972

SAP Analytics Cloud combines analytical stories with planning-oriented models and decision-support workflows. Its appeal extends beyond viewing historical results: organizations can connect analysis with controlled versions, input and business planning. That breadth makes the platform relevant to enterprise teams that need consistent analytical presentation and governed participation in planning, while keeping the evaluated product distinct from SAP's wider data and application portfolio.

Data Access Control can set read and write rights for individual dimension members. Planning versions and data locking add further operating controls. The documented privilege hierarchy matters: roles with full data access can override dimension-level restrictions. A sound implementation therefore considers role assignments, model policy and member permissions together rather than relying on one filter as a universal safeguard.

Tier II reflects substantial analytical and planning provision supported by practical administration guidance. The strongest evaluation uses an actual planning cycle, with different contributors, reviewers and privileged administrators. This reveals whether the modeled business process, version controls and effective permissions work together when users move from consuming a story to updating governed planning information.

SAS Visual Analytics

• Provider / operator: SAS
• Provider headquarters: Cary, North Carolina, United States
• Provider origins: 1976

SAS Visual Analytics supplies visual reporting and analytical applications within the SAS software environment. It is relevant where exploratory analysis and governed report delivery need to connect with established enterprise analytical workflows. The comparison evaluates the named product, while recognizing that current Viya services and an older supported Visual Analytics installation can differ materially in architecture and administration.

Current developer references expose report operations through APIs. Versioned administration manuals provide a separate, detailed account of authorization in the documented edition, including metadata-based rights over reports, tables and other objects. The Visual Analytics 7.5 guide's security limits are kept specific to that version; they are not generalized into a claim about every current Viya deployment or all SAS analytical products.

Tier II recognizes substantial analytical depth, administration and programmatic integration. The appropriate evaluation begins with an exact deployment and release, then tests report creation, access and consumer delivery in that environment. This avoids comparing a current cloud API demonstration with the governance assumptions of a different installed edition while still acknowledging the product's supported enterprise analytical breadth.

Sisense

• Provider / operator: Sisense
• Company-declared headquarters: New York, New York, United States
• Provider origins: 2004

Sisense provides data modeling and dashboards with a pronounced emphasis on embedding analytics into applications. This makes it relevant both to internal business intelligence and to software teams delivering analysis as part of a customer-facing product. The assessment focuses on the maintained analytical platform and its integration capabilities, rather than assuming that embedded presentation alone establishes effective data governance.

Model permissions distinguish editing, creating dashboards and viewing existing analytical content. Current guidance also describes ownership consequences when model access changes. Administrators and data administrators retain access to models even when ordinary designers face restrictions, so that exception must be included in a realistic permissions design. Embedding documentation connects these model and consumer arrangements with the surrounding application implementation.

Tier II recognizes deep application integration and substantial analytical governance. Sisense is a strong candidate when analytics must become part of another product's user experience. Teams should evaluate the complete path from model ownership to embedded consumer identity, including a change in author access, so that dashboards remain maintainable without exposing capabilities intended only for platform administrators.

Strategy One

• Provider / operator: Strategy
• Company-declared headquarters: Tysons Corner, Virginia, United States
• Provider origins: 1989

Strategy One places a shared semantic layer at the center of its business intelligence and analytics offering. Business terms, metrics and relationships provide a reusable foundation for analysis rather than being defined repeatedly in independent reports. That emphasis suits enterprises seeking a consistent analytical vocabulary across teams, especially where established content must remain understandable as sources and business structures evolve.

Current product material describes governance and the extension of semantic definitions into other analytical tools through the wider Strategy portfolio. The comparison retains one Strategy One placement rather than treating an adjacent semantic product as a separate provider. The reviewed evidence establishes the maintained platform and its intended integration model; it does not convert broad claims about trust or speed into independently measured comparative results.

Tier II recognizes substantial semantic capability and enterprise analytical integration. A useful evaluation follows the same business measure through authoring, shared definitions and multiple consumers. Organizations should also examine how changes are reviewed and distributed, because semantic centralization is valuable only when the actual operating process keeps those definitions consistent and accessible.

ThoughtSpot

• Provider / operator: ThoughtSpot
• Company-declared headquarters: Mountain View, California, United States
• Provider origins: 2012

ThoughtSpot emphasizes search-oriented exploration and reusable analytical content through Models, Answers and Liveboards. Its appeal is the connection between business questions and maintained analytical structures that users can revisit and share. Mode is consolidated within the same provider group for this comparison, preserving one placement rather than counting an acquired product as a separate corporate competitor.

Current documentation describes row-level rules for users and groups across searches, Answers and Liveboard interactions. It also identifies exceptions, including the treatment of string values in custom sort orders. Release material distinguishes available functions from coming-soon changes. These details matter when evaluating a search-driven interface: familiar question wording does not remove the need to understand the model, permitted data and feature stage beneath it.

Tier II recognizes substantial exploration capability with inspectable governance and product maintenance. ThoughtSpot suits organizations that want business users to ask follow-up questions within a controlled analytical environment. A pilot should compare authorized users asking the same question and verify how shared answers behave after a model or access rule changes.

---

Tier III — Specialist Business Intelligence & Analytics Platforms

(Alphabetical order)

Amazon Quick Sight

• Provider / operator: Amazon Web Services
• Headquarters: Seattle, Washington, United States
• Provider origins: 2006 (AWS cloud business)

Amazon Quick Sight is the current business intelligence offering within Amazon Quick. This profile keeps the scope on dashboards, datasets and analytical consumption, rather than importing unrelated research or automation capabilities from the wider suite. It is relevant to organizations seeking managed BI and to application teams embedding analytical content for different categories of users.

Row-level security can apply user- or group-based dataset rules, while embedded sessions can use tags to restrict data for unregistered application consumers. The documented functionality has Enterprise Edition scope. Dataset owners can still see the complete data when a restricted dataset is shared with them, making ownership a privileged operating role rather than another ordinary reader assignment.

Tier III reflects a substantial analytical delivery platform with clear embedding and access-control documentation. A useful pilot compares a dataset owner, a registered reader and a tagged embedded session. That demonstrates whether the chosen configuration produces the intended analytical boundaries and avoids treating the wider Amazon Quick brand as a substitute for product-specific BI validation.

Bold BI

• Provider / operator: Syncfusion
• Provider office / company base: Morrisville, North Carolina, United States
• Provider origins: 2001

Bold BI provides dashboards and data-source management for embedded business intelligence. It supports live connections and extracted data, giving application teams different ways to connect analytical presentation with operational sources. The product belongs here because maintained modeling, dashboard and integration functions form an actual analytical offering, rather than a consultancy producing isolated reports or a visualization component without a surrounding platform.

Source administration includes sharing, version history and file logs. The documentation distinguishes extraction through the Bold BI engine from a Data Hub arrangement, while user filters and embedded row-level settings provide control over presented data. Those choices affect freshness, storage and access, so connection type and authorization should be designed together rather than treated as separate implementation details.

Tier III recognizes a coherent embedded analytics platform with useful operational specificity. Bold BI fits teams seeking configurable analytical delivery inside an application. Evaluation should revise a data source, inspect its history and test restricted consumers through the actual embedding path, confirming that data refresh and security behave consistently with the selected connection arrangement.

Domo

• Provider / operator: Domo
• Company-declared headquarters: American Fork, Utah, United States
• Provider origins: 2010

Domo combines dashboards, data preparation and analytical application workflows within a broad business intelligence platform. That connected scope is useful where teams need to bring information into a maintained environment and distribute analysis to different business audiences. The assessment focuses on documented analytical provision, rather than adopting claims about productivity, adoption or business outcomes from the provider's wider product positioning.

Personalized Data Permissions establish configurable access at the DataSet level. Row policies limit which records users or groups can interact with, while column policies and masking address sensitive fields. These settings affect analytical consumption through cards and relevant data workflows. Their value depends on correctly designed policies and group membership, particularly when the same prepared information supports several audiences with different responsibilities.

Tier III recognizes broad functional scope and useful controlled-distribution mechanisms. Domo is relevant when preparation, visualization and application delivery need to connect in one operating environment. An evaluation should follow a sensitive dataset through those stages and test how each consumer's effective permissions affect the resulting analytical experience.

Hex

• Provider / operator: Hex
• Company-declared headquarters: San Francisco, California, United States
• Provider origins: 2019

Hex connects analytical projects with reports, dashboards and interactive data applications. Authors can curate selected project cells into an app while retaining the underlying analytical context. That makes it relevant where data practitioners need to turn code-backed investigation into a usable business experience, rather than manually rebuilding the result in an unrelated presentation tool or exposing an entire working project to every consumer.

Publication and access are separate actions. The documentation explains how an app is assembled and published, while project permissions can grant a recipient access only to the published application. This distinction is operationally useful: an author can maintain analytical work without automatically making all development surfaces available to the audience consuming the final result.

Tier III reflects a focused bridge between analytical development and business-facing delivery. Hex suits teams that need flexible analysis and curated applications to coexist. Evaluation should revise a project, publish the intended view and test consumer access independently, ensuring that the development process supports a dependable audience experience without broadening permissions beyond what the application requires.

Lightdash

• Provider / operator: Lightdash
• Provider base: London, United Kingdom
• Provider origins: 2020 (provider origins; originally Hubble)

Lightdash connects business intelligence with dbt-defined dimensions and metrics. Definitions live alongside the data team's existing model properties, giving self-service analysis a reusable semantic foundation. Its strongest fit is an organization that wants analytical authoring to participate in established engineering workflows, with business users exploring prepared metrics instead of creating a competing calculation layer in every dashboard.

Content validation identifies charts, dashboards and deliveries broken by changes to metrics or dimensions. The documented workflow can run after a dbt refresh, a CLI deployment or an explicit validation request. This connects model evolution with visible analytical consequences. Role-aware access and project administration remain separate responsibilities; finding broken content is useful maintenance evidence, not proof that the underlying business definition or access policy is correct.

Tier III recognizes a technically coherent, engineering-oriented analytical platform. The next step for an evaluator is to change a shared metric, deploy it and inspect affected content under real user permissions. Lightdash's documented validation path is particularly useful for teams that need frequent model changes to remain manageable across an expanding self-service reporting estate.

Logi Symphony

• Provider / operator: insightsoftware
• Provider headquarters: Raleigh, North Carolina, United States
• Provider origins: 2018 (current provider group formation)

Logi Symphony brings embedded dashboards, reporting and data preparation into an application-oriented analytical offering. Dundas BI is now positioned within the Symphony portfolio and is consolidated here rather than counted again as an independent provider. The evaluation therefore follows the maintained named product and current insightsoftware ownership, preserving continuity without multiplying placements through acquired brands.

Versioned product documentation establishes the platform's current scope, while official materials describe white-label and embedded scenarios. These are substantive uses for teams incorporating analysis into their own applications. The surrounding deployment still needs explicit choices about users, data access and operational ownership; the ability to customize analytical presentation is distinct from verifying every permission or lifecycle requirement of the host product.

Tier III recognizes a broad embedded analytics offering with an identifiable current product boundary. It is relevant where product teams need reporting and interactive analysis to form part of a larger application. Evaluation should use the intended Symphony configuration and test authoring, publication and restricted consumption together, avoiding assumptions drawn from a differently packaged legacy Dundas installation.

Luzmo

• Provider / operator: Luzmo
• Company-declared headquarters: Brooklyn, New York, United States
• Provider origins: 2015

Luzmo focuses on embedding analytics into software products, with complete dashboards and individual analytical components available for application experiences. Its relevance is strongest where a product team wants to deliver maintained analysis without building every visualization and analytical interaction itself. The evaluation concerns that documented embedded platform, with application integration treated as a central technical requirement rather than an incidental sharing feature.

Authorization begins on the server, where privileged credentials are used to generate temporary embed tokens. Those tokens can restrict the resources and features available to a consumer. This provides a concrete boundary between administrative capability and end-user access. Frontend components then deliver the permitted analytical experience without requiring the application to expose the underlying privileged API credentials in a browser.

Tier III reflects substantial embedded delivery and clear developer guidance. A useful evaluation tests token expiry, resource restrictions and different user entitlements within the intended application. Luzmo is particularly relevant when those integration controls fit a product's existing identity system and the team can maintain the relationship between customer permissions and analytical resources.

Metabase

• Provider / operator: Metabase
• Company-declared headquarters: Spring Valley, California, United States
• Provider origins: 2014

Metabase provides questions, dashboards and self-service exploration over connected data. It is relevant to organizations that want a coherent business intelligence experience and to software teams incorporating analytical consumption into another application. The evaluated unit is the maintained platform, with its embedding and permission design treated as substantive operating capabilities rather than assuming an open-source label alone establishes deployment simplicity.

Embedding documentation distinguishes commingled customer data from separate databases and separate schemas. Different architectures lead to different permission arrangements, including row and column controls or group-based access to database connections. This is useful implementation evidence because tenant separation depends on how data is actually stored. A single convenient embedding method is not automatically the right security model for every customer architecture.

Tier III reflects accessible analysis supported by unusually practical integration guidance. Evaluation should use the intended data layout, register representative consumer identities and test cross-tenant restrictions. The strongest fit is a team that values the platform's analytical workflow while explicitly matching its permissions and embedding arrangement to the surrounding application.

Omni

• Provider / operator: Omni
• Principal regional hub / company base: San Francisco, California, United States
• Provider origins: 2022

Omni combines shared analytical models, topics and workbooks to support governed exploration. Its model-extension approach is relevant to organizations balancing common definitions with the needs of distributed teams. Rather than forcing every group into an identical authoring environment, the documented pattern allows related models to share upstream logic while supporting differentiated analytical work and consumer visibility.

That flexibility has explicit governance implications. Editors of an extension can override upstream logic, including data-access policies, so central definitions are not automatically immutable controls. Visibility is also model-aware: a workbook containing topics with different permissions can show some charts and errors for others. Git integration and document APIs provide development and administration paths, but the modeling pattern still requires deliberate access design.

Tier III recognizes strong semantic and integration provision with an instructive account of deployment trade-offs. Omni fits teams that can manage distributed analytical ownership carefully. Evaluation should test an extension change and a mixed-permission workbook, confirming how the chosen governance process preserves shared meaning while allowing useful local analysis.

Phocas

• Provider / operator: Phocas
• Current UK provider office: Coventry, United Kingdom
• Provider origins: 2001

Phocas provides analytical grids and dashboards over business data, with a particular relevance to teams using operational information to investigate performance. The product's maintained analysis and distribution workflows establish eligibility; it is not included as a consultancy preparing one-off commercial reports. The fact box uses an explicitly labeled current UK office and distinguishes the provider's business origins from the launch of an individual module.

Administration separates functional permissions from underlying database access. A user may have permission to open dashboards yet see no data if the associated database is unavailable to them. Collaboration rights govern sharing, while query permissions control actions in the analytical grid. This makes the effective consumer experience a combination of several decisions rather than a single dashboard-view entitlement.

Tier III recognizes a coherent platform for business analysis with practical permission guidance. Phocas fits organizations that want users to move from a summary view into the underlying analytical detail. A useful evaluation follows that transition under several roles, confirming that the intended freedom to explore is supported by appropriate database and functional permissions.

Preset

• Provider / operator: Preset
• Company-declared headquarters: San Mateo, California, United States
• Provider origins: 2019

Preset provides a managed analytical service built around Apache Superset, with exploration and dashboards delivered through maintained cloud workspaces. Its eligibility follows from the actual operated platform and its documented analytical workflows, rather than treating the open-source project and commercial provider as interchangeable entities. The fact box identifies Preset's corporate origins separately from Superset's earlier technical lineage.

Embedding places a workspace-hosted dashboard inside another application. Current guidance describes domain restrictions and row-level rules as parts of the access design. It also identifies embedding as an add-on for specified plans, so a trial or commercial configuration must be matched to the functionality actually intended for production. Availability in an example does not remove those product and administrative boundaries.

Tier III recognizes a coherent managed analytics offering with practical application integration. Preset fits teams that value the Superset analytical model while preferring an operated service. Evaluation should include authoring, publication and restricted embedded consumption, establishing how workspace administration and application identity combine to protect the data presented to each audience.

Reveal

• Provider / operator: Infragistics
• Provider office / company base: Cranbury, New Jersey, United States
• Provider origins: 1989

Reveal supplies an embedded analytics toolkit for integrating interactive dashboards and visual exploration into applications. Its documented SDKs and APIs make it relevant to product teams that need analytical functions within an existing software experience. The evaluated offering is the maintained embedded platform from Infragistics, with its newer AI interfaces considered separately from the established dashboard and integration foundation.

Current help material provides implementation examples, data-source guidance and customization paths. Security and trust references describe the surrounding integration context, making application-side responsibilities material to the assessment. A visual component does not determine the identity or data entitlements of its eventual consumer; those decisions must be carried through the embedding architecture and the resources supplied to the analytical interface.

Tier III reflects particularly strong application integration with a focused analytical scope. Reveal fits organizations with development capacity to manage the surrounding product experience. A useful pilot exercises the actual framework, data connections and consumer identities, checking that customization preserves the intended controls and that newer AI demonstrations do not obscure the requirements of dependable core analytics.

Toucan

• Provider / operator: Toucan
• Company-declared headquarters: Boston, Massachusetts, United States
• Provider origins: 2015

Toucan emphasizes story-oriented analytical experiences embedded within applications. Its workflow separates technical modeling and integration from the construction of user-facing dashboards and stories. That makes it relevant where product teams want to give consumers a guided analytical experience, with deliberate context and presentation rather than an unrestricted authoring surface or a collection of disconnected visual components.

The documentation describes a complete embedding workflow and customization of the resulting stories. This establishes an actual reusable analytical offering, while leaving the surrounding application responsible for fitting integration and access to its users. Claims that an audience needs no training are not treated as measured evidence; the suitability of the presentation depends on the questions, data and decisions it is intended to support.

Tier III reflects a focused approach to analytical consumption and application integration. Toucan is most relevant when a guided experience fits the requirement. Evaluation should ask representative users to follow an actual decision workflow, checking both comprehension and authorized data access rather than equating an attractive story layout with dependable analysis.

Yellowfin

• Provider / operator: Yellowfin / Idera
• Yellowfin business base: Melbourne, Victoria, Australia
• Provider origins: 2003 (Yellowfin business origins)

Yellowfin combines dashboards, linked reports and interactive exploration within a web-based analytical platform. It is relevant where organizations want consumers to move between related views and investigate information rather than receive static reports alone. The profile identifies Yellowfin's business lineage within Idera ownership, with one placement for the maintained offering and no separate slot for its wider corporate group.

Illustrated authoring guidance describes linking report filters so that related content supports coordinated analysis. A current REST API provides a separate programmatic integration path. The evidence distinguishes current API scope from older illustrated workflows, which should not be interpreted as a claim that every historical interface remains unchanged. Access filters and distribution arrangements also require configuration appropriate to the intended consumer population.

Tier III recognizes a coherent analytical platform with useful embedded and application integration. Yellowfin fits teams seeking connected reporting experiences and controlled distribution. Evaluation should follow a question across linked reports, then test the relevant filters and API access under actual user permissions, confirming that exploratory convenience remains consistent with the organization's data boundaries.

Zoho Analytics

• Provider / operator: Zoho
• Provider headquarters: Chennai, India
• Zoho provider origins: 1996

Zoho Analytics provides tables, reports, charts and dashboards in a self-service analytical environment. It is relevant to organizations seeking recurring business analysis and controlled sharing across teams, with the surrounding Zoho ecosystem offering integration context rather than an automatic reason for placement. The product's own reporting and permission workflows establish the basis of its evaluation.

Sharing can target individual users or groups, with permissions governing access to particular analytical objects and the actions available to recipients. That makes distribution a deliberate part of the operating model. A report being available online does not mean every consumer should receive the same underlying data, editing rights or ability to extend analysis into other shared resources.

Tier III recognizes a complete business intelligence product with accessible collaboration guidance. It suits teams that want analysis and distribution to remain closely connected. An evaluation should create a small set of reusable reports, share them under different rights and verify the consumer experience, ensuring that straightforward delivery also preserves ownership and appropriate boundaries as the reporting estate grows.

---

Remarks

Private criterion assessments use the published weights before selecting the five, ten and fifteen entries in each band. Scores express editorial judgment of documented capabilities. Equal totals are reviewed for relevant technical priorities, with no commercial factor; lower-band alphabetical presentation does not imply an internal ordinal ranking.

The platforms deliberately serve different needs. A developer-focused embedded toolkit, a code-defined semantic environment and a planning-oriented enterprise suite may all qualify while assigning different work to the buyer. Their placement does not make those responsibilities interchangeable or determine the most suitable option for every organization.

Evaluation should include representative questions, permission changes and analytical revisions. Ask both authors and consumers to complete actual tasks, then inspect whether the definitions and access controls remain understandable after content changes. Treat preview functions and vendor-selected productivity claims according to their documented limitations.

The profiles describe current provision at the research date. A product in a lower band can be the best fit for a particular application or operating model. Final selection should follow the required analytical workflow, governance obligations and the team responsible for maintaining the result.

---

Recognition

Inclusion in the Top 30 Business Intelligence & Analytics Platforms 2027 ranking is an editorial determination of The Economy Rankings and does not require licensing, advertising, sponsorship, or other commercial participation.

Ranked organizations may factually refer to their inclusion in the ranking in their own communications. When describing the result, entities should accurately reflect the tier structure and methodology used in the published ranking.

How the ranking should be interpreted

• Tier I represents the Top 5 entities, and the published order within Tier I reflects the ranking order.
• Tier II represents entities ranked within the Top 15, following Tier I. Entities within Tier II are displayed alphabetically; their displayed order should therefore not be interpreted as an individual numerical ranking.
• Tier III represents entities ranked within the Top 30, following Tiers I and II. Entities within Tier III are also displayed alphabetically, and their displayed order should not be interpreted as an individual numerical ranking.
• An entity's tier, rather than its alphabetical position within Tier II or Tier III, should therefore be used when describing its standing.

Referencing the ranking

Depending on the entity's published tier, appropriate factual descriptions may include:

• Tier I: “Ranked Tier I” or “Ranked among the Top 5”
• Tier II: “Ranked Tier II” or “Ranked among the Top 15”
• Tier III: “Ranked Tier III” or “Ranked among the Top 30”

Entities should not describe an alphabetical position within Tier II or Tier III as a specific numerical rank.

Use of The Economy Rankings recognition materials

Editorial inclusion in a ranking does NOT by itself grant permission to use The Economy Rankings badges, seals, logos, official recognition graphics, licensed quotations, or other proprietary recognition materials.

Organizations wishing to use official The Economy Rankings recognition materials in corporate websites, marketing materials, investor communications, client presentations, social media, press releases, or other external communications should refer to the applicable licensing terms and usage policies:

• The Economy Rankings License Structure — available licence levels and permitted recognition uses
  The Economy Rankings License Structure | The Economy Rankings
• The Economy Rankings License Policy — licensing conditions governing use of The Economy Rankings recognition, marks, and related materials
  The Economy Rankings License Policy | The Economy Rankings
• Recognition Use Guide — guidance on permitted wording, presentation, attribution, and use of ranking recognition
  Recognition Use Guide | The Economy Rankings

Purchasing or holding a recognition-materials licence does not confer inclusion or a higher tier.

Recognized organizations may reference the designation in:

• corporate websites
• investor communications
• marketing materials
• client presentations

Licensing inquiries:
[email protected]