Four views, one project
List, board, calendar and Gantt read the same data. You change the view to suit the question instead of maintaining a second copy of the plan.
For project managers
A plan built on what the team is actually doing.
Planning creative work fails in a specific way: the plan is maintained in one tool and the work happens in another, so the plan is always a description of last week. Ceyu puts the schedule next to the canvas the work lives on, which is the only arrangement where updating the plan is cheaper than not updating it.
The planning surface
Every item below exists in the product today. What is still coming is on the roadmap.
Dependencies and milestones
The Gantt view carries real dependencies and milestones, so a slip propagates visibly rather than being absorbed silently by the next task.
Capacity before commitment
Capacity planning shows what people are already committed to, which is the number you need before you agree to a date, not after.
Statuses that match your process
Define your own statuses and their colours. A workflow that does not fit three columns does not have to pretend that it does.
Time and expenses on the task
Tracked time sits on the task, with a timer that pauses on idle instead of billing lunch. Expenses are recorded against the project with GoBD-compliant records.
Repeating work stays repeatable
Project templates and recurring tasks mean a monthly retainer or a fixed onboarding is set up once rather than rebuilt from memory.
What this does not do
There is no resource-levelling algorithm, no earned value analysis and no portfolio roll-up across dozens of projects. Ceyu suits a team that runs a handful of creative projects at once and wants the plan to stay honest, not a PMO that needs formal programme controls.
Plan one real project with it
Bring a project that is already running and rebuild its plan here. If the plan does not stay current on its own, it has not solved anything, and you will know within a week.