This reference article lists each domain that Miro uses in its SaaS application.
✏️ Some third-party applications developed for Miro, and Miroverse applications, may rely on external domains and services that Miro does not control.
Global production domains
Organizations that use a secured network must allow the following global production domains:
*.miro.com
Note: Include derivatives, for example: *.api.miro.com | *.svc.miro.com*.miro-apps.commirostatic.com*.mirostatic.comonlinewhiteboard.comrealtimeboard.com*.realtimeboard.comwebwhiteboard.comProduction tooling domains
Organizations that use a secured network must allow the following production tooling domains:
api.stigg.io
Note: Required for Miro AI functionality.*api.stigg.io
Note: Required for Miro AI functionality.braze.eu*.braze.eubrowser.sentry-cdn.iocdn.cookielaw.orgfonts.googleapis.comfonts.gstatic.commiroapp.github.iorealtimeboardhelp.zendesk.com*.sentry.iosplit.io*.split.ioRegional production domains
Organizations that use a secured network must allow the following regional production domains.
✏️ In addition to global production domains, and production tooling domains, you must also allow regional production domains for data residency in Australia, or United States, whichever applies.
Australia
*.au.miro.com
Note: Include derivatives, for example: *.api.au.miro.com | *.svc.au.miro.com*.au01.miro.comUnited States
*.us.miro.com
Note: Include derivatives, for example: *.api.us.miro.com | *.svc.us.miro.com*.us01.miro.com