Canvases: shape it with the team, then publish
Review ·
Until now, Publidock started where the work ended. Your AI tool made a dashboard, a page or a prototype; you dropped it here; the team got a link. That still works the same way. But the page someone sends a client is rarely the first one the AI made. It goes back and forth: a screen is too busy, the deck is one slide too long, the button colour isn't the brand's. Today that back and forth happens in screenshots and DMs, before Publidock ever sees the file.
So we built the place where it happens.
A canvas is a project, not a file
A canvas holds the outputs for one project: landing pages, app screens, slide decks, and the design system they share. Each output is a Publidock site underneath, so everything you know still applies: versions, rollback, sharing rules, comments. The difference is that the canvas is private. Work on it is a draft until someone presses Publish, and the people you send the link to never see the canvas, only what you published.
Bring the work you already make
Most of what lands on a canvas won't be made on it. Connect Claude Code, Cursor, VS Code or any MCP client once, and ask: "Add these screens to the Acme canvas for review." The agent sends them in as a draft. Say "publish it and send me the link" and it does that instead. It picks by what you ask for, and asks when it can't tell.
You can also drop a folder, paste HTML, import from a link, or start from a template. Everything is checked against the Publisite format when it arrives, and, if your workspace runs the render worker, loaded in a real browser to catch a screen that's wider than its frame.
Change it in place
Select a frame and ask the canvas chat for a change: "Make checkout one step." It runs on your workspace's own model key, from Anthropic, OpenAI, Google or any compatible endpoint, so there's no new AI bill from us and no data going to a model you didn't choose. Every change lands as a new draft with an Undo button. Attach a sketch or a brief and the model sees it.
Review where the work is
Comments pin to the frame they're about. Comments from people viewing the published page come back to the canvas, labelled with the version they were left on, so feedback on last week's draft isn't mistaken for feedback on today's. You can see who else has the canvas open and what they're looking at.
What it costs
Canvases are on every plan, and each output counts as one site. AI in the canvas, on your own key, is part of Team and above. Sending work in from your own AI tool works on every plan. Self-hosted installs get all of it in the same binary. The pricing page has the details, and the docs cover setup.