Get a demo

All use cases

Enterprise knowledge

Know what's current, and who says so

Policies and processes sprawl across tools until no one can tell which copy is current or who owns it. In NeoWiki, a policy's text sits beside its owner, status and review date, which your teams set in forms. You can list what is overdue or unowned, and your AI can read the same records.

Retention policystatus approvedreviewed Mar 2026LegalCustomer recordsowned byapplies toauditsRetention policystatus approvedreviewed Mar 2026LegalCustomer recordsowned byapplies toaudits

See each policy's owner, status and review date ​

Each policy, process or system gets a record with the fields you choose: an owner that links to a person or team, a status from a fixed list, a review date. Your teams fill it in through a form, with no syntax to learn and mistakes flagged as they edit. Scripts can load what you already have through the REST API.

Ask what is overdue, and what depends on what ​

Ask the questions an auditor or an agent would: every policy not reviewed in a year, every process without an owner, every system that depends on one you are retiring. Query in Cypher on Neo4j, or in SPARQL on any SPARQL 1.1 store, such as QLever, Oxigraph, or Fuseki. Answers come from the current records, and a template can list them on any page. You can query each page's last editor and edit date without adding a field.

Control who reads and edits, and see every change ​

You set who can read and edit each page. Every change is versioned and attributed: you can see who changed what, compare any two versions, and watch a page for changes. Add sign-off where you need it; then query what awaits approval, and who approved the rest and when.

Bring your own AI ​

Assistants answer fluently from whatever they find, including a policy superseded last quarter or an owner who left. Connect yours through the MediaWiki MCP server instead: it can read your records and schemas, run Cypher queries, and check an edit against the schema before saving it. What it retrieves carries each record's owner, status and review date, and its edits are validated and attributed like anyone else's.

Open source, and yours to run ​

NeoWiki is an open-source MediaWiki extension, licensed under the GPL. Host it yourself, or let Professional Wiki run it. Your knowledge exports as RDF, JSON or MediaWiki XML, so you can always leave.

Chosen by the team behind BlueSpice ​

Hallo Welt!, maker of BlueSpice, the leading commercial MediaWiki distribution, chose NeoWiki as the structured-data layer of BlueSpice Galaxy, the next major version, and funds the integration. They build enterprise knowledge tooling for a living. Running Semantic MediaWiki today? Compare it with NeoWiki.

Where NeoWiki is going ​

  • More property types, such as locations and files.
  • Richer query results on wiki pages.
  • A way to find every record that breaks its schema.
  • Bulk and RDF import, and migration from template-based wikis such as Semantic MediaWiki.

Want the full picture? See all of NeoWiki's capabilities.

Recognize your situation?

Let's talk through the specifics.

Talk to usTry the sandbox