Compare
Metabase embedding vs EmbedPortal
Metabase makes it easy to embed a chart or dashboard. Running a multi-customer portal around it is the harder part. Here is how they compare.
At a glance
Side by side
| Native Metabase embedding | EmbedPortal | |
|---|---|---|
| What you build | Your app signs embed tokens and handles login, users, navigation and branding | Portal, login, navigation and branding are included |
| Row-level security | Locked parameters signed by your server | Locked parameters signed by EmbedPortal from each viewer's values |
| External users | Managed in your own app | Invited and managed in EmbedPortal |
| Other BI tools | Metabase only | Metabase plus Power BI, Tableau, QuickSight, Looker and Domo |
| Branding | Depends on your Metabase plan and your own app | Logo, colors, custom domain and email sender |
| Hosting | Self-hosted or Metabase Cloud | Works with your Metabase; Enterprise includes Metabase hosting |
Choose native Metabase embedding if
you are comfortable signing tokens in your own backend, only need Metabase, and want to build the surrounding app yourself.
Choose EmbedPortal if
you want a ready-made, branded portal for customers with users, groups and audit logs, or you use Metabase beside other BI tools.
FAQ
Common questions
Does EmbedPortal work with open-source Metabase?
EmbedPortal uses Metabase signed embedding with locked parameters. Check which embedding features your Metabase plan includes.
Can viewers change the filters?
No. Locked parameters are signed into the token, so viewers cannot change them.
Can EmbedPortal host Metabase for us?
Enterprise plans include a dedicated instance with Metabase hosting.
Try it with your own dashboards
14-day free trial. Unlimited viewers on every plan.