Huwise

Name: Huwise
Brand: Huwise
Rating: 4.8 (29 reviews)

The leading data product marketplace unlocking data value for business users.

Est 2011|Valuation $46.2M|Raised $35.7M

LinkedIn 12K|Website|Web traffic 16K|FTEs 100|HQ Paris, Île-de-France, FR

MarketsData Catalog

Published Sep 26, 2026

01Common complaints

- When the primary need is a governance control plane with deep stewardship workflows and comprehensive lineage functionality; governance incumbents may be a better fit. - When an organization is fully committed to a single cloud data platform (for example, Snowflake) and requires native monetization/listing mechanics deeply integrated with that cloud provider; native marketplace solutions may be more appropriate. - When advanced, cross-dataset dashboarding and complex analytics modeling are the primary requirements; separate BI and analytics platforms may better meet those needs. - When transparent, predictable, self-serve pricing is a strict procurement requirement and contract negotiation is not feasible.

Deal disqualifiers (poor fit)

Requirement that the platform’s built-in visualization replace a full BI platform
Need for transparent, self-serve pricing with predictable scaling without contract negotiation
Lack of internal front-end capability combined with a requirement for a highly tailored portal UX

Current limitations acknowledged by customers

Reviewers report limitations in the built-in visualization studio for advanced use cases
Some reviewers report that combining multiple datasets in a single visualization is not supported or is difficult
Advanced UX customization can require CSS/HTML skills

Vendor-acknowledged limitations / roadmap signals

Historical vendor communications reference API transitions and security upgrades; buyers should verify current API behavior and deprecation schedules directly with the vendor.

Security/compliance gaps (public info)

The vendor describes a security policy aligned with ISO 27001/27002 practices, but no public statement of ISO 27001 certification or SOC 2 attestation was located in the materials accessed. Prospective buyers should request formal compliance artifacts and recent third-party assessment reports.

Use cases where it struggles / isn’t ideal

Advanced visualization requirements spanning multiple datasets and complex modeling
Heavy custom UX where the organization lacks web development capability

02Why they buy

Unique selling points supported by customer feedback (not just vendor claims)

Ability to centralize and publish heterogeneous data sources and reduce time to provision and publish datasets, according to reviewer excerpts.
SaaS hosting model that abstracts hosting, monitoring, and maintenance responsibilities from the customer in certain deployment patterns.

Differentiation likely vs competitors

The platform aligns with organizations seeking a portal-like marketplace experience that supports public and internal audiences and focuses on discoverability and API-driven reuse rather than only metadata governance.

Areas where competitors have clear advantages

Cost transparency and native billing models available from some cloud data platforms
Advanced analytics and BI capabilities offered by dedicated analytics platforms
More mature governance and stewardship tooling offered by incumbent governance platforms

03Field reports

Review platform availability and limitations

Listings and review excerpts are available on major review platforms; however, some full review texts are gated and not fully accessible without account access. Platform presence includes Gartner Peer Insights and G2; TrustRadius presence was not clearly documented in the sources accessed.

Gartner Peer Insights — examples

Example reviewer comment (paraphrased): a reviewer cited the product as "very complete" and noted easy onboarding and connector-based ingestion. The available sample of Gartner reviews is directionally positive but not comprehensive based on the accessible excerpts.

G2 — examples (positive and critical)

G2 reviews include a mix of positive and critical feedback. Examples drawn from accessible review excerpts include: - Positive: reviewers cite time savings from centralization and publication of heterogeneous sources. - Pricing criticism: some reviewers report price increases and describe the pricing model as complex and difficult to forecast. - Feature limitations: reviewers have described the no-code visualization tool as limited for advanced visualization needs and note specific constraints such as combining multiple datasets in a single visualization. - Customization learning curve: reviewers note advanced UX or complex portal use cases may require web design skills (CSS/HTML).

Why customers select the platform (patterns)

Recurring selection drivers in accessible materials include:

Integrated capabilities for publishing and sharing, including API exposure
Support for both public and restricted access modes
Reduced dependence on centralized IT for basic publishing workflows, enabling business teams to manage certain publishing tasks

Why some customers might leave (inferred from complaints)

Churn risk factors suggested by reviewer feedback include:

Pricing increases or complex pricing models affecting budget predictability
Limitations in the platform’s built-in visualization capabilities if BI-level dashboards are required
Requirements for front-end development skills to deliver advanced, tailored portal experiences

Town of Cary (Smart community / data portal)

A vendor-authored success story indicates a Town of Cary deployment that went live in 2016. Critical evaluation: - This is vendor-authored content and may present selective outcomes. - The publicly available excerpt does not include independently verified KPIs (e.g., adoption metrics, request-volume reductions, or time-savings). Buyers should request portal usage analytics, operational cost comparisons, and dataset publishing cycle time metrics from the vendor or references.

Smart Cities program participation (accelerator membership)

Huwise has publicly noted participation in a smart cities accelerator program and references a set of city and enterprise customers.

Critical evaluation:

Accelerator participation indicates ecosystem engagement but is not an objective measure of product performance.
Reference customer lists are useful for validation calls, but deployment scope and outcomes require further verification.

Vendor-published satisfaction survey

A vendor-published satisfaction survey is available in promotional materials; methodological details such as sample size, response rate, and segmentation were not included in the accessible excerpt. Treat vendor-published satisfaction claims as directional and triangulate with independent reviews.

04Best fit

Company sizes

Observed uses include public sector bodies and mid-market to enterprise organizations; reviewer categories range from mid-market to enterprise.

Industries / verticals

Strong use-case evidence is present for:

Government / municipalities / smart cities
Utilities and energy networks
Transportation and public policy analytics

Roles and personas

Common buyer and user roles include:

Chief Data Officer and data leadership
Business analysts and product owners responsible for data products
IT and security teams responsible for governance and access control
Open data managers and public sector data administrators

Qualification criteria (good fit)

Requirement for a branded portal for broad discovery and distribution (public and/or internal)
Need to publish APIs and data exports with governance controls
Desire to consolidate distributed datasets for discovery and reuse across departments

05The pitch

What the product does (objective value proposition)

Huwise is a data product marketplace (formerly Opendatasoft) that enables organizations to centralize, govern, publish, and share data products to internal and external audiences. The platform combines capabilities commonly expected in a data marketplace and portal stack, such as: - Data ingestion/connection to heterogeneous sources - Cataloging and metadata management with search - Publishing portals for public and controlled-access distribution - API publishing and reuse - Visualization and dashboarding with no-code tooling and options for customization Vendor materials describe a marketplace approach intended to support self-service discovery and distribution across business teams, IT, and data leaders.

Target market and market positioning

Huwise is frequently used for: - Public sector and smart cities / open data programs - Enterprises seeking to operationalize internal data sharing and publish data products (data mesh‑adjacent initiatives) Positioning sits between traditional open data portal vendors, enterprise data catalog/governance platforms, and data marketplace/exchange platforms that focus on monetization and cross-organization distribution. Huwise is also available through cloud marketplaces, indicating procurement commonly follows an enterprise contract motion rather than a purely self-serve SaaS model.

Get a comprehensive analysis of Huwise including market position, competitive landscape, adoption trends, and peer benchmarks.

Download full report →

Published Sep 26, 2026

01Common complaints

When the primary need is a governance control plane with deep stewardship workflows and comprehensive lineage functionality; governance incumbents may be a better fit.
When an organization is fully committed to a single cloud data platform (for example, Snowflake) and requires native monetization/listing mechanics deeply integrated with that cloud provider; native marketplace solutions may be more appropriate.
When advanced, cross-dataset dashboarding and complex analytics modeling are the primary requirements; separate BI and analytics platforms may better meet those needs.
When transparent, predictable, self-serve pricing is a strict procurement requirement and contract negotiation is not feasible.

Deal disqualifiers (poor fit)

Requirement that the platform’s built-in visualization replace a full BI platform
Need for transparent, self-serve pricing with predictable scaling without contract negotiation
Lack of internal front-end capability combined with a requirement for a highly tailored portal UX

Current limitations acknowledged by customers

Reviewers report limitations in the built-in visualization studio for advanced use cases
Some reviewers report that combining multiple datasets in a single visualization is not supported or is difficult
Advanced UX customization can require CSS/HTML skills

Vendor-acknowledged limitations / roadmap signals

Historical vendor communications reference API transitions and security upgrades; buyers should verify current API behavior and deprecation schedules directly with the vendor.

Security/compliance gaps (public info)

The vendor describes a security policy aligned with ISO 27001/27002 practices, but no public statement of ISO 27001 certification or SOC 2 attestation was located in the materials accessed. Prospective buyers should request formal compliance artifacts and recent third-party assessment reports.

Use cases where it struggles / isn’t ideal

Advanced visualization requirements spanning multiple datasets and complex modeling
Heavy custom UX where the organization lacks web development capability

02Why they buy

Unique selling points supported by customer feedback (not just vendor claims)

Ability to centralize and publish heterogeneous data sources and reduce time to provision and publish datasets, according to reviewer excerpts.
SaaS hosting model that abstracts hosting, monitoring, and maintenance responsibilities from the customer in certain deployment patterns.

Differentiation likely vs competitors

The platform aligns with organizations seeking a portal-like marketplace experience that supports public and internal audiences and focuses on discoverability and API-driven reuse rather than only metadata governance.

Areas where competitors have clear advantages

Cost transparency and native billing models available from some cloud data platforms
Advanced analytics and BI capabilities offered by dedicated analytics platforms
More mature governance and stewardship tooling offered by incumbent governance platforms

03Field reports

Review platform availability and limitations

Gartner Peer Insights — examples

G2 — examples (positive and critical)

G2 reviews include a mix of positive and critical feedback. Examples drawn from accessible review excerpts include:

Positive: reviewers cite time savings from centralization and publication of heterogeneous sources.
Pricing criticism: some reviewers report price increases and describe the pricing model as complex and difficult to forecast.
Feature limitations: reviewers have described the no-code visualization tool as limited for advanced visualization needs and note specific constraints such as combining multiple datasets in a single visualization.
Customization learning curve: reviewers note advanced UX or complex portal use cases may require web design skills (CSS/HTML).

Why customers select the platform (patterns)

Recurring selection drivers in accessible materials include:

Integrated capabilities for publishing and sharing, including API exposure
Support for both public and restricted access modes
Reduced dependence on centralized IT for basic publishing workflows, enabling business teams to manage certain publishing tasks

Why some customers might leave (inferred from complaints)

Churn risk factors suggested by reviewer feedback include:

Pricing increases or complex pricing models affecting budget predictability
Limitations in the platform’s built-in visualization capabilities if BI-level dashboards are required
Requirements for front-end development skills to deliver advanced, tailored portal experiences

Town of Cary (Smart community / data portal)

A vendor-authored success story indicates a Town of Cary deployment that went live in 2016.

Critical evaluation:

This is vendor-authored content and may present selective outcomes.
The publicly available excerpt does not include independently verified KPIs (e.g., adoption metrics, request-volume reductions, or time-savings). Buyers should request portal usage analytics, operational cost comparisons, and dataset publishing cycle time metrics from the vendor or references.

Smart Cities program participation (accelerator membership)

Huwise has publicly noted participation in a smart cities accelerator program and references a set of city and enterprise customers.

Critical evaluation:

Accelerator participation indicates ecosystem engagement but is not an objective measure of product performance.
Reference customer lists are useful for validation calls, but deployment scope and outcomes require further verification.

Vendor-published satisfaction survey

04Best fit

Company sizes

Observed uses include public sector bodies and mid-market to enterprise organizations; reviewer categories range from mid-market to enterprise.

Industries / verticals

Strong use-case evidence is present for:

Government / municipalities / smart cities
Utilities and energy networks
Transportation and public policy analytics

Roles and personas

Common buyer and user roles include:

Chief Data Officer and data leadership
Business analysts and product owners responsible for data products
IT and security teams responsible for governance and access control
Open data managers and public sector data administrators

Qualification criteria (good fit)

Requirement for a branded portal for broad discovery and distribution (public and/or internal)
Need to publish APIs and data exports with governance controls
Desire to consolidate distributed datasets for discovery and reuse across departments

05The pitch

What the product does (objective value proposition)

Data ingestion/connection to heterogeneous sources
Cataloging and metadata management with search
Publishing portals for public and controlled-access distribution
API publishing and reuse
Visualization and dashboarding with no-code tooling and options for customization

Vendor materials describe a marketplace approach intended to support self-service discovery and distribution across business teams, IT, and data leaders.

Target market and market positioning

Huwise is frequently used for:

Public sector and smart cities / open data programs
Enterprises seeking to operationalize internal data sharing and publish data products (data mesh‑adjacent initiatives)

Positioning sits between traditional open data portal vendors, enterprise data catalog/governance platforms, and data marketplace/exchange platforms that focus on monetization and cross-organization distribution. Huwise is also available through cloud marketplaces, indicating procurement commonly follows an enterprise contract motion rather than a purely self-serve SaaS model.

Get a comprehensive analysis of Huwise including market position, competitive landscape, adoption trends, and peer benchmarks.

Download full report →