Panel rating · 6 judges · How to read the stars
Category median
Sovereignty: 1 of 6 dimensions proven
0–5 in half steps. 5 means the rubric's top anchor is met on the evidence.
by Maglr · maglr.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.
Maglr at a glance
- Vendor
- Maglr
- Headquarters
- Not stated on the vendor’s pages as of 10 Nov 2026
- Data hosting
- In the EU source, captured 10 Nov 2026
- Free plan
- Not stated on the vendor’s pages as of 10 Nov 2026
- Panel verdict
- The AI panel rates Maglr 1.5/5, the mean of 6 judges. Maglr is a web-based publication design tool for white papers, annual reports, digital magazines and brochures, built around three editor views — Design, Build and Content — and ready-made building blocks. how scores are made
- As of
- Vendor pages captured 10 Nov 2026; evaluated by the panel 11 Nov 2026. all sources
Read this page as one judge. Each weighs the same scores by what they care about.
The panel's verdict
Maglr is a web-based publication design tool for white papers, annual reports, digital magazines and brochures, built around three editor views — Design, Build and Content — and ready-made building blocks. It scores strongest on collaboration and approval: roles map to editor views, live publishing sits behind an admin-granted permission, and review runs through comments, review rounds and a separate preview URL. Distribution and integrations score 3-4, covering a live URL on a coupled domain, interactive embeds, a presenter app, Google Analytics 4 and Tag Manager per domain, and Zapier pushes. Weakest are editorial planning, with no calendar, briefs or workload views found publicly, and content model and reuse and AI and content rights, both flat at 2, with AI at exploration stage only. Sovereignty scores 4-6 on storage at Amazon Web Services in Frankfurt with backups in Ireland and named subprocessors, offset by Cloudflare caching outside the EU for up to 24 hours and no public information on a data processing agreement. Persona-weighted totals range from 2.7 to 3.5.
Speaks for it
- Collaboration and approval scores 4-5, with roles mapped to three editor views and live publishing gated behind an admin-granted permission.
- Review is documented end to end — comments including on the mobile version, settable review rounds, solving and re-reviewing comments, and a separate preview URL to share for feedback before anything goes public.
- Delivery covers a live URL on a coupled domain, a separate preview URL, interactive embeds and a presenter app, wired to Google Analytics 4 and Google Tag Manager per domain and Zapier pushes, with an anonymous mode that skips IP and geo-location tracking.
- Storage is stated at Amazon Web Services in Frankfurt with two daily backups plus additional backups in Ireland, and subprocessors Adyen, Cloudflare and Crisp are named with their purposes.
- A plans page publishes a price range from 400.00 to 1100.00 EUR across Basic, Advanced and Enterprise, with freeform scenes gated to Advanced and Enterprise.
Held against it
- Editorial planning scores 0-2, with no public information on an editorial calendar, briefs, campaign or topic grouping, or deadline and workload views.
- Content model and reuse scores a flat 2: content is stored as designed grid and freeform scenes, with no public information on a configurable content model, locales managed side by side, or a documented export.
- AI and content rights scores a flat 2, with AI listed as explorations and no public information on model providers, where AI processing runs, training on customer content, retention, or rights to generated output.
- We found no public information on a documented API, webhooks or SDKs, so integrations rest on Google Analytics 4, Google Tag Manager and Zapier.
- We found no public information on version history with restore, a formal approval status before publishing, or an audit log recording who released which version.
Best for
- You design interactive publications — white papers, annual reports, digital magazines, product brochures — and want review rounds and a separate preview URL before anything goes public.
- Your team needs writing separated from publishing: the Content view edits text and media only, and live publishing requires an admin-granted permission.
- Your analytics and form flows fit Google Analytics 4, Google Tag Manager and Zapier, including an anonymous analytics mode with no IP or geo-location tracking.
- You need storage stated at Amazon Web Services in Frankfurt with additional backups in Ireland, and subprocessors named with their purposes.
Avoid if
- You need editorial planning — an editorial calendar, briefs, campaign grouping, due dates and workload views — rather than page status colours and manual republishing.
- You need structured multilingual content: pages are stored as designed grid and freeform scenes, automatic translation appears only as an announced exploration, and shared libraries are announced as upcoming.
- You need generally available AI assistance: the vendor's own updates page lists the AI work as explorations that are not generally available.
- You need API-driven or automated delivery: changes reach the live URL only when you click Publish live again, and delivery runs on the vendor's own channels rather than a documented interface.
The scores
| Criterion | Panel median |
|---|---|
| Planning, editorial calendar & briefs | 1 of 5 |
| Creation, review & approval | 2.5 of 5 |
| Structured content, localisation & export | 1 of 5 |
| Publishing, distribution & integrations | 2 of 5 |
| AI assistance & content rights | 1 of 5 |
| European sovereignty | 2 of 5 |
Planning, editorial calendar & briefs
n/r
Show reasoningHide reasoning
How this is scored
Turning a content strategy into scheduled work: topics and campaigns, an editorial calendar across channels, briefs that carry the goal, audience and keywords to the writer, and a view of what is due, late or missing.
0 — No planning at all; the product only stores or renders content.
3 — A calendar or list view of content with publish dates and statuses.
5 — An editorial calendar across channels with owners, due dates and custom statuses, and content grouped by campaign, topic or channel.
8 — Strategy connected to the plan: briefs carrying goal, audience and keywords attached to each piece, topics or personas defined once and assigned to pieces, configurable workflows per content type, workload and deadline views per person, and recurring formats scheduled as series.
10 — The plan is accountable: every published piece traces back to its brief, topic and campaign, gaps in coverage per topic or funnel stage are reported, and plan-versus-published is visible over time without a spreadsheet.
The Head of Content
The captured pages present Maglr as a design-and-publish tool for interactive publications — white papers, annual reports, digital magazines — with green, orange and red page status indicators and a separate preview-versus-live state. We found no public information on an editorial calendar, briefs, campaign or topic grouping, owners or due dates, and publishing itself is manual: changes reach the live URL only when you click Publish live again. 4 5 6
The SME Marketer
The captured pages describe a publication design tool for white papers, magazines and reports rather than a planning tool, and the closest thing to planning I found is the green/orange/red status each page carries for published, changed or inactive. We found no public information on an editorial calendar, briefs carrying goal and keywords, campaign grouping or deadline and workload views. 4 6
The Localisation Lead
The closest thing to planning on the captured pages is the page status colour scheme — green for published, orange for unpublished changes, red for inactive — which tracks publication state, not editorial work. We found no public information on an editorial calendar, briefs, campaigns, topics, due dates or scheduled publishing; the product is documented as a design-and-publish tool for interactive publications. 6 4
The Web Engineer not rated — no public information
We found no public information on editorial planning: nothing in the captured pages describes an editorial calendar, briefs carrying goal and audience, campaign or topic grouping, or any view of what is due or overdue. The product's own framing is publication design — white papers, annual reports, digital magazines and brochures — rather than scheduled editorial work. 1 4 8
The Data Protection Officer
The captured pages show page status colours (published, unpublished changes, inactive) and the ability to set up review rounds, but we found no public information on an editorial calendar, briefs, campaign or topic grouping, or per-person workload and deadline views. 4 6
The Skeptic
The captured pages show per-page status colours — published and unchanged, unpublished changes, inactive — and use cases such as white papers, annual reports and digital magazines. We found no public information on an editorial calendar, campaigns, briefs, keywords or deadline and workload views. This reads as a publication design tool with page states rather than a planning system. 4 6
Creation, review & approval
Show reasoningHide reasoning
How this is scored
Writing and reviewing content together: editing with comments and suggestions, roles and permissions for internal and external contributors, and an approval trail that records who released which version — published content is a legal statement (UWG, Heilmittelwerbegesetz, the imprint duty).
0 — A single-user tool; content cannot be shared with or reviewed by others.
3 — Several users working on content, with comments or a version history.
5 — Roles and permissions that separate writing from publishing, comments on content, a version history with restore, and an approval or review status before publishing.
8 — Configurable multi-step approval per content type or market, mandatory reviewers (legal, product, brand), inline suggested edits, guest or freelancer access limited to assigned pieces, scheduled publishing that waits for approval, and an audit log of every edit, approval and publish with user and timestamp.
10 — Approval is evidence: the exact version each approver released is preserved and exportable, permissions reach down to field and locale level, and the audit trail is retained for a stated period and available after the contract ends.
The Head of Content
Roles map cleanly onto editing power — a Contributor is limited to the Content view, editing text and media only, and live publishing sits behind admin-granted permission — and review is genuinely supported with comments, settable review rounds, solved-comment handling and a separate preview URL to share for feedback before going live. We found no public information on version history with restore, a formal approval status, mandatory reviewers or an audit log recording who released which version. 4 5 6
The SME Marketer
Review is real: comments (including on the mobile version), review rounds you set up and solve, a design review system and a separate preview URL to collect feedback before anything goes public. Roles and views separate who may only edit text and media (Content), who builds in a grid (Build) and who designs freely (Design), and publishing live is an admin-granted permission. We found no public information on version history with restore, guest access limited for our agency, or an audit trail of who released which version. 4 5 6
The Localisation Lead
The help pages show several roles mapped to editor views, with the Content role limited to text and media edits while live publishing requires permission granted by an admin, alongside comments, review rounds, a separate preview URL for feedback and the ability to solve comments. We found no public information on version history with restore, multi-step approval per market, an audit log of edits and approvals, or retention of approval records after the contract ends. 4 5 6
The Web Engineer
Roles map cleanly to editor views — Contributor edits text and media only, Editor works in grid scenes, Designer has full editing — and live publishing sits behind an admin-granted permission, so writing is genuinely separated from releasing. Comments, review rounds and shareable preview URLs with optional commenting are documented, but we found no public information on version history with restore or an audit log recording which user released which version. 4 5 6
The Data Protection Officer
Roles map to three editor views and live publishing is admin-controlled, with the Content view able to publish a preview only, and comments can be enabled on a separate preview URL with review rounds to review and solve them — that separates writing from publishing. We found no public information on a version history with restore, a formal approval status before publishing, or an audit log recording who released which version. 4 5 6
The Skeptic
Roles are concrete: Super admin, Team leader, Designer, Editor and Contributor each work in a distinct editor view, and the ability to publish live is an admin-granted permission, which separates editing from publishing. Comments, review rounds, solving and re-reviewing comments, comments on the mobile version and a separate preview URL for feedback are all documented. We found no public information on a version history with restore, formal multi-step approvals, scheduled publishing or an audit log of edits and publishes. 4 5 6
Structured content, localisation & export
Show reasoningHide reasoning
How this is scored
Whether content is stored as reusable structure rather than pages: a content model, components shared across channels, German and other locales managed side by side, and the whole repository exportable in a documented format.
0 — Not a content store; the product keeps no content of its own (for example a pure scheduling or analytics tool).
3 — Templates or custom fields for content, a media library, and content in several languages.
5 — A configurable content model or content types with reusable components, locales managed side by side for each entry, and an export of entries in JSON, CSV, XML or a similar documented format.
8 — References between entries, field-level localisation with fallback languages, variants per market or audience, translation workflows with status per locale and named translation-service connectors, and a full export of content, model, locales and assets documented and self-service.
10 — The repository is portable by design: model and content exportable together and re-importable, migration tooling or a CLI documented in both directions, version history included in the export, and no feature that only works while the content stays.
The Head of Content
Content lives as visual scenes assembled from ready-made building blocks and elements, in grid or freeform mode, with text and media replacement for content-only roles. We found no public information on a configurable content model, locales managed side by side or a documented export of entries; translation appears only as an AI exploration and reusable libraries as a post-summer roadmap item. 5 8
The SME Marketer
For my second language this is thin: automatic translation appears only on a list of things being explored, not as a shipped feature, and pages are composed from grid scenes with ready-made building blocks rather than a content model with fields, components and locales. We found no public information on side-by-side locale management, fallback languages or an export of entries in a documented format. 5 8
The Localisation Lead
Pages are assembled from ready-made blocks in grid and freeform scenes, which is reuse at the design level, but the captured pages describe a page builder rather than structured entries, and we found no public information on a content model, locales managed side by side per entry, translation status per language, or a documented export of content and model in any format. Automatic translations appear only on the updates page as an exploration, and shared libraries are announced as upcoming, so both remain future work. 5 8
The Web Engineer
Content is stored as designed scenes — grid or freeform — assembled from building blocks, with text and media assets such as images, video and audio; that is page structure rather than a content model, and we found no public information on configurable content types, locales managed side by side, or a documented export format. Automatic translations appear only as an exploration on the updates page, not as a shipped capability. 3 5 8
The Data Protection Officer
Pages are built as grid and freeform scenes from ready-made building blocks, which gives reusable structure inside a page. We found no public information on a configurable content model, locales managed side by side, translation workflows, or a documented export of the repository in JSON, CSV or a similar format; automatic translation appears only as an announced exploration. 5 8
The Skeptic
Content is designed pages — grid and freeform scenes assembled from ready-made building blocks — which gives block-level template reuse. We found no public information on a configurable content model, locales managed side by side, translation workflows or a documented export of entries, model or assets. The privacy policy instead describes content staying live until the paid licence ends and deletion six months later, with an export path not documented on the captured pages. 2 5 8
Publishing, distribution & integrations
Show reasoningHide reasoning
How this is scored
Getting approved content to where it is read: publishing to websites and channels, a documented API and webhooks, and named connections to the CMS, CRM, analytics, SEO and translation tools a marketing stack already runs.
0 — A closed tool; content leaves only by copy and paste.
3 — Publishing to one website or CMS, and a few named integrations.
5 — Publishing to websites and several channels from one place, a publicly documented API or webhooks, and integrations named for common CMS, CRM or analytics tools.
8 — A versioned API with published rate limits and SDKs, webhooks on publish and change, preview environments, a marketplace or integration directory with maintained connectors, performance data per piece pulled back from analytics, and a public status page.
10 — The platform is a dependable source for every channel: API deprecation policy published, CDN and delivery SLA stated, scheduled and event-driven publishing documented end to end, and content performance attributed per channel without a separate tool.
The Head of Content
A project publishes to a public live URL readable on desktop and mobile, with interactive embeds and a presenter app carrying content into other settings, and the analytics wiring is documented in detail: Google Analytics 4 and Google Tag Manager set per domain, with strict, light and manual consent modes and an anonymous option that skips IP and geo tracking. Named connections are analytics and Zapier for contacts and forms; we found no public information on a documented API, webhooks, or CMS and CRM connectors. 4 6 7
The SME Marketer
Getting content out is covered: publishing live to a coupled domain, a separate preview URL, taking projects inactive, interactive embeds and a presenter app, with Google Analytics 4 (in anonymous mode if wanted), Google Tag Manager and Zapier named as integrations and consent modes for cookies. We found no public information on a documented API or webhooks, so our CRM would hang off Zapier alone. 4 6 7
The Localisation Lead
Approved projects go live on their own domain URLs, with interactive embeds and a presenter app as additional delivery forms, and the help centre documents Google Analytics 4 per domain, Google Tag Manager, Zapier pushes and a consent manager, plus a status page among support resources. We found no public information on a documented API, webhooks, SDKs, rate limits or preview environments, so delivery rests on the vendor's own channels rather than a documented interface. 6 7 4
The Web Engineer
Publishing live to a hosted URL is documented step by step — separate preview URL, manual republish, take-offline — alongside named Google Analytics 4, Google Tag Manager and Zapier connections, interactive embeds and per-project statistics in the dashboard. From an integrations standpoint I have to report that we found no public information on a documented API, webhooks, rate limits, SDKs or a deprecation policy; a Status link does appear among the support resources. 4 6 7
The Data Protection Officer
Projects publish live to their own URL tied to a customer domain, with a separate preview URL, interactive embeds, a presenter app, and named integrations for Google Analytics 4, Google Tag Manager and pushing contacts and forms to Zapier; a Status link is offered in the footer. We found no public information on a publicly documented API or webhooks. 3 4 6 7
The Skeptic
Publishing to the product's own destinations is documented end to end: a live URL on a coupled domain, a separate preview URL, manual republish and a set-inactive control, with interactive embeds on top. Named connections cover Google Analytics 4 per domain, Google Tag Manager, Zapier form pushes, a consent manager with strict mode, and a Status page is listed among support resources. We found no public information on a documented API, webhooks or SDKs on the captured pages. 4 6 7
AI assistance & content rights
Show reasoningHide reasoning
How this is scored
What the platform's AI does with the customer's content and what the customer may do with the AI's: the models and where they run, whether content trains them, opt-out, labelling of generated text under the EU AI Act, and who holds the rights to output.
0 — The vendor states that customer content trains its models with no opt-out, or reserves the rights to AI output for itself.
3 — AI writing features described with what they do, and a general statement on how content is handled by them.
5 — The AI model provider named, a statement that customer content does not train models, and AI features that an admin can switch off.
8 — Model providers listed as subprocessors, EU processing for AI features stated or selectable, retention of prompts and outputs given in days, ownership of generated output assigned to the customer in the terms, generated content markable for EU AI Act transparency, and brand voice or terminology rules applied without training a shared model.
10 — AI is governed and documented: per-feature list of model, provider and processing location, admin controls per role and content type, an audit trail of AI-generated changes, and the output rights and any indemnity written into the contract terms.
The Head of Content
AI is explicitly at the exploration stage — automatic translations, design adjustments from text prompts, desktop-to-mobile conversion and generating a design from PDF, Word or PowerPoint — with an option to always opt out and a stated philosophy that judgment stays with the designer. We found no public information on the models or providers involved, where AI processing runs, whether customer content trains them, retention of prompts and outputs, or who holds rights to generated content. 8
The SME Marketer
The AI features I write with daily are still explorations — automatic translations, prompt-based layout adjustment, desktop-to-mobile conversion and generating a design from PDF, Word or PowerPoint — with an option to always opt out, so nothing is generally available yet and the vendor states that judgment stays with the designer. We found no public information on the models or providers, whether customer content trains them, who holds the rights to generated output, or labelling under the EU AI Act, all of which I need in writing before an assistant drafts a word for us. 8
The Localisation Lead
The updates page lists AI explorations — automatic translations, layout adjustment through text prompts, desktop-to-mobile conversion and generating a design from PDF, Word or PowerPoint — with an option to always opt out, and states they are not generally available. We found no public information on the models or providers used, where AI processing runs, whether customer content trains them, prompt and output retention, or who holds the rights to generated output, and there is nothing on labelling generated content for EU AI Act transparency. 8
The Web Engineer
The AI work is explicitly exploratory — automatic translations, prompt-driven layout changes, desktop-to-mobile conversion and design generation from PDF, Word or PowerPoint — with an opt-out option and a stated commitment to human-led design. We found no public information on model providers, where AI processing runs, whether customer content trains models, retention of prompts and outputs, or ownership rights over generated content. 8
The Data Protection Officer
AI is presented only as explorations (automatic translations, layout changes from text prompts, converting desktop designs to mobile, generating a design from PDF, Word or PowerPoint) with a stated option to always opt out. We found no public information naming model providers, where AI processing runs, whether customer content trains models, prompt retention in days, or who holds rights to generated output — nothing I could sign off on today. 8
The Skeptic
The only AI on record is an exploration list — automatic translations, prompt-driven layout adjustment, desktop-to-mobile conversion, generating a design from PDF, Word or PowerPoint — explicitly not generally available, with a stated option to opt out. The stated position is human-led design, with judgment staying with the designer. We found no public information on model providers, processing location, whether customer content trains models, prompt retention, or rights to generated output. 8
European sovereignty
panel opinion
Show reasoningHide reasoning
How this is scored
Who the contracting entity is, where content, assets and AI prompts are stored and processed, and which subprocessors touch them. Independently sourced by the sovereignty pipeline; dimensions the evidence does not establish are unknown, not non-European.
0 — Vendor, contracting entity and hosting all shown to be outside the EU, with no data processing agreement offered.
3 — A privacy policy and a data processing agreement offered, with hosting or the contracting entity outside the EU or not established.
5 — EU hosting stated for content and assets, with a data processing agreement offered.
8 — EU contracting entity, content, assets and backups stored in the EU on named infrastructure, subprocessor list published with locations and purposes, and AI processing location stated.
10 — Sovereign end to end and evidenced: European ownership, EU entity, every hosting, CDN, AI and support subprocessor European or optional, self-hosting or a European cloud offered, and certifications published.
The Head of Content
All data is stated to be hosted at Amazon Web Services in Frankfurt, with two daily backups plus additional backups in Ireland, and Maglr states it collects no personal data from publication visitors. Cloudflare, Adyen and Crisp are named as subprocessors with their purposes though without locations, and published assets are cached on local servers outside the EU for under 24 hours via Cloudflare. We found no public information on the contracting entity's jurisdiction or a data processing agreement; the vendor address shown is in Breda, the Netherlands. 2 3 8
The SME Marketer
Storage sits on Amazon Web Services in Frankfurt with daily backups and a second backup region in Ireland, Adyen, Cloudflare and Crisp are named as subprocessors with their purposes, and the vendor address is in Breda in the Netherlands. The caveat is disclosed: published content is delivered through Cloudflare's global network with temporary copies outside the EU for under 24 hours, and we found no public information on a data processing agreement or the contracting entity's jurisdiction. 2 3 8
The Localisation Lead
Storage is stated as Amazon Web Services in Frankfurt with two daily backups and additional backups in Ireland, and the privacy policy names Cloudflare, Adyen and Crisp as subprocessors with their purposes. The contracting entity's jurisdiction remains unstated on the captured pages despite a Dutch address in Breda, we found no public information on a data processing agreement or subprocessor locations, and published content is cached on Cloudflare edge servers worldwide for up to 24 hours. 2 3 8
The Web Engineer
All customer data is stated to be hosted at Amazon Web Services in Frankfurt, with two daily offsite backups plus additional backups in Ireland, and a Dutch company address is published; the stated caveat is that published assets are cached worldwide on Cloudflare for under 24 hours. Adyen, Cloudflare and Crisp are named as subprocessors with their purposes but without locations, and we found no public information on a data processing agreement or the contracting entity's jurisdiction. 2 3 8
The Data Protection Officer
Storage is stated at Amazon Web Services in Frankfurt with two daily backups plus additional backups in Ireland, and the privacy policy names subprocessors with their purposes (Adyen for payments, Cloudflare for security and traffic distribution, Crisp for product e-mails); the published address is in Breda, the Netherlands. The captured pages do not establish the contracting entity's jurisdiction or a data processing agreement, and published content is cached on servers outside the EU for up to 24 hours through Cloudflare, so EU-only residence holds for storage with a disclosed, transient exception for delivery. 2 3 8
The Skeptic
The security page states all data is hosted at Amazon Web Services in Frankfurt with two daily backups plus additional backups in Ireland, and an address in Breda, The Netherlands is published. The privacy policy names Adyen, Cloudflare and Crisp as subprocessors with their purposes, and the same pages describe published assets cached on servers outside the EU for under 24 hours via Cloudflare. We found no public information on a data processing agreement, hosting options or the contracting entity's jurisdiction. 2 3 8
Pricing transparency
not rated — the vendor publishes no price
Show reasoningHide reasoning
How this is scored
Whether a buyer can compute the annual cost for their team, locales and traffic from public pages alone — seats and contributor roles, locales, content records, API calls and bandwidth, AI credits, and the plan where approval workflows or SSO begin.
0 — No public prices at all; every plan is a sales conversation.
3 — A public "from" price, a free tier, or one priced plan, with the rest on request.
5 — Prices for each plan public with the billing period (per month or per year) and the seats or main limits each includes.
8 — Every plan priced with seats, locales, records, API and bandwidth limits and overage rates stated, AI usage priced or included explicitly, and the plan that unlocks approval workflows, SSO and audit logs named.
10 — Complete cost computability: annual cost derivable for a given team, locale count and traffic, every add-on and overage priced publicly, contract term and renewal conditions stated, and the cost of exporting or leaving the platform zero or published.
The Head of Content
A pricing page is published with a stated range from 400.00 to 1100.00 EUR, and the tiers are named — Basic, Advanced, Enterprise — with documented feature gates such as freeform editing and all views arriving with Advanced and Enterprise. We found no public information on billing periods, seat counts, usage limits or overage rates for any plan, so the annual cost of a given team is not derivable from the captured pages. 1 5
The SME Marketer
The homepage's structured data shows a range from 400.00 to 1100.00 EUR across Basic, Advanced and Enterprise licences, with freeform design work starting at Advanced, but the captured pages do not state whether those figures are per month or per year, nor what seats, guest users or a second language cost. I cannot compute our annual cost once I add the agency as guests, and the plan where anything like approval workflows or SSO begins is not named anywhere I read. 1 5
The Localisation Lead
The homepage publishes a price range of 400.00 to 1100.00 EUR and a plans page exists, and the help centre names Basic, Advanced and Enterprise licenses distinguished by which editor views and freeform editing they unlock. We found no public information on per-plan prices with billing periods, seat or role counts, content and traffic limits, overages, or where approval, audit and single sign-on capabilities begin. 1 5
The Web Engineer
The plans page publishes a price range from 400.00 to 1100.00 EUR, and the license tiers are named — Basic, Advanced and Enterprise — with documented feature gating such as freeform editing requiring Advanced or Enterprise. We found no public information on per-plan prices together with their billing period, included seats, or content and usage limits, so an annual cost is not computable from the captured pages. 1 5
The Data Protection Officer
The homepage carries a public price range from 400.00 to 1100.00 EUR and a plans page exists, with Basic, Advanced and Enterprise licenses named and their editor-view differences documented. We found no public information on the billing period, seats or limits each plan includes, or add-on and overage pricing, so the annual cost for a given team cannot be computed from the captured pages. 1 5
The Skeptic
A public plans page carries a price range from "400.00" to "1100.00" EUR, with Basic, Advanced and Enterprise named and freeform scenes available only on Advanced and Enterprise. The captured pages state no billing period, seat counts, usage or API limits, overage rates or AI pricing, so an annual cost cannot be computed from public pages. We found no public information on contract term, renewal conditions or the cost of leaving. 1 5
European sovereignty — proven facts
1 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 | — | uncited Report an error |
|---|---|---|---|
| Hosting location |
EU only
unverified
Why unverified?Both pages also disclose that published content is distributed worldwide via a global Cloudflare CDN with temporary copies cached on local servers outside the EU for up to 24 hours, so storage is EU-only while published assets briefly exist elsewhere. |
4/4 pts | 3 Report an error |
| Hosting options | Not determined | — | 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 Maglr
Is Maglr European?
Not determined: the vendor’s pages as captured do not say where Maglr is based.
Where does Maglr store data?
Maglr stores customer data in the EU, per the vendor’s page captured 10 Nov 2026.
Does Maglr have a free plan?
Not stated on the vendor’s pages as of 10 Nov 2026.
What are the best alternatives to Maglr?
As of 19 Nov 2026, the panel rates Kontent.ai (3.5/5), StoryChief (3.5/5) and Scompler (3/5) highest among the other 30 Content Marketing 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 Kontent.ai (EU-Made, Czechia). Ratings are the AI panel’s opinion, formed from public evidence: how scores are made. The full list, with European products first: Maglr alternatives.
Where this could be wrong
- Evidence ages. The oldest capture behind this page is from 10 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. Both pages also disclose that published content is distributed worldwide via a global Cloudflare CDN with temporary copies cached on local servers outside the EU for up to 24 hours, so storage is EU-only while published assets briefly exist elsewhere.
- 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.
- 9 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
- 5 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
- 2 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
- 1 compliance 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
- 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
- 1 support 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
Sources (8)
The pages every claim on this page was read from — each one checked, dated, and kept verifiable.
- 1 Vendor page maglr.com Checked 10 Nov 2026 Details →
- 2 Privacy policy — found from the homepage www.maglr.com Checked 10 Nov 2026 Details →
- 3 Security / trust page — found from the homepage www.maglr.com Checked 10 Nov 2026 Details →
- 4 Creation, review & approval — found from sitemap www.maglr.com Checked 10 Nov 2026 Details →
- 5 Creation, review & approval — found from sitemap help.maglr.com Checked 10 Nov 2026 Details →
- 6 Publishing, distribution & integrations — found from sitemap help.maglr.com Checked 10 Nov 2026 Details →
- 7 Publishing, distribution & integrations — found from sitemap help.maglr.com Checked 10 Nov 2026 Details →
- 8 AI assistance & content rights — found from sitemap www.maglr.com Checked 10 Nov 2026 Details →