Graphwise
Type: company (knowledge-graph and semantic-layer software vendor) Sector: Semantic technology / knowledge graphs / AI context infrastructure First seen: 2026-08-28 Last updated: 2026-08-28
Created 2026-08-28 from S-2026-08-21-solutionsreview-dm-roundup (daily vendor-intelligence scan). Adjacent to the core Data Governance watchlist: Graphwise sells the semantic/knowledge-graph layer rather than a catalogue, but that layer is where business-term meaning and critical-data-element definitions live. Ownership-change signal only — no product capability is recorded here. Primary announcement not fetched.
Snapshot
Graphwise is a European knowledge-graph and semantic-layer provider formed in 2024 by the merger of Ontotext and Semantic Web Company, positioned around grounding AI, search and analytics in “connected, governed enterprise knowledge” for regulated and data-intensive organisations [S-2026-08-21-solutionsreview-dm-roundup]. It matters to this wiki for two reasons: the semantic layer is the substrate for consistent data definitions that BCBS 239 and glossary work depend on, and — as of August 2026 — it is under new private-equity control, which is a vendor-lifecycle event of the kind tracked on Vendor Lifecycle Events as Evidence-Continuity Risk.
Positions / Claims they advance
- Positions itself as helping “regulated and data-intensive organizations ground AI, search, and analytics applications in connected, governed enterprise knowledge” [vendor/PE framing relayed by trade press — S-2026-08-21-solutionsreview-dm-roundup].
- Formed in 2024 through the merger of Ontotext and Semantic Web Company — i.e. the current entity is itself the product of a prior consolidation [S-2026-08-21-solutionsreview-dm-roundup].
- Stated post-investment priorities are international expansion, go-to-market development, and selective acquisitions [S-2026-08-21-solutionsreview-dm-roundup].
Relationships
- relates-to → Vendor Lifecycle Events as Evidence-Continuity Risk — a change of control at a supplier whose output feeds governance artefacts is precisely the event class that page tracks [inference].
- relates-to → BCBS 239 and Data Lineage — semantic/knowledge-graph layers carry the business-term and CDE definitions that BCBS 239 consistency expectations rest on [inference].
- relates-to → Operational Resilience and Third Party Risk — PE control of a European supplier bears on DORA ICT third-party risk, continuity and exit assessment [inference].
- relates-to → CLM Glossary Acceleration Squad — semantic-layer tooling is directly adjacent to glossary/taxonomy build work [inference].
Tracked changes
- 2026-08-21 (reported week of; logged 2026-08-28) — Oakley Capital acquired a majority stake in Graphwise. Investment stated to fund international expansion, go-to-market development and selective acquisitions. Deal terms, valuation and stake percentage were not disclosed in the available source, and the primary Graphwise announcement could not be fetched (WebFetch provenance restriction) [S-2026-08-21-solutionsreview-dm-roundup].
Open Questions
- What stake size and governance rights did Oakley Capital acquire, and is this a control transaction with board control or a majority economic interest only? Not disclosed.
- Does the transaction change support commitments, roadmap, pricing or data-residency guarantees for existing regulated customers? Firms using Graphwise in a governance-critical path would need this for DORA third-party assessment.
- Are Ontotext and Semantic Web Company product lines (GraphDB, PoolParty and successors) being consolidated, and is any line facing end-of-life? A “selective acquisitions” strategy under PE ownership often precedes portfolio rationalisation [inference — no source].
- Does Graphwise have named EU/UK regulated-FS customers? None surfaced in this source.
- How, if at all, does Graphwise’s positioning intersect with the “governing semantic model above the platforms” argument that Collibra advances [S-2026-08-10-collibra-banking-readiness-gap]? Both claim the layer above platform-specific semantics — potentially a competitive overlap, but no source compares them.