2026-09-13
The MVP is ready: the demo is open
Depensee is out as a public demo: a task map with dependencies, real-time collaboration, imports from Jira and Yandex Tracker. What you can try today, why it is an MVP rather than a release, and where we go next.
- #status
- #mvp
- #demo
The public demo we promised on the landing page is out. You can try Depensee at demo.depensee.com (Russian version - demo.depensee.ru). Sign up with an email, free, no plans and no card.
What you can do today
- Workspace and team. Your own workspace, teammates invited by email with admin / editor / viewer roles. The invite works even if the person has no account yet.
- Boards. Several boards in one workspace. The first one is created during onboarding: blank, with demo tasks, or with an import from a tracker.
- Task map. Tasks are cards on a canvas: status, priority, assignee, due date, progress. Cards can be moved, the layout is saved, and the level of detail follows the zoom.
- Relations. Three types:
blocks,contains,relates. Drag a link from the edge of a card onto another task, and the map shows what depends on what. - Auto-layout. Two modes -
flowandwaterfall- turn the graph into a readable diagram: fewer crossings, a clear direction. - Real-time collaborative planning. The team works on one map: who is on the board right now, other people’s cursors, card moves, relations and edits - everything reaches every participant right away.
- Import from Jira and Yandex Tracker. Connect with an API token, pick a project - tasks with statuses, assignees and links land on a board. Read-only for now: the tracker stays the source of truth.
- Planning. Due dates on cards, filters by status and assignee, sorting by due date.
Every screen is covered in the user guide.
An MVP, not a release
One important caveat: this is a minimum viable product, not a full release. Its job is to test the idea: a project and its tasks can be seen as a map and worked on together. There are rough edges, some flows are incomplete, and there are surely things we do not know about yet.
What to build first will largely be decided by the first users. If something is missing or gets in the way, tell us. That is the best signal we can get.
Where we go next
There are more ideas and directions than hands. The main ones:
- Task tracker integrations. More trackers on top of trackerkit, import into an existing board, two-way sync.
- LLM integration. Access to the map from assistants, for example via the Model Context Protocol: ask what is blocking the release, break a large task into subtasks, find bottlenecks in the dependencies.
- A built-in task tracker. A board without an external tracker already works. Grow it into a full tracker with its own planning model.
- Further work on collaborative planning. The team already plans on one map in real time; next is refining that mode: creating a task together with its relation in one motion from the side of a card, handling simultaneous edits of one card gracefully, making a planning session smoother.
- And more: sprints, a self-hosted edition, dependency and workload analytics.
The order is not fixed. If something on this list matters to you more than the rest - say so.
How to help
Try the demo, bring your team, and tell us what worked and what did not: info@depensee.com or the Telegram channel. We read every message.