Build together, in the open.
Live editing, threads on any element, and view analytics on every page — a published artifact is a surface your team works on, not a file you send.
3 editing | Line | Plan |
|---|---|
| Marketing | $44k |
| Growth | $58k |
| Hiring | $120k |
| Total | $222k |
Collaboration usually means a pile of file copies.
final_v3_REALfinal.xlsx is not collaboration. People need one live surface.
Two people, one page
CRDTs over WebSocket: edit the same cell at once, no merge conflicts. Presence shows who is in the room.
Comments, mentions, reactions
On a chart, a cell, a slide, or the files behind them — with unread state, and resolved like a review.
See who actually read it
Views, trends and real load times per page. Visitors are hashed, and there is no third-party tag.
A shared sheet — edit it, it syncs.
This is a live, shared artifact. Change a cell; anyone else looking sees it move, right now.
It all connects.
Every piece is the same live artifact, wired together — explore the rest.
Questions, answered
How fast can I publish a shared page?
Most pages go from a sentence to a live link in under a minute. Describe it, refine it in the browser, and share — no deploys, no exports.
Does it stay connected to my data?
Yes. Pages read live from Google Sheets, Shopify, your warehouse, or any API, so what you share stays current without re-exporting.
Is it private?
Artifacts are private by default. You control visibility per page and can publish behind your own workspace or subdomain.
Can we push Hiring to Q4? Frees up runway.