System of Record · Collaboration
OwnWiki
Knowledge. Operations. Information Sharing.
A self-hosted knowledge operating system combining pages and databases in one workspace with function-owned spaces, clear ownership, and audit-ready review trails.
In week one. Not year one.
01
Specs and their tracking databases live on the same page — the wiki-to-tracker shuffle ends.
02
Every page has a named owner and a review trail, so stale docs get caught instead of discovered.
03
Company knowledge stays on your infrastructure, with a full audit trail on every change.
And the Confluence renewal stops being a line item — the replacement is an asset you own. Run your numbers →
What sets it apart
Pages and databases in one workspace — no switching between tools
Function-owned spaces with nested trees and clear ownership
Audit-ready review threads with governance panel and notifications
Key Capabilities
15 Block Types
Headings, lists, tables, callouts, code blocks, toggles with slash commands, auto-save, and inline databases.
Function Spaces
Nested page trees with space-level members, ownership, and cross-team visibility from a single front door.
Inline Databases
Structured data alongside documents for managing specs, inventories, and operational checklists.
Review Threads
Inbox notifications, governance panel, and audit-ready review trails living alongside the documents.
Who it’s for
Architecture decision records, runbooks, and API docs in function-owned spaces with review workflows.
Specs with inline databases for feature tracking, embedded from the same workspace — no Notion + Jira switching.
SOPs, checklists, and process documentation with governance panel and mandatory review cycles.
Perpetual Licence
OwnWiki is available as a perpetual licence. You own the software forever. Deploy on your infrastructure. No annual renewals, no per-seat pricing, no vendor lock-in. Prefer OpEx? A managed subscription is available too — switch between the two anytime, nothing to re-buy.
Every screen here also works without the screen.
OwnWiki implements the Own360 headless spec: a standard /api/v1 surface with OpenAPI, cursor pagination, idempotent writes, and entity.changed events — drivable from its own CLI, any HTTP client, MCP tools generated straight from its OpenAPI, and the OwnAgents runtime.
$ ownwiki entities # 9 entities
$ ownwiki space list --limit 20
$ ownwiki space create --data '{…}'
$ ownwiki domain publishThe generated OwnWiki CLI — every entity and domain op, OwnAuth-authenticated, idempotent by default.
Entities
Domain ops
13 verified agent tasks · 6 cross-app workflows
- OwnHRMS → OwnWiki → OwnTasks — OwnHRMS new hire → OwnWiki onboarding page → OwnTasks onboarding task (3-app chain)
- OwnDesk → OwnWiki — OwnDesk incident ticket → OwnWiki postmortem page titled with the ticket id
- OwnSocial → OwnWiki → OwnChat — OwnSocial campaign → OwnWiki campaign brief → OwnChat launch announcement (3-app chain)
- OwnHRMS → OwnTasks → OwnWiki → OwnChat — Hire onboarding: OwnHRMS employee -> OwnTasks checklist task -> OwnWiki onboarding page -> OwnChat announcement
Inside OwnWiki
The full story — why it exists, what it replaces, every capability in detail, and real product screens.