Scoped realtime
One board connection carries tenant, workspace, project and resource scope. Ephemeral presence can fan out quickly while durable commands follow the same authorization boundary.
Visual collaboration
Boilerrum
Collaboration platform · Discuss your deployment
Turn ideas into shared visual work, then carry them into tasks, roadmaps and presentations.
Visual collaboration
Boilerrum Canvas
Give ideas, diagrams and workshops a shared visual workspace. Connect the discussion to the work that follows.
Explore productTeam knowledge & documents
Boilerrum Docs
Keep briefs, decisions and project knowledge in a shared document workspace, close to the team and the work.
Explore productWork planning & delivery
Boilerrum Tasks
Turn decisions into work your team can follow. Plan tasks, track progress and keep priorities visible.
Explore productIs this the right product?
- Built for
- Product, design and engineering teams that need shared context.
- What it helps you do
- Connect workshops, decisions, tasks and presentations in one visual workspace.
- Its role in your stack
- The collaboration workspace for people. Use the delivery control plane when approved work needs agent execution.
Scope & availability
Sharing a board does not grant access to unrelated projects. Confirm workspace permissions before inviting collaborators.
- Starts with
- Shared projects, boards and structured work items.
- Produces
- A visual workspace connecting decisions, tasks and presentations.
- Deployment
- Workspace access through your organisation; confirm hosting and retention for your deployment.
Follow the work
From a working session to a shared decision.
A product team explores a change, keeps supporting material close and prepares the same workspace for a review.
Illustrative workflow · not a live result
Gather the context
Place the brief, supporting documents and working canvas in the project resource tree. The team can move between the explanation and the visual work without losing the project context.
Example output
- Project context
- A brief, a working canvas and supporting documents organised under the same project.
A real-time workspace that combines a visual canvas, structured work items, documents and presentation around one shared project context.
01
Canvas & nodes
Build shared boards with mind maps, text, sticky notes, shapes, diagrams, frames, documents, code blocks, voting and connectors.
02
Work items & workflows
Link tasks to the canvas with statuses, owners, priorities, estimates, time tracking, components and activity history.
03
Planning views
Use Kanban, backlog and sprint views, then connect epics, stories, milestones and layers in roadmaps without copying the work.
04
Realtime collaboration
Keep comments, replies, mentions, reactions, watchers and notifications in the same project context with live updates.
05
Presentation & knowledge
Turn frames into a presentation with ordering and speaker notes, while versioned documents and search keep decisions discoverable.
06
Workspace governance
Manage projects, resource trees, sharing and access controls, assets and AI assistance through the Mindtro Hub boundary.
Architecture & control
A shared workspace with durable state.
The collaboration surface is backed by explicit project, resource and operation boundaries, so realtime interaction does not come at the cost of recoverability.
Sequenced writes
A single-writer sequencer, durable operation log and idempotent client mutation IDs make reconnects, ordering and safe retries predictable.
Recoverable history
Snapshots, named versions and replay keep the canvas, documents and work items recoverable; inverse hints provide a foundation for undo and time-aware collaboration.
Where teams use it
Make shared work visible.
Boilerrum keeps discovery, planning and decisions in one context so teams can move from a first sketch to work that is ready to run.
Discovery workshops
Map a problem together and keep the reasoning beside the artefacts.
Product planning
Turn ideas into owned work, priorities, roadmaps and sprint-ready slices.
Delivery handoffs
Carry context from a canvas into tasks without losing the decisions behind it.
Decision records
Keep presentations, documents, comments and outcomes searchable in one project.
In practice
What happens in day-to-day use?
Explore the working steps, operational controls and evaluation boundaries behind the product.
How do documents, boards and tasks stay organised?
A project resource tree brings folders, documents, canvases and task views into one navigation structure. A document can contain related boards and supporting documents; a canvas can carry its own documentation. Teams can keep the brief, visual exploration and work context together instead of maintaining disconnected links.
Can the same canvas support a presentation?
Presentation frames reference the working canvas. The presentation selection keeps only frames that still exist on that canvas, so removed material does not remain as a stale slide reference. This supports a direct path from a working session to a review using the same visual material.
What happens when a team switches projects?
Local workspace state is partitioned by organisation, workspace and project, with an additional canvas scope where needed. Read-only resource views disable edits such as rename and delete while keeping favourites available. Local state separation and interface controls complement server permissions; they do not replace them.
Works alongside
Give each product a clear responsibility.
Combine the capabilities your process needs. Define how products share context, permissions and results across your workflow.
Mission Control
Explore a controlled delivery path when agreed work should become an approved agent action. The control plane is in development.
Pyrodit Essentials
Evaluate private assistants for everyday team work. Agree on document access separately; a shared project does not automatically become assistant knowledge.
Build with Mindtro