/ omninium · integrated workspaces
One workspaceto rule them all.
Docs, decks, whiteboards, design canvases, tables, boards, dashboards, forms, live code — fifteen page types over one source of truth, wired with automations and an assistant that acts. One app instead of five subscriptions.
/ one app to rule them all
Everything they do, one product does together.
/ pages · the data engine
Ten lenses. one truth.
Keep scrolling — the same records recompose through every view. Nothing is exported, nothing copied: the page IS the view.
/ five engines · fifteen types
Documents, decks, canvases, data, code. all first-class.
Five render engines behind fifteen page types — a brief, its deck, the design exploration and a running prototype live in the same tree as your data.
Launch brief
/ sources
Structured data that stays yours. Real fields, not free text.
Fifteen field types
From text and numbers to relations, formulas, people and files — a schema that means something, not free text pretending to be structure.
Directional relations
Link records across sources with a labeled kind. A launch task points at its project; the project sees its tasks.
Bind once, inherit down
Every page binds to a source — or inherits its parent's, so a whole branch of the tree shares one dataset. Change a record once and every view stays in step.
/ automations
One trigger. Ordered steps. zero babysitting.
Set a trigger, chain the steps — branch, loop, call an API, ask a model — and let it run while you work. Everything acts on the one source your whole workspace reads.
Automation
record-updated
when a record changes
find-records
step 1
branch
step 2
invoke-model
step 3
update-record
step 4
Run trail
runningrecord-updated
CQ-103 · Record demo video → Blocked
find-records
matched 3 records with status Blocked
branch
owner is set → continue
invoke-model
drafted an unblock summary
update-record
CQ-103 flagged · owner notified
every run leaves this trail — step by step, in the open
Six ways in
Thirteen blocks
/ ai assistant · claude sonnet 4.5
An assistant that acts — not one that just answers.
Ask for a field, a view, an automation. It streams its answer live and calls 22 real tools — you watch the workspace build itself.
it builds, you approve — every action is a visible tool call
It acts, not just answers
Ask for a field, a page, a view, an automation — the assistant calls real tools and you watch the workspace change.
Every call visible
Every action it takes renders inline as it works — you watch each change land in your workspace before the sentence finishes. No black box.
You stay in control
It builds, proposes and configures — but switching an automation on is always your click, and every change is undoable.
/ the point
Stop syncing copies.
Start composing.
/ workspaces · access · payments
Everything else you'd expect. done properly.
/ roles
Six roles, plus yours
/ sharing
Links that behave
/ api
API access, done right
/ credits
AI, metered honestly
/ layout
Fields become elements
/ sync
Bring data in, safely
/ the model
A page is the view
/ workspaces
Personal or shared
/ pricing