The canvas is built around your files. Not next to them.
Chatbots are single-player, and docs are linear. In Notion, files are embedded inside pages of text. In Slack, files get dropped into a stream and lost in scrollback.
In ALLO, files are the canvas itself. Drop in fifty reference images and they spread across the surface. Add a video and it plays where you put it. Pin a brief next to the mockups it describes. The references stay where you arrange them. The work grows around them.
The card is the canvas
In most tools a card is a row with a title and a few files clipped to it, and the real work happens somewhere else. Here, you click the card and it opens into the whole thing. The brief, the references, the mockups, whatever the AI made, all of it laid out in front of you.
Put anything on it
Drop in images, video, PDFs, links, and voice notes. They stay as themselves, not as attachments buried in a thread. Spread them out the way you'd spread them on a table.
Build the project together, one piece at a time.
ALLO canvases grow incrementally. Day 1 has the brief and references. Day 3 has the first round of mockups. Day 12 has the revisions. Multiple people work on the canvas at the same time, cursors visible, changes live. Nobody has to ask if this is the latest version. The canvas is the single source of truth.
A canvas grows across the project.
The same canvas, evolving over 15 days. The arc stays readable end-to-end.
Day 1 · References + brief
Designer drops in 40 reference images, the campaign brief PDF, and a colour palette. The canvas is mostly inputs.
Day 3 · First round of mockups
Three directions appear next to the references. Comments thread to specific mockups. Team votes inline.
Day 7 · Feedback collected
Brand and client comments pin to specific elements. No threads in Slack, every note has a coordinate on the canvas.
Day 12 · Revisions land
Round 2 mockups slot in beside the first round, side by side. Changes are obvious. The history stays visible.
Day 15 · Final at the bottom
The final version lives at the bottom of the canvas. The whole arc, references, drafts, feedback, decisions, final, is one scrollable artifact.
When the project ends, the canvas is the work.
Most project tools archive the deliverable and lose the context. The Slack thread gets buried. The Figma file gets renamed. The Notion page goes stale. ALLO canvases stay readable. Months later, a new teammate can see the brief, the references, every iteration, the feedback, the decisions, and the final. The canvas is the work, not a snapshot of it.
It reads top to bottom
The canvas isn't an endless wall you get lost in. It runs in an order, like a page. A teammate who opens it for the first time can follow it without anyone giving them a tour.
Built for decisions, not just generation
A pile of AI-generated options is not a decision. ALLO is where the team reviews parallel outputs, compares the tradeoffs, and chooses the direction worth shipping, with the reasoning sitting right next to it.