Borealmap draws, documents and presents your processes on three levels. Every box and every arrow carries its documentation: description, rules, owner, data and sources.
Connect your organization’s AI (MCP server and skills). It works from your documents, cites its sources, and nothing enters a diagram without human review.
Borealmap provides no AI and sends your data to no AI provider: you plug in your own.
1
Reproduces an existing diagram.
Import a Visio, BPMN, draw.io, Mermaid or PlantUML file: Borealmap reads the boxes, texts and arrows directly. A screenshot or an image is reproduced by your organization’s AI; you compare it with the original in transparency, then you validate.
Old Visio (.vsd): save it as .vsdx first. PDF or PowerPoint: export the page as an image.
Visio (.vsdx)
BPMN
draw.io
Mermaid
PlantUML
Image
Original imageBorealmap diagram
The shapes of the picture become numbered Borealmap boxes. Then you overlay them to compare.
Drag the handle to compare the original and the reproduction.
2
Starts from your existing documentation.
No need to start from scratch: your organization’s AI works from the documents you already have.
You give it your current documents: procedures, policies, guides, technical specifications.
It extracts the steps, the teams and the exchanges, and draws the diagram. That diagram is a draft, which you validate.
It fills in the documentation of each box: description, business rules, owner, data. Every field is marked “Filled by AI” and cites the original passage, so you can check it.
Documentationcomponent
B1Receive the request
Description
The payment request arrives with its invoice and budget code.
Filled by AIRequest guide · section 1
Business rules
Every request must have an invoice and a budget code.
Filled by AIPayment policy · section 3.1
An invoice already paid cannot be submitted again.
Every proposal waits for your decision: accept, edit or reject. Nothing is applied without a human, and the AI never changes the structure of an existing diagram.
Nothing enters the diagram without a human click. Fictional example.
B2Validate and approve
Business ruleEmpty: waiting for your decisionPayment policy · section 4.2
AI proposal
A payment over $50,000 requires a second approver.
Payment policy · section 4.2
Two presentation modes, for two needs.
You work in the diagram and navigate it freely. When it is time to show it, Borealmap adds two presentation modes: one to present it to an audience, the other to walk through it step by step as a team, to understand and validate it.
Option 1
Presentation mode
You are presenting the diagram.
Situations
Steering committee, management, training, a demo for a client.
Preparation
Slides prepared in advance, with presenter notes.
How it runs
You guide the eye, one slide after another. Visual effects work on every element of the diagram: a spotlight on a lane, a glow on a lane, a box or an arrow, a laser pointer.
Nominal path
Exception: sanctions match → compliance review
OverviewSlide 1 / 7
Presenter notesFour lanes: we start with payment operations, which receive the batch.
Option 2
Step-by-step mode
You are working through the process in a workshop.
Situations
Validation workshop, process review with the teams, a newcomer learning the flow.
Preparation
No slides: pick one of the diagram’s paths (nominal case, refusal, exception).
How it runs
One step at a time, stopping to discuss. Boxes off the path stay visible, but fade out.
Nominal path (happy path)Step 1 / 8
The policyholder suffers a loss.
Examples to explore
Projects, workshops and backlogs, all tied to the real process.
Here is a fictional case: the City of Rivebelle processes a renovation permit request. The diagram has three levels. Every responsibility and every risk in the panel is tied to a step of the diagram.
Explore freely: drag, zoom, click a step or a story.
1Start with the diagram: drag to move, scroll to zoom, click a box to see its sheet. Then click “Explore the process”, under this box, to go down one level.
Click the diagram to zoom with the mouse wheel
Project and rituals
Current iterationSprint 3
Project
The diagram’s lanes become the columns. Every step has its R and its A.
Step
Citizen
Counter clerk
Systems
Urban planning analyst
Inspector
R
A
C
Complete
I
RA
C
Complete
C
RA
I
Complete
C
A
R
Complete
I
C
RA
Complete
I
RA
Complete
I
R
I
C
C
RA
I
Complete
C
I
RA
Complete
I
I
RA
Complete
I
RA
I
C
Complete
RResponsibleAAccountableCConsultedIInformed
!
A register where every line is tied to a step, with its mitigation.
Type
Risk
Step
Likelihood
Impact
Owner
Due
Risk
The step 2 bottleneck breaks the legal delay
High
High
Product Owner
Sprint 4
Detail
The actual delay is 5 days for a target of 2 days. Every day of delay delays the whole permit.
Mitigation
Check the documents automatically. Follow the actual delay at every review.
Risk
The zoning data are out of date
Medium
High
Architect
Sprint 4
Detail
A recently changed zone may not be up to date. The opinion would then be wrong.
Mitigation
Require the update date in the answer. Check by hand if it is missing.
Dependency
The land registry is an external service
Medium
Medium
Architect
Sprint 5
Detail
The city has no availability commitment from the registry.
Mitigation
Try three times. Keep the last record read.
Issue
Nobody is named to decide on a variance
High
Medium
Project manager
Sprint 4
Detail
The question is open: the committee or council? Without an answer, the step has no approver in the RACI.
Mitigation
Have management decide before Sprint 5.
Assumption
All citizens can upload their plans
Low
Medium
Head of the planning department
Sprint 6
Detail
Some citizens have neither a computer nor a scanner.
Mitigation
Keep submission at the counter as a fallback.
!
Fictional example: the Claims department of Assurances Rivebelle. No diagram yet: the team starts from an extract of its Jira or Azure DevOps backlog.
Click the diagram to zoom with the mouse wheel
Project and rituals
Agile team
Import the file yourself, or ask your AI: it prepares everything, you only validate.
Import it yourself
Does the backlog or the sprint already exist? Export it as CSV: features, stories and tasks arrive with their sprint, points and status. You see everything before importing.
1Start here: click “Import from Jira / Azure” to open a sample file.
CSV file exported from Jira or Azure DevOps. No connection, no sync.
Ask your AI
Your AI is connected to Borealmap and to Azure DevOps (or Jira). It reads this backlog, creates the tickets with the Azure DevOps tool, then reports their status in a file. You validate in Borealmap.
Suggested sentence (one click sends it):
The AI changes neither the diagram nor the backlog: you click “Apply”. No sync. New Jira or Azure items arrive through the CSV file.
Conversation with your AI
YouCreate these stories in Azure DevOps and bring back their status
Your AI
Simulated example. It takes an AI connected to Borealmap and to Azure DevOps.
Update the status
File from your AI: 3 tickets read. Nothing changes before “Apply”.
Key
Story
Current status
New status
What will happen
Choose a sample file
2Pick one of the two files. They are fictional exports, ready to try.
Fictional sample files. In Borealmap, you pick your own CSV file.
Import a Jira / Azure DevOps backlog
Key
Type
Title
Parent
Sprint
Pts
Status
What will happen
3Read the last column: it says what will happen to each line. Nothing changes before “Import”.
Draw the diagram from the backlog
Features become lanes, stories become boxes, tasks become steps in a box’s detail view. Anything without a feature goes to the “To sort” lane. Nothing changes before “Create the diagram”.
Type
Title
Where it goes
What will happen
5Read “Where it goes”: each feature becomes a lane, each story a box. The tasks become the steps of their box’s detail view. Nothing changes before “Create the diagram”.
4The backlog is imported, with its sprints, points and statuses. No diagram yet? Click “Draw the diagram”: features become lanes, stories become boxes. No AI.
6The diagram is drawn and linked to the backlog. Click a number in the backlog: its box lights up. Then go to the roadmap: it starts from the sprints.
No diagram yet? “Draw the diagram” makes one from this backlog, each story linked to its box. The “Undo” button reverts the last action.
Item
Points
Status
Sprint
7Solid bars: the sprints from Jira or Azure. Dotted: the “First draft” has no sprint, so Borealmap forecasts it at the velocity. Try it: drag a bar to replan it, pull an edge to lengthen it (unfold a feature to shorten its stories), or a feature by its ⋮⋮ handle to change the order.
Fictional example: the “Swimming-pool permit request” workshop, City of Rivebelle. Five frames: four filled during the session, one still empty.
Click the diagram to zoom with the mouse wheel
Project and rituals
Agile team
Run a workshop
Fictional example: the draft diagram “Swimming-pool permit”, City of Rivebelle. Three lanes and their boxes, no descriptions.
Click the diagram to zoom with the mouse wheel
Project and rituals
Agile team
Jira and Azure DevOps
CSV export in each tool’s own format (Epic › Story › Sub-task), and reading their exports to update the links.
From workshop to sprint, with AI
The AI reads the workshop’s sticky notes and proposes features, stories and tasks, already described. You review each item. Then your AI assistant can create the backlog in Azure DevOps or Jira through our MCP. The CSV export is still there.
Ready-made templates
Retrospective, story map, review, RACI, risks, project kickoff: a complete example to copy for each.
Official schemas
Add another team’s official process to your own.
The Claims team’s official diagram is almost complete. One step is missing, done by the Accounts payable team. Follow the bubbles: add the box, link it to their official diagram, open it. Nothing is copied, and you are warned when it changes.
Accounts payable
On request
Entry pointEntry point
Claims handlingClaims team
v2Official
The official view “Record an invoice” (Accounts payable team) changed since your last review.
View of the Accounts payable team · read onlyRecord an invoice
The view changed since your last review.
Click the diagram to zoom with the mouse wheel
Official schemas
Rivebelle Insurance
Selected box
No box selected. Click + in the diagram to add the missing step.
Register the file
Level of detail
This box can open a more detailed diagram (next level).
View of the Accounts payable teamRecord an invoice
Last review
Up to dateTo review
Accounts payable team side
Accounts payable team side
You play both teams. This button does what their editor would do in their diagram. Nothing changes by itself.
Official sheet of your diagram
Process
Claims handling
Responsible team
Claims (Indemnity sector)
Status
Official
Version
2.0
Uses
No other official schema
To make a diagram official: “…” in the top bar, then “Declare official schema”.
Good to know
Read only. Their diagram is never modified.
Sensitive data cannot be linked outside its sector.
Without access, the box shows “On request: … team”. No title of their diagram is shown.
Editors see the banner and the halo on the arrows. Readers only see the dot. No email is sent.
Moving or recoloring a box is not a change. Only the content of the view counts.
Built to pass your security teams' assessment.
Planned
Data in Canada
Hosting planned on AWS, Canada (Central) region, in Montréal. Backups stay in Montréal too.
In pilot
Microsoft Entra ID or email
Organizations: sign-in through your Microsoft Entra ID directory, licences managed by your groups. Individuals and small teams: a sign-in code received by email, by invitation.
In pilot
Quebec Law 25 (Loi 25)
Export and deletion of the organization’s data, with a receipt.
In pilot
Audit log
Who changed what, and when. Adjustable retention period.
No certification (SOC 2, ISO) to date. Company run by one person. We say so upfront. Read the security page
Team · 5 to 29 members
$24 per member / month
Billed annually, in CAD, taxes extra.
Organization · 30 members and more
from $18 per member / month
The larger the team, the lower the price.
Founder offer
-20%
For 12 months for the first organizations, pilot included.