In short
remo is a visual canvas where a team assembles plans, diagrams, kanban boards and notes, then takes the result out as a file or hands it to an integration. A board is both the unit of work and the unit of access: whatever a person can do, they can do on a specific board and nowhere else.
The product is sized for a team of roughly ten people: one organisation, a few teams, and boards that live for a long time and change often.
Get started — a working board in ten minutes.
Explore the capabilities — everything in one table.
Solve a task — step-by-step instructions by goal.
Open the reference — roles, codes, formats, limits.
What you get
| Result | How it is built |
|---|---|
| A team workspace | organisation → team → board; the role is granted on the board |
| Visual material | sticky notes, shapes, text, frames, kanban, cards, connectors |
| Card work | status, assignee, date range, WIP, tags and links |
| Discussion | server threads on an object or point, pins, resolve, live reactions |
| Presentation | frame order, presenter and followers, late viewer |
| Protection from edits | author lock; the author or a board manager releases it |
| Real-time collaboration | cursors, presence, follow, "Bring everyone to me" |
| Controlled access | a role for a person or a team, a public link with a password and an expiry |
| Taking the result out | PNG or PDF by the chosen scope, a full JSON backup |
| Automation | agents, server commands, events, a signed webhook |
| Extension without foreign code | a declarative app panel |
What to understand first
- A board is the unit of access. Permissions are not granted on an individual object: they are granted on a board and apply to everything on it.
- A change counts as saved when the server confirms it, not when you release the mouse. The save indicator says so plainly.
- Extensions are first-party only. No foreign code runs: an integration receives events and acts with a token, an app draws a panel from a schema.
Where to go next
- Capability map — every capability in one table, and how they combine.
- Quick start — a working board in ten minutes.
- Product model — what a board is made of and how access works.