Board, list and calendar
Kanban with swimlanes and statuses you define, a dense table with inline editing and bulk actions, and due dates in a month or week grid with Google Calendar events alongside.
Launch 20% off every paid plan for the first year.
See the plansProject planning
Every planning tool can hold a task with a due date. The question for a studio or an agency is what happens to the half of the work that comes before the task exists — the references, the rough cut, the three directions and the argument about which one is right. In most stacks that half lives in a whiteboard tool and the plan lives somewhere else, and by the time anyone questions a decision the reasoning is two subscriptions away.
Views are not features if they are separate tools stitched together. These are five readings of the same tasks, which is why moving something in one of them moves it in all of them.
Kanban with swimlanes and statuses you define, a dense table with inline editing and bulk actions, and due dates in a month or week grid with Google Calendar events alongside.
Bars, dependencies and a critical path for the plan you show a client, plus a wider horizon for seeing how several projects overlap. Both start at the Pro plan.
Tasks and subtasks with priority, assignee, estimate and due date; custom fields for whatever your process tracks; saved filters, portfolios and task templates.
A timer that logs against a task, capacity checked against each person's work calendar, expenses with receipt PDFs, customer records and reports per project, customer or person.
The plan and the boards share one project model, so a task can reference the board object it came from and the reference that justified a decision is next to the work that delivers it.
Local-first storage that keeps working offline, opt-in end-to-end encrypted sync, and a workspace-wide local-only policy an admin can enforce.
If the work has no visual side at all, a planning tool on its own will be cheaper than paying for a canvas nobody opens. If you need a public API or webhooks today, both are planned and neither is shipped, so anything that has to be driven from outside rules Ceyu out. Single sign-on and SCIM need the Enterprise plan. And a team already deep in Jira for engineering will get more from connecting it than from replacing it.
Creative work does not begin as a task list. It begins as references, sketches, a rough cut and an argument about which direction is right, and only then becomes a schedule. A planning tool that cannot hold the first half loses the reasoning behind every decision it schedules. Ceyu keeps the canvas and the plan on one project model, so a task can point back at the board object it came from.
You can, and that is the point of paying one bill instead of two, but you do not have to start there. Boards import from Miro, FigJam, Excalidraw and Mural, so you can move one project across and leave the rest where it is until you are convinced.
Yes. A timer logs against a task, with manual entry and a weekly sheet. Expenses are recorded against a project and can produce a receipt PDF, customer records sit next to the projects and hours booked to them, and reports cover hours, cost and progress per project, customer or person.
A public API and webhooks are planned and not shipped, so nothing outside Ceyu can drive it yet. Single sign-on and SCIM need the Enterprise plan. And if your work has no visual side at all, a planning tool on its own will be cheaper than paying for a canvas you never open.
Not a trial project — a real one, from the first reference board to the invoiced hours. The free plan carries three projects, which is two more than that test needs.