Pre-launch preview. Pauhu® Ltd is building toward launch. Explore the foundation and register your interest; subscriptions are not open yet.
Pauhu

Datasets

The foundation, in detail.

Pauhu®'s corpus aligns structurally with the Common European Data Spaces framework, sourced row by row across fourteen domains in twenty-four European languages. An approved provider to the European Language Data Space since 8 July 2025, registry ID 66. Live DCAT3 catalog. Helsinki, EU jurisdiction. VAT FI07681718.

CredentialVerify at
European Language Data SpaceApproved participant, registry ID 66, since 8 July 2025: language-data-space.eu/catalogue/list-of-participants
Common European Data Spaces frameworkEuropean Commission strategy: digital-strategy.ec.europa.eu/en/policies/data-spaces
Pauhu® DCAT3 catalogLive: api.pauhu.eu/v1/lds/_catalog

The foundation

One corpus. Fourteen domains. More than eleven million sourced rows. Twenty-four European languages.

Pauhu®'s corpus is one cited foundation, structurally aligned with the Common European Data Spaces framework. Each access path is designed around the same catalog; per-domain row counts show what is live and what is still filling.

The corpus spans the fourteen sectoral domains named in the European Commission's 2022 strategy.

Coverage today

DomainCoverage areaRows, approx. launch-time
AgricultureCommon European Agriculture Data Space (CAEDS)90,500
Cultural HeritageCommon European Cultural Heritage Data Space129,500
EnergyCommon European Energy Data Space (CEEDS)367,000
FinanceCommon European Finance Data Space778,000
Green DealCommon European Green Deal Data Space (GDDS)456,000
HealthEuropean Health Data Space (EHDS), Regulation (EU) 2025/327, two-axis filter applied10,000
LanguageCommon European Language Data Space7,082,000
ManufacturingCommon European Manufacturing Data Space71,000
MediaCommon European Media Data Space1,700
MobilityCommon European Mobility Data Space551,000
Public AdministrationCommon European Public Administration Data Space1,771,000
Research and InnovationCommon European Research and Innovation Data Space, EOSC-adjacent260,000
SkillsCommon European Skills Data Space91,000
TourismCommon European Tourism Data Space2,400

Where the foundation is dense, Pauhu® returns sourced answers row by row, with source URL, paragraph-precise identifier, and timestamp. Where it is still filling, Pauhu® returns an honest gap that names what would close it. Both behaviours are the product. Row counts above are launch-time. Live counts resolve at each domain's API URL inside the catalog.

Where Pauhu® fits

Where Pauhu® fits.

The European Commission's strategy names the Common European Data Spaces as the framework for sharing sector-specific data across Europe. The European Language Data Space was the first sectoral pilot. Pauhu® is listed in its registry, ID 66.

The Commission states the shared mission in its own words: "empower the Multilingual Digital Single Market while preserving Europe's language diversity through digital means" and "advance Europe's digital autonomy and technical sovereignty" (DG CNECT). Pauhu® has been building the foundation in production since 2023. Today the foundation is approved as an LDS provider, listed in the registry, and live.

Verify

Verify the foundation.

ClaimVerify at
Approved participant in the European Language Data Space, LDS Governance Board, 8 July 2025, registry ID 66language-data-space.eu/catalogue/list-of-participants
Common European Data Spaces framework, European Commission strategydigital-strategy.ec.europa.eu/en/policies/data-spaces
EHDS regulatory framework, Health domainRegulation (EU) 2025/327, Official Journal of the European Union
Public DCAT3 catalog, open discovery across all fourteen domainsapi.pauhu.eu/v1/lds/_catalog
Per-domain data envelope, example path (access required), Energyapi.pauhu.eu/v1/lds/pauhu-energy
Per-domain rows, example path (access required), Energyapi.pauhu.eu/v1/lds/pauhu-energy/rows?limit=5

Licensing

Licensing.

Pick the data spaces you need, per seat. Every plan delivers the same foundation through MCP, REST, and the structured stream.