Public development log
Building Ceyu in public.
What is already in the product, what is being built right now, and what we intend to build next. Nothing appears under “Shipped” before it exists. If it is on this page under any other heading, do not buy the product for it yet.
The short version
Ceyu 2.0 is shipped and is what every plan on the pricing page covers today: two modules in one workspace, video, PDF and 3D on the canvas, board import, real-time multiplayer, end-to-end encrypted sync, planning with Gantt and capacity, automation, and enterprise access control. An AI assistant and deeper board-to-task linking are being built now. A community template gallery, animation review tools and a public API are planned but not started. Unshipped rows carry a target quarter, which is what Ceyu is aiming at rather than a commitment; only the shipped rows are covered by the plans on the pricing page.
Where everything stands
Four stages in decreasing order of certainty. Only the first is a promise. Pick one to narrow the table below it.
Already shipped
Everything the plans on the pricing page cover
-
Ceyu 2.0, the two-module workspace
The whiteboard and the Flowtask planning suite became one product with a shared project model, so a board and the work around it stopped being two separate tools.
-
Video, PDF and 3D on the canvas
MP4 and WEBM with frame-accurate scrubbing, multi-page PDFs, and GLB/GLTF models you can orbit, all of them ordinary objects on the board next to the images.
-
Board import from Miro, FigJam, Excalidraw and Mural
Objects, text and layout come across, so moving to Ceyu does not start with rebuilding last year's boards by hand.
-
Real-time multiplayer
Presence cursors, live object updates, comment threads with mentions, dot voting, a shared timer and presentation mode. Available from the Pro plan.
-
End-to-end encrypted cloud sync
Optional sync across your devices with the encryption keys held only on those devices. Organisations can disable cloud sync entirely with a workspace-wide local-only policy.
-
Planning: Gantt, capacity, time and expenses
Dependencies and a critical path, capacity against each person's work calendar, time tracking, expenses with receipt PDFs, customer records and reports.
-
Automation rules and recurring work
Rules that react to changes on a task, with a simulation step so you can see what a rule would have done before switching it on.
-
Enterprise access control
Single sign-on, SCIM provisioning, granular roles and tenant-scoped data boundaries.
Q3 2026
The quarter in progress
-
AI assistant on the board
Turning a cluster of notes into a structured task list, summarising a long board, and pulling the shape of a plan out of a brainstorm, with the board's contents staying under the same privacy rules as everything else.
-
Deeper board ↔ task linking
Any object on a canvas can already become a task. Next is the return path: seeing a task's status on the object it came from, and keeping the two in step as work moves.
Q4 2026
Target, not a commitment
-
Community template gallery
A public gallery of mood boards, character sheets, sprint layouts and UX flows, duplicable into your own workspace in one step.
-
Public API and webhooks
A documented API over projects, tasks and time, so Ceyu can feed the reporting and billing systems a studio already runs.
Q1 2027
Target, not a commitment
-
Animation review tools
A-B looping over a section of a clip and onion skinning across adjacent frames, for studying an arc rather than just watching it.
No quarter yet
Under discussion, and some of this will never be built
-
DCC integrations
Pushing a reference board or a task list into Blender, Maya or a game engine editor without leaving the application you are working in.
-
Self-hosted sync
Running the sync service inside a studio's own network, for teams whose contracts rule out any external storage at all.
-
Client review portal
A lightweight surface where a client approves deliverables and leaves feedback without ever seeing the workspace behind them.
A quarter on an unshipped row is what we are aiming at, not what we have promised. The plans on the pricing page cover the shipped rows and nothing else.
Your turn
The list moves because people ask
Everything under “Exploring” is there because somebody wanted it. Tell us what would make the difference for your team.
Or use the support form on its own page
Questions about this roadmap
Are the quarters on this page release dates?
Every unshipped row carries a target quarter, and a target is exactly what it sounds like. It is what we are aiming at on the day the page was built. It is not a commitment, nothing is sold on the strength of it, and it moves when the work does. Shipped rows carry no quarter because they are simply in the product.
Can I buy a plan for something listed under Planned?
Please do not. The plans on the pricing page cover what is under Shipped and nothing else. If a feature matters to your decision and it is not under Shipped, treat it as absent.
How does something move up the page?
Mostly because people ask for it. Exploring becomes Planned when we decide it is worth building. Planned becomes In development when someone starts. In development becomes Shipped on the day it is in a release you can install.
Is the Ceyu roadmap public?
Yes, and this page is it. No login, no sales call, no NDA. It is built from the same list the team works from, and it is the only roadmap Ceyu publishes.
How often is this page updated?
Whenever something moves, which is usually a few times a month. The page is generated from the working list at build time, so a row changes stage here on the next deploy after it changes in the work.
Can I request a feature, and what happens to it?
Yes, and it is the main way this page changes. Send it through the idea box above or the support form, and it is read by the people who build Ceyu. What comes up repeatedly moves from Exploring to Planned.
What do Exploring, Planned, In development and Shipped mean?
Four stages, ordered by certainty. Exploring means the problem is real and the solution is not decided. Planned means we have decided to build it. In development means someone is working on it right now. Shipped means it is in a release you can install today.
How do I find out when something has shipped?
Watch the changelog. Every shipped row lands there with the version it went out in, and the desktop app checks for updates on its own. The roadmap says what is coming and the changelog says what arrived.
What actually shipped
The newest releases, in the order they went out. The roadmap says what is coming, and these are the notes for what arrived.
Something missing from this list?
The roadmap moves because people ask. Tell us what would make the difference for your team.