Collaborative pages, collections, and templates
Today: company knowledge pages that Ask Runlium answers from. Collections and templates are planned.
Runlium Docs
Create a trusted knowledge layer that is readable by people and safely usable by your organization’s AI agents.
Core capabilities
Documents, decisions, policies, procedures, wikis, templates, and governed knowledge.
Today: company knowledge pages that Ask Runlium answers from. Collections and templates are planned.
Planned: version history, named owners, and review and approval for every page.
Planned: policies, procedures, and decisions linked to the work they govern.
Planned: page-level access and external sharing controls.
Knowledge pages are searchable and Ask Runlium says which sources it used. Semantic search is planned.
Planned: periodic verification so stale or unowned content gets flagged.
Connected workflows
Each workflow is modeled as visible steps, typed events, clear ownership, approval rules, retries, and recoverable execution.
Request review when a policy reaches its renewal date.
Turn an approved decision into linked implementation tasks.
Suggest knowledge updates from repeated support questions.
AI in context
The AI experience is designed to retrieve only permitted context, expose evidence for important answers, and separate recommendations from approved execution.
What is our approved discount policy?
Show the sources behind this answer.
Which operating documents are stale or unowned?
Works with
Records, permissions, and events are common across the platform, so each module adds context to the others instead of copying it.
Event-driven workflows, approvals, agents, schedules, integrations, and execution history.
A permission-aware assistant that understands every connected business record.
A flexible customer system for leads, deals, accounts, renewals, and relationships.
New to the category? Read what an AI business operating system is, or see how the modules share one platform architecture and workspace-based pricing.
Founding design partner
Use cases from founding teams will define the first workflows, integrations, fields, and migration tools.