Online Whiteboard
Stormboard
Rest of world Report an error0–5 in half steps. 5 means the rubric's top anchor is met on the evidence.
by Edistorm Inc. · stormboard.com
Report an error on this page Is this your product? →
Link to this page
Add ?theme=dark to the image address for dark backgrounds.
The badge shows the category and the month of the latest evaluation, and EU-Made where
that is the product’s provenance. It never shows a score.
Stormboard at a glance
- Vendor
- Edistorm Inc.
- Headquarters
- Not stated on the vendor’s pages as of 1 Nov 2026
- Data hosting
- Default not stated; pages mention United States and Canada source, captured 1 Nov 2026
- Free plan
- Not stated on the vendor’s pages as of 1 Nov 2026
- Panel verdict
- The AI panel rates Stormboard 2.5/5, the mean of 6 judges. Stormboard is a structured, template-based online whiteboard whose strongest ground is integrations and export, scoring 6-7: a documented REST API with rate limiting and public code examples, a two-way Jira sync with webhooks against cloud and on-premise Jira (Enterprise accounts only), Azure DevOps, Rally, Slack, Teams, Zoom, Webex and Zapier, and reports exporting to editable Word, Excel and PowerPoint plus PDF and CSV. how scores are made
- As of
- Vendor pages captured 1 Nov 2026; evaluated by the panel 1 Nov 2026. all sources
Read this page as one judge. Each weighs the same scores by what they care about.
The panel's verdict
Stormboard is a structured, template-based online whiteboard whose strongest ground is integrations and export, scoring 6-7: a documented REST API with rate limiting and public code examples, a two-way Jira sync with webhooks against cloud and on-premise Jira (Enterprise accounts only), Azure DevOps, Rally, Slack, Teams, Zoom, Webex and Zapier, and reports exporting to editable Word, Excel and PowerPoint plus PDF and CSV. Facilitation scores 3-4: the timer is documented in depth, but we found no public information on voting, anonymous note modes or presentation mode. Sovereignty scores 3-5: personal information is stored and processed on AWS in the United States and Canada, StormAI transmits contextual prompts and Storm metadata to Microsoft Azure OpenAI, and EU single-tenant hosting appears as an enterprise option on request. Scores spread on canvas and content, 4-6, between judges crediting a documented template engine and judges reading a template-and-section board with no public information on an infinite canvas or freehand drawing. Access and administration holds at 5; pricing transparency sits at 2 with no price figure on any captured page.
Speaks for it
- A documented REST API with rate limiting and public code examples, plus a two-way Jira sync with webhooks against cloud and on-premise Jira (Enterprise accounts only).
- Reports export to editable Word, Excel and PowerPoint as well as PDF and CSV, with reports embeddable back into the storm.
- A role-based licensing model documented at storm, folder and team level, where members always occupy a licence and guests do not.
- StormAI is optional, can be disabled at account level, never trains on customer data, and names Microsoft Azure OpenAI as its processor.
- Single sign-on with Active Directory, Okta, OneLogin or AWS on an Enterprise subscription, and single-tenant hosting in Germany, Ireland, France or the UK on request.
Held against it
- No price figure on any captured page, including the pricing page — plan names and a 30-day free trial on Startup and Business are public, no figure is.
- We found no public information on an infinite canvas, freehand drawing, pen input or search across boards — the pages describe a structured, section-based workspace.
- We found no public information on voting, anonymous or private note modes, or a mode that brings all participants to one view.
- Encryption at rest depends on the level of the team's subscription, and no deletion period for boards or accounts is stated.
- Single sign-on, the two-way Jira integration and guest contributors sit on the Enterprise tier, and we found no public information on SCIM provisioning or audit logs.
Best for
- You run structured workshops from hundreds of templates and section types — matrix, Venn, fishbone, an editable spreadsheet — and need editable Word, Excel or PowerPoint reports afterwards.
- Your team plans in Jira and needs a two-way sync that creates and updates issues with webhooks, and you can buy at the Enterprise tier.
- You want an optional AI assistant you can disable at account level, with the processor named as Microsoft Azure OpenAI and a stated no-training guarantee.
- You mix licensed members with occasional external guests who occupy no licence, alongside view-only viewers on paid plans.
Avoid if
- Your data protection rules exclude US or Canadian storage or US AI processors by default — personal information is stored and processed on AWS in the United States and Canada, and StormAI transmits contextual prompts and Storm metadata to Microsoft Azure OpenAI.
- You need external contributors to edit boards without an Enterprise subscription — guest contributors are Enterprise-only, and on the Business plan converting a member to a guest requires closing every storm they own and participate in.
- You need every participant able to export — only Storm Creators or Administrators can export or download a storm.
- You must compute an annual cost before committing — ask the vendor: the public pages we read do not show it
The scores
| Criterion | Panel median |
|---|---|
| Canvas, templates & content | 2 of 5 |
| Workshop facilitation & participation | 2 of 5 |
| Integrations, import & export | 3.5 of 5 |
| Sharing, permissions & administration | 2.5 of 5 |
| Security, AI controls & deployment | 3 of 5 |
| European sovereignty | 2 of 5 |
Canvas, templates & content
Show reasoningHide reasoning
How this is scored
What can be put on the board and how fast: an infinite canvas, sticky notes, text, shapes and connectors, freehand drawing and pen input, frames and sections, images, files, documents and video embedded on the board, tables, mind maps, diagrams and flowcharts, a template library for workshops, retrospectives and planning, own templates for the organisation, search across boards, performance on large boards, and AI that clusters, summarises or generates content.
0 — Not a whiteboard; there is no shared canvas to put content on.
3 — A shared board with sticky notes, text, shapes and drawing; templates, embeds, diagrams and large boards are basic or not described.
5 — An infinite canvas with sticky notes, shapes and connectors, frames, images and files on the board, a template library for workshops, retrospectives and planning, own templates saved for the team, and the board usable on desktop, browser and tablet with pen input.
8 — Diagrams, mind maps, tables and kanban on the same board, embeds of live documents and video, templates managed centrally for the organisation, search across all boards, documented limits for large boards (objects, participants), and AI that clusters or summarises notes with its data use stated.
10 — A canvas a whole organisation builds on: structured data on the board (cards linked to records, custom fields), smart diagramming with shape libraries for named notations, offline work with conflict-free sync described, board performance at stated scale, and every content type exportable with its structure.
The Workshop Facilitator
Hundreds of templates I can customize, save and re-run, structured section types like matrix, Venn, fishbone and a spreadsheet with editable rows, calendars on the board, and images and files pulled in from Google Drive, Box or Dropbox — that covers most of my evening build. What holds it down is that the pages describe a template-and-section board: I found no public information on an infinite free canvas, freehand drawing, connectors or pen input for the moments a workshop goes off-script. 1 2 9 10
The Product Team Lead
The template engine is genuinely documented — hundreds of templates, reusable own templates and vendor-built enterprise templates private to the team, plus section types from Venn and Fishbone to an editable spreadsheet, with images and files added from Google Drive, Box or Dropbox. We found no public information on an infinite canvas, connectors, freehand pen input or limits on large boards, so for our story maps and architecture sketches this reads as a structured workspace rather than a free-form board. 1 2 9 10
The Microsoft 365 Admin
Storms are organised into structured sections rather than described as a free-form infinite canvas, but the content model is real: hundreds of templates across agile and project work, custom templates users create and share, vendor-built enterprise templates kept private to the team, section types including Matrix, Fishbone, Venn and an editable Spreadsheet, images and files from Google Drive, Box and Dropbox, and live work on Docs, Sheets and Slides inside the Storm, plus an optional AI whose data-use terms are spelled out. We found no public information on freehand drawing, search across all Storms, or stated size limits for large boards. 1 2 4 9 10 17
The Works Council Member
This is a structured board built on sections rather than a described infinite canvas: hundreds of templates, own and team templates that can be saved and reused, spreadsheet, matrix, Venn, funnel and fishbone section types, calendars, and images and files brought onto Storms through Drive, Box and Dropbox. We found no public information on freehand drawing or pen input, connectors, search across Storms, or documented performance limits on large boards, so the evidence reaches the structured-template level rather than a full canvas. 1 2 9 10
The Public-Sector Project Lead
Storms are built on template sections — matrix, Venn diagram, fishbone, funnel and a spreadsheet with editable rows — with hundreds of templates, reusable custom templates and images or files from Google Drive, Box and Dropbox placed on the board, which suits my structured workshops with municipalities. We found no public information on an infinite free-form canvas, freehand drawing or pen input, search across boards, or limits for large sessions. 1 9 10 2
The Skeptic
The structured content is real and documented: hundreds of templates, templates a team saves for its own reuse, sections that behave as structured containers — spreadsheet with editable rows, matrix, Venn, fishbone — files brought onto the storm from Box, Dropbox and Google Drive, and an AI assistant whose data use is published in unusual detail. What I could not find is the canvas underneath: we found no public information on an infinite canvas, freehand drawing or pen input, search across boards, or documented limits for large boards. 2 9 10 17
Workshop facilitation & participation
Show reasoningHide reasoning
How this is scored
What it takes to run a session on the board: guests who join without an account, a timer, voting and dot voting, a private or anonymous mode for notes, bringing everyone to the facilitator's view (summon, follow), a presentation or frame mode, locking objects, reactions, breakout areas, an agenda or session plan, built-in audio or video or the call apps the board runs inside, participant limits, and accessibility for participants (keyboard, screen reader, contrast).
0 — No real-time collaboration; only one person can work on a board at a time.
3 — Several people edit the same board in real time and see each other's cursors; facilitation tools and guest access are basic or not described.
5 — Guests join by link without an account, a timer, voting, bringing participants to the facilitator's view, a presentation mode through frames, locking objects, and comments with mentions.
8 — A private or anonymous mode for brainstorming, voting with results and export, breakout areas or assigned frames, a session agenda or facilitator panel, the board running inside Teams, Zoom or Webex meetings, participant limits per session stated, and an accessibility statement for the board.
10 — Facilitation that a large event runs on: hundreds of participants per board with stated limits, facilitator controls over who may edit what and when, session recordings or summaries with their data use stated, a published accessibility conformance report (WCAG), and facilitation features documented step by step.
The Workshop Facilitator
The timer is documented exactly how I run it — pre-set or custom times, a sound at the end, a label the whole team sees, started only by the Storm Administrator — and the board works inside Zoom, Teams and Webex. But the things a mixed-client session lives on are undocumented here: I found no public information on voting or dot voting, anonymous or private note modes, or bringing everyone to one view, and guest access is a Business-and-Enterprise matter with Guest Contributors an Enterprise-only role, while any Contributor a creator invites is automatically counted towards the bill. 2 11 15
The Product Team Lead
The timer is documented in real depth — presets, custom time, team-visible labels, sound, one per storm, administrator-controlled — and the board runs inside Zoom, Teams and Webex. We found no public information on voting, anonymous modes, presentation mode or summoning participants, and guest contributors are an Enterprise-only role, so the facilitation kit looks thin for our retrospectives. 2 11 15
The Microsoft 365 Admin
The timer is documented end to end — custom times, sounds, labels, controlled by Storm Administrators — and the board runs inside Teams, Zoom and Webex, with chat exposed in the API and guest as a real role that does not consume a licence (guest contributors on Enterprise only). We found no public information on voting, private or anonymous note mode, bringing everyone to the facilitator's view, locking objects, breakout areas, participant limits or accessibility conformance. 2 4 11 12 15
The Works Council Member
The timer is documented in unusual detail — pre-set and custom times, a label everyone on the team can see, sound alerts, one timer per Storm set only by Storm Administrators — and members, guests and viewers are distinct, administered roles. We found no public information on voting, an anonymous or private mode for notes, bringing participants to the facilitator's view, breakout areas, participant limits per session, or an accessibility statement, so facilitation stays at a basic documented level. 11 12 15
The Public-Sector Project Lead
The timer is documented in detail — administrator-controlled, with pre-set and custom times, labels and a sound alert — and guests exist as a role that does not consume a licence, though guest contributors are an enterprise-only feature. We found no public information on joining by link without an account, voting, a private mode, follow-the-facilitator or presentation mode, and no accessibility statement for the board — the last would stall any tender I run. 11 15 12
The Skeptic
The timer is documented down to the sound it plays and is available on all plans, guests exist as a licence-free role, and the board runs inside Teams, Zoom and Webex — but guest contributors are an Enterprise-only role, and on Business every storm a member owns or participates in must be closed before they can be converted to a guest. We found no public information on voting, anonymous or private note modes, a follow-me or presentation mode, object locking, participant limits per session, or accessibility for participants. 2 11 12 15
Integrations, import & export
Show reasoningHide reasoning
How this is scored
How the board connects to the work around it and whether the content can leave: apps for Teams, Zoom, Webex, Slack and Google or Microsoft files, a two-way sync with Jira, Azure DevOps or other work tools, embedding boards in Confluence, SharePoint or intranets, a documented REST API and webhooks, import from Miro, Mural or other boards and from CSV or images, and export as PDF, image, CSV of the notes or an editable file another tool can open.
0 — No integration and no export of any kind; content can only be viewed on the vendor's board.
3 — Export as image or PDF and a few named integrations; an API, imports and structured export are basic or not described.
5 — Apps for at least Teams or Zoom and Slack, an integration with Jira or another work tool, embedding a board in other tools, export as PDF, image and CSV of the notes, and a documented API.
8 — A two-way sync with Jira or Azure DevOps that keeps cards and issues aligned, a REST API with webhooks covering boards and items, import from other whiteboards documented, an export in an editable or open format, and a marketplace or app framework for extensions.
10 — Integration and exit both complete: an API that can read and write everything the board holds, a full account export in an open format that another tool imports with structure kept, SDKs or an embeddable board for own applications, and the export and deletion on termination documented.
The Workshop Facilitator
The strongest area: a documented REST API with endpoints for storms, ideas, folders, tags, templates and users plus rate limiting, a two-way Jira integration with webhooks, issue creation and story-point updates supporting both Jira cloud and on-premise, reports exported to Excel, Word, PowerPoint and PDF including an editable download, CSV data portability, and Zapier connections to a thousand apps. I found no public information on importing from Miro, Mural or other whiteboards, and the deep Jira sync sits behind the Enterprise tier. 2 4 7 13 14
The Product Team Lead
This is what I care about most and it delivers: a two-way Jira integration with application link and webhooks that creates and updates issues including story points, priority and sprint, on cloud and on-premise Jira (Enterprise plan only), plus Azure DevOps, Rally, Slack, Zapier and a documented REST API with rate limiting and public code examples. Reports export to Excel, Word, PowerPoint and PDF, including an editable format another tool can open; we found no public information on importing from other whiteboards or an app marketplace. 2 4 9 13 14
The Microsoft 365 Admin
This is the strong suit: a documented REST API with rate limiting, GitHub examples and endpoints covering Storms, Ideas, Folders, Templates and Users; a two-way Jira integration with webhooks that works against both Jira cloud and on-premise; Azure DevOps, Rally, Teams, Power Automate, Office 365, Slack, Zoom, Webex and Zapier; and export to Excel, Word, PowerPoint, PDF, an editable report, and CSV for portability. We found no public information on import from other whiteboards or a full account export in an open format. 2 4 7 9 13 14
The Works Council Member
A documented REST API with rate limiting covering Storms, ideas, folders, tags, templates and users, a two-way Jira integration with an application link and webhooks (Enterprise accounts only, both Jira cloud and on-premise), integrations with Teams, Zoom, Webex, Slack, Azure DevOps, Rally and Zapier, and reports exported as editable Word, Excel and PowerPoint as well as read-only PDF. We found no public information on import from other whiteboards or on a full account export in an open format another tool could open with the structure kept. 2 4 9 13 14
The Public-Sector Project Lead
A documented REST API with rate limiting and public code examples, apps for Teams, Zoom, Webex and Slack, Zapier, and a two-way Jira integration with webhooks, creatable and updatable fields and support for on-premise Jira make the connection story solid. Export covers editable Word, Excel and PowerPoint reports as well as PDF, with reports embeddable back into the storm; we found no public information on importing from other whiteboards. 2 4 14 13 9
The Skeptic
This is the product's strongest ground: a documented REST API with authentication and rate limiting, a two-way Jira sync that creates and updates issues with webhooks (Enterprise accounts only), Azure DevOps, Zapier, Slack, Teams, Zoom and Webex, and reports that export to editable Word, Excel and PowerPoint rather than a stack of images. Two caveats a buyer should weigh: only storm creators and administrators can export, with more reporting options reserved to monthly and annual plans, and we found no public information on importing from Miro, Mural or other boards. 2 4 9 13 14
Sharing, permissions & administration
Show reasoningHide reasoning
How this is scored
Who can see and change a board and how the organisation controls it: sharing by link with expiry and password, guest and external-user rules, roles per board, project and team, default sharing settings set by the admin, single sign-on (SAML, OpenID Connect), user provisioning (SCIM), domain capture and control of shadow accounts, audit logs, content retention and legal hold, transfer of boards when a person leaves, and admin reports.
0 — No accounts or permissions; anyone with a board's address can see and edit it, with no way to restrict it.
3 — Boards are shared with named people or by link with view or edit rights; admin controls, SSO and audit are basic or not described.
5 — Roles per board and per team, link sharing that can be restricted or switched off, guest access controlled by the admin, single sign-on with SAML, a user and board admin console, and boards transferred when a person leaves.
8 — SCIM provisioning, domain capture of existing accounts, sharing policies set centrally (no public links, guests only from allowed domains), audit logs exportable to a SIEM, retention rules and legal hold, data classification labels on boards, and admin roles split by scope.
10 — Administration that a regulated organisation can sign off: every sharing and access setting the admin controls listed with its effect, complete audit trails with a stated retention, eDiscovery and export for investigations, delegated administration across subsidiaries, and every control documented in the help centre.
The Workshop Facilitator
The role model is genuinely spelled out — Storm Creator, Storm Administrator, Contributor, Viewer, Folder and Team roles, one Team Administrator on Business and several on Enterprise, member-to-guest conversion restricted to Team Administrators, storms private by default — and single sign-on with Active Directory, Okta, OneLogin or AWS is there on the Enterprise subscription. I found no public information on audit logs, SCIM provisioning, admin-set link-sharing rules, or what happens to a leaver's boards, which is exactly what a client's IT department asks me before signing off. 7 12 15 16
The Product Team Lead
The role model is documented in depth — Folder Owner, Administrator and Member, storm-level Creators, Administrators, Contributors, Viewers and Guests, with Members always occupying a license and Guests not — and SSO with Okta, OneLogin, Active Directory or AWS is available on the Enterprise plan, with retention settings customisable by plan. We found no public information on SCIM provisioning, audit logs, domain capture or transfer of boards when someone leaves. 7 12 15 16
The Microsoft 365 Admin
Roles are well worked out per Storm, Folder and Team with Viewers, Guests, Storm Administrators and multiple Team Administrators on Enterprise, Storms are private to specifically invited users by default, SSO is offered with Active Directory, Okta, OneLogin and AWS on the Enterprise plan, retention settings can be customised at Team or Storm level depending on the plan, and enterprise customers get extra privacy and access settings. For my 600 shadow accounts, we found no public information on SCIM provisioning, domain capture of existing accounts, audit logs exportable to a SIEM, legal hold, or transfer of Storms when a person leaves — the controls I would actually need to consolidate them. 7 12 13 15 16
The Works Council Member
Roles are documented at Storm, folder and team level — Storm Creator, Storm Administrator, Team Administrator (one on Business, several on Enterprise), Member, Guest, Viewer — Storms are private and invite-only by default, only Team Administrators may convert a member to a guest, and single sign-on with Active Directory, Okta, OneLogin or AWS requires an Enterprise subscription. We found no public information on SCIM provisioning, domain capture, audit logs, or legal hold, and the only documented leaver path converts the person to a viewer in every Storm they participate in. 7 12 15 16
The Public-Sector Project Lead
Roles are documented at team, folder and storm level — creator, administrator, contributor, viewer, guest — with storms private by invitation only, single sign-on via Active Directory, Okta, OneLogin or AWS on the enterprise plan, and member-to-guest conversion reserved to team administrators. We found no public information on SCIM provisioning, audit logs, centrally enforced sharing policies, or transfer of boards when a colleague leaves, which my agency's security review will ask for. 15 16 7 12
The Skeptic
Roles are documented to unusual depth — storm, folder and team levels; members who always occupy a licence; guests who do not; an invited contributor who counts towards the bill — and single sign-on is supported via Okta, OneLogin, Active Directory and AWS, but only with an Enterprise subscription, and Business teams get exactly one team administrator. We found no public information on link sharing with expiry or password, SCIM provisioning, domain capture, audit logs, legal hold, or transfer of a leaver's storms. 7 12 15 16
Security, AI controls & deployment
Show reasoningHide reasoning
How this is scored
How the content of the boards is protected and where the product can run: encryption in transit and at rest, customer-managed encryption keys, a dedicated or private-cloud tenant and an on-premises edition, AI features that the admin can switch off and that do not train on customer boards, which AI providers process board content, data loss prevention, deletion of boards and accounts with stated periods, and whether individual activity (logins, contributions, time on board) is tracked and shown to managers, with a statement for works councils. Who processes the data and where, and the certifications, are scored under sovereignty.
0 — Content is not protected in transit, or boards are used for the vendor's own purposes by default with no way to opt out.
3 — Encryption is mentioned and the product is described as secure or GDPR-compliant; AI use, deletion and deployment options are basic or not described.
5 — Encryption in transit and at rest stated, AI features that the admin can switch off, a statement that customer content is not used to train AI models, deletion of boards and accounts with a stated period, and a security page describing the measures.
8 — Customer-managed keys or a dedicated tenant, a private-cloud or on-premises edition documented, the AI providers that process board content named with their location, data loss prevention or classification controls, individual activity tracking described with what managers can see, and a statement or template for works council agreements.
10 — Protection that can be verified: client-side or end-to-end encryption for boards with the method published, an on-premises or sovereign-cloud edition with feature parity stated, no AI processing outside the customer's chosen region, a published penetration test summary, and every security and AI control listed with its effect.
The Workshop Facilitator
TLS on all transfers with strong ciphers, encryption at rest stated as dependent on the subscription level, annual third-party penetration tests, employee background checks, and an AI service that can be switched off at account level, never trains on customer data, and names Microsoft Azure OpenAI as its provider with no connection to it when idle. I found no stated deletion periods for boards or accounts, and no public information on customer-managed keys, data loss prevention or an on-premises edition. 7 17 18
The Product Team Lead
TLS with strong ciphers by default, annual third-party penetration tests, employee background checks, a documented security page and a single-tenant option in Germany, Ireland, France or the UK on request, with StormAI switchable off at account level, never training on the data, and Microsoft Azure OpenAI named as its provider. At-rest encryption is "encrypted at rest according to the level of your team's subscription", which I would want spelled out per plan before signing. We found no public information on customer-managed keys, an on-premises edition, data loss prevention, manager-visible individual activity or a works council statement. 6 7 17 18
The Microsoft 365 Admin
The AI story is the part legal can work with: StormAI is optional, can be disabled at account level, its data is never used to train models, Microsoft Azure OpenAI is named as the processor, and there is no connection to it when the feature is idle; TLS is standard and annual third-party penetration tests are stated. Two flags for procurement: encryption at rest is 'according to the level of your team's subscription', and no deletion period for boards or accounts is stated; we found no public information on customer-managed keys, an on-premises or private-cloud edition, or data loss prevention. 7 17 18
The Works Council Member
TLS for all data transfer and encryption at rest are stated — the latter explicitly depending on the team's subscription tier — with penetration tests at least annually, and StormAI can be disabled at account level, transmits only contextual prompts and Storm metadata to Microsoft Azure OpenAI, and its data is never used to train AI models. But we found no public information on stated deletion periods for boards and accounts, on whether individual contributions, logins or time on board are tracked and what a manager can see of that, or any statement aimed at works councils — the questions my committee must answer before agreeing under section 87(1) no. 6 of the Works Constitution Act. 7 17 18
The Public-Sector Project Lead
TLS for all transfers, at-rest encryption tied to the subscription tier, annual contracted penetration tests, employee background checks and an optional AI assistant that can be disabled at account level with a stated no-training guarantee are documented, and the AI provider is named as Microsoft Azure OpenAI. We found no public information on an on-premises or private-cloud edition — so I cannot place this in our state data centre on this evidence — nor on deletion periods, data loss prevention, or how individual activity is tracked and shown. 18 17 7
The Skeptic
The AI story is better than most: StormAI is optional, can be disabled at account level, states its data is never used to train AI models, names Microsoft Azure OpenAI as the processor, and claims no Azure connection when idle. The rest is thinner — encryption at rest is "according to the level of your team's subscription", deleting an account removes personal information but leaves the customer data contributed in place, no deletion period is stated, a single-tenant option in Germany, Ireland, France or the UK exists on request, and we found no public information on customer-managed keys, on-premises deployment, individual activity tracking, or works council statements. 6 7 17 18
European sovereignty
panel opinion
Show reasoningHide reasoning
How this is scored
Who the contracting entity and the parent company are, where boards, files and user data are stored and processed, and who the subprocessors are (hosting, CDN, real-time collaboration servers, AI providers, email, support and payment tools). Independently sourced by the sovereignty pipeline; boards hold personal data of participants and often of customers, so the whole chain counts, not only the database. An on-premises or self-hosted edition the customer runs on its own European servers counts as the customer's chain, whatever the vendor's seat.
0 — Non-EU vendor and contracting entity, hosting unstated, subprocessors unnamed, and no data processing agreement offered.
3 — A privacy policy and a data processing agreement exist, but hosting location is unstated or non-EU and the subprocessors are not listed.
5 — EU hosting available and an EU contracting entity or EU representative, but parts of the chain (AI features, CDN, real-time servers, email, support, payment) run through non-EU providers without a stated safeguard, or EU residency is an option of the top tier only.
8 — EU hosting on named infrastructure, EU contracting entity, subprocessors listed with their locations, a data processing agreement published, and security certifications (ISO 27001, BSI C5, SOC 2) stated — or an on-premises edition documented that keeps every board on the customer's own servers.
10 — Sovereign end to end and evidenced: European ownership, entity, hosting and every subprocessor including AI, or an on-premises or open-source edition with no call home, data export and deletion documented, and certifications published with their scope rather than implied.
The Workshop Facilitator
The contracting entity is Edistorm Inc., an Alberta, Canada corporation, personal information is stored and processed in the United States and Canada on AWS, and the AI chain runs through Microsoft Azure OpenAI; standard contractual clauses cover EEA transfers and an Article 27 EU and UK representative are appointed. EU-region single-tenant hosting appears as an enterprise choice rather than a default, and I found no public information on a published subprocessor list, a data processing agreement, or certifications such as ISO 27001 or SOC 2 — so my answer to the client who asks where the board is stored is North America by default. 7 8 17 18
The Product Team Lead
The contracting entity is Edistorm Inc. of Alberta, Canada, personal data is stored and processed in the United States and Canada on AWS, and the visible chain already includes Microsoft Azure OpenAI for StormAI and Intercom for the help centre — a non-European chain with an EU representative and standard contractual clauses named as safeguards. European residency appears only as an enterprise single-tenant option in Ireland or Germany on request. We found no public information on a published data processing agreement or a full subprocessor list. 6 7 8 10 17 18
The Microsoft 365 Admin
The contracting entity is Edistorm Inc., an Alberta, Canada corporation, and personal information is stored and processed in the United States and Canada; GDPR posture exists through an Article 27 EU representative, an EU-standard transfer mechanism and a named DPO contact. We found no public information on a published data processing agreement, a subprocessor list, security certifications, or EU hosting outside an enterprise single-tenant option, so the chain I would have to defend to my works council is largely unmapped. 7 8 18
The Works Council Member
The contracting entity is Edistorm Inc., an Alberta, Canada corporation, personal information is stored and processed in the United States and Canada on AWS, and Storm content for the AI feature goes to Microsoft Azure OpenAI; standard contractual clauses and an Article 27 EU representative are named, but we found no public information on a published data processing agreement, a subprocessor list with locations, or security certifications. The only European hosting in the captured pages is enterprise single-tenant hosting in Ireland, Germany and other regions on request, which does not move the default chain. 6 7 8 17
The Public-Sector Project Lead
The contracting entity is the Alberta, Canada corporation Edistorm Inc., personal information is stored and processed in the United States and Canada on AWS, and storm content is transmitted to Microsoft Azure OpenAI when the AI assistant is used — a default chain my data protection officer has ruled out. A single-tenant EU option appears on the trust page as an enterprise choice, alongside Article 27 EU and UK representatives and standard contractual clauses; we found no public information on a data processing agreement, a subprocessor list, or certifications such as ISO 27001 or BSI C5. 8 7 18 17 6
The Skeptic
The contracting entity is Edistorm Inc., an Alberta, Canada corporation, and personal information is stored and processed on AWS in the United States and Canada; European buyers get an Article 27 EU representative, standard contractual clauses for EEA transfers, and single-tenant hosting in Ireland, Germany or other regions — an enterprise ask rather than a default. We found no subprocessor list, no published data processing agreement and no ISO 27001, SOC 2 or BSI C5 certification on the captured pages, and the AI chain runs through Microsoft Azure OpenAI with its region unstated. 6 7 8 17 18
Pricing transparency
not rated — the vendor publishes no price
Show reasoningHide reasoning
How this is scored
Whether a buyer can compute the real annual cost from public pages alone: price per user and tier, how guests, viewers and external participants are counted, limits of the free plan (number of boards, objects, members), which features (SSO, SCIM, audit logs, EU data residency, AI credits, on-premises) cost extra, the enterprise tier's price or minimum, annual versus monthly billing, minimum seats and term.
0 — No public prices at all; every customer is a sales call.
3 — A starting price or a free plan exists, but how cost scales with users, guests or features is unclear.
5 — Tiers are public with their price per user and main inclusions, but at least one commonly needed piece (SSO, EU data residency, guests, AI credits, the enterprise tier) is unpriced or "on request".
8 — Every tier priced publicly with its scaling rule (members, guests, boards), free-plan limits stated, add-ons and AI credits priced, the on-premises or dedicated edition's cost or licence stated, minimum seats, term and VAT treatment stated.
10 — Complete price computability: annual cost derivable for a given team size, guest count and feature set, with every add-on, setup, support and AI fee and the cancellation and data-return terms published.
The Workshop Facilitator
Plan names and billing logic are public — Startup, Business and Enterprise with a 30-day free trial for the first two, Members occupying a license, Guests not, every invited Contributor automatically counted towards the monthly bill or annual licenses, folders from Business up, single sign-on and Jira in Enterprise. But I found no public information on a per-user price for any tier, free-plan limits or an Enterprise minimum, so I cannot work out what a twenty-person team would cost a client from these pages. 5 9 13 15 16
The Product Team Lead
The captured pages name the Startup, Business and Enterprise plans with a 30-day free trial on the first two, and describe who costs money clearly — Members always occupy a license, invited Contributors are automatically added to the bill, Guests and Viewers are free or view-only on paid plans, with SSO and the Jira integration sitting in Enterprise. I found no price for any tier, no free-plan limits and no minimum seats, so I cannot compute an annual cost for my teams from public information. 5 9 14 15 16
The Microsoft 365 Admin
Tier structure, licence counting and feature gating are public: Startup, Business and Enterprise with a 30-day free trial on the first two, Members always occupy a licence, Guests do not, invited Contributors are automatically added and counted towards the bill, Viewers require a paid plan, and SSO, the Jira integration, folders and guest contributors sit on Enterprise. We found no public information on any price figure — no per-user price, free-plan limits, annual versus monthly terms or the Enterprise minimum — so I cannot compute an annual cost for 2,400 seats from the captured pages. 9 13 14 15 16
The Works Council Member
The captured pricing page names Startup, Business and Enterprise tiers with a 30-day free trial for Startup and Business, but we found no price figures on any of the public pages: no per-user price, no enterprise price, no free-plan limits. The role-based licensing is documented clearly — members always occupy a license, a contributor invited by a Storm Creator is automatically added to the team and counts towards the monthly bill or annual licenses, guests take up no license, and viewers exist on paid plans — so who is counted is public, but without a single figure the annual cost cannot be computed. 5 9 13 15
The Public-Sector Project Lead
The public material names the Startup and Business plans with a 30-day free trial and states the counting rules — members occupy a licence, guests do not, and an invited contributor is automatically added and billed. We found no public price information — no per-user or tier figure — and the enterprise tier that carries single sign-on, the Jira integration and guest contributors directs buyers to sales, so my procurement office cannot compute an annual cost. 9 15 16 14
The Skeptic
We found no public price on any captured page, including the pricing page itself: plan names (Startup, Business, Enterprise), a 30-day free trial on Startup and Business, and the billing rules — members always occupy a licence, guests do not, a creator's invites count towards the bill — are public, but not one figure is. Single sign-on, the Jira integration and guest contributors sit behind the unpriced Enterprise tier, and we found no public information on per-user prices, minimum seats, VAT treatment, or annual versus monthly terms, though monthly and annual plans are named. 5 9 13 14 15 16
European sovereignty — proven facts
0 of 6 dimensions provenBuilt only from facts shown on the vendor's own pages. A dimension we could not prove is left open, not scored as zero.
| Legal entity | Not determined ⚠ unverified | — | uncited Report an error |
|---|---|---|---|
| Hosting location | Not determined ⚠ unverified | — | uncited Report an error |
| Hosting options | Not determined ⚠ unverified | — | uncited Report an error |
| Open source | Not determined | — | uncited Report an error |
| Data processing agreement | Not determined | — | uncited Report an error |
| Transfer impact assessment | Not determined | — | uncited Report an error |
Questions about Stormboard
Is Stormboard European?
No. whats-best.ai classifies Stormboard as Rest of world.
Where does Stormboard store data?
The default storage location for customer data is not stated on the vendor’s pages as of 1 Nov 2026. The vendor’s pages mention United States and Canada as hosting locations, per the vendor’s page captured 1 Nov 2026.
Does Stormboard have a free plan?
Not stated on the vendor’s pages as of 1 Nov 2026.
What are the best alternatives to Stormboard?
As of 1 Nov 2026, the panel rates Miro (3.5/5), Collaboard (3.5/5) and Klaxoon (3/5) highest among the other 12 Online Whiteboard products evaluated. Ratings that look equal are rounded to half stars; the order uses the unrounded rating, then the name. The highest-rated European alternative is Collaboard (UK / wider Europe). Ratings are the AI panel’s opinion, formed from public evidence: how scores are made. The full list, with European products first: Stormboard alternatives.
Where this could be wrong
- Evidence ages. The oldest capture behind this page is from 1 Nov 2026. Vendors change pricing and policies without notice; every fact reflects its source as of the capture date shown in the registry.
- Weak sourcing — Hosting location, Hosting options, Legal entity. Not confirmed on the vendor’s own pages as captured.
- AI can misread a source. Extraction and judgement are automated; a citation guarantees traceability, not infallibility. If something here is wrong, say so — no account needed, every report is decided within 5 business days, and accepted corrections are published.
What we left out
A claim that does not survive our checks costs us the claim, not the page. This is what was taken off this one.
- 33 product facts could not be confirmed on the vendor’s page as captured and were left out of this page and of the panel’s material. Know more? Tell us
- 12 compliance facts could not be confirmed on the vendor’s page as captured and were left out of this page and of the panel’s material. Know more? Tell us
- 8 legal facts could not be confirmed on the vendor’s page as captured and were left out of this page and of the panel’s material. Know more? Tell us
- 8 support facts could not be confirmed on the vendor’s page as captured and were left out of this page and of the panel’s material. Know more? Tell us
- 7 integrations facts could not be confirmed on the vendor’s page as captured and were left out of this page and of the panel’s material. Know more? Tell us
- 6 pricing facts could not be confirmed on the vendor’s page as captured and were left out of this page and of the panel’s material. Know more? Tell us
- 5 hosting facts could not be confirmed on the vendor’s page as captured and were left out of this page and of the panel’s material. Know more? Tell us
- 2 data facts could not be confirmed on the vendor’s page as captured and were left out of this page and of the panel’s material. Know more? Tell us
- 1 subprocessors fact could not be confirmed on the vendor’s page as captured and was left out of this page and of the panel’s material. Know more? Tell us
- 3 sovereignty dimensions could not be confirmed on the vendor’s own pages and are shown as unknown. Know more? Tell us
- 6 of the readings below were written against an earlier fact sheet — a fact has been corrected, added or pulled since. Until the panel next runs on this product you are reading the older judgement. Know more? Tell us
Sources (18)
The pages every claim on this page was read from — each one checked, dated, and kept verifiable.
- 1 Vendor homepage stormboard.com Checked 1 Nov 2026 Details →
- 2 Integrations page stormboard.com Checked 1 Nov 2026 Details →
- 3 Features page (enterprise) stormboard.com Checked 1 Nov 2026 Details →
- 4 API documentation api.stormboard.com Checked 1 Nov 2026 Details →
- 5 Pricing page stormboard.com Checked 1 Nov 2026 Details →
- 6 Security / trust page stormboard.com Checked 1 Nov 2026 Details →
- 7 Privacy policy stormboard.com Checked 1 Nov 2026 Details →
- 8 Terms of service stormboard.com Checked 1 Nov 2026 Details →
- 9 Canvas, templates & content — found from sitemap help.stormboard.com Checked 1 Nov 2026 Details →
- 10 Canvas, templates & content — found from sitemap help.stormboard.com Checked 1 Nov 2026 Details →
- 11 Workshop facilitation & participation — found from sitemap help.stormboard.com Checked 1 Nov 2026 Details →
- 12 Workshop facilitation & participation — found from sitemap help.stormboard.com Checked 1 Nov 2026 Details →
- 13 Integrations, import & export — found from sitemap help.stormboard.com Checked 1 Nov 2026 Details →
- 14 Integrations, import & export — found from sitemap help.stormboard.com Checked 1 Nov 2026 Details →
- 15 Sharing, permissions & administration — found from sitemap help.stormboard.com Checked 1 Nov 2026 Details →
- 16 Sharing, permissions & administration — found from sitemap help.stormboard.com Checked 1 Nov 2026 Details →
- 17 Security, AI controls & deployment — found from sitemap help.stormboard.com Checked 1 Nov 2026 Details →
- 18 Security, AI controls & deployment — found from sitemap help.stormboard.com Checked 1 Nov 2026 Details →