Umbraco Heartcore
Headless edition of the Danish Umbraco CMS, sold from €60 per month with REST, GraphQL and Azure hosting
Quick Overview
| Company | Umbraco A/S |
|---|---|
| Category | Headless CMS |
| Headquarters | Odense, Denmark |
| Founded | 2014 |
| EU Presence | Yes - Denmark (EU) |
| Data Location | Umbraco Cloud on Azure; region not stated on the pages checked |
| Open Source | No |
| GDPR Compliant | Yes |
| Self-Hosting | No (the Umbraco CMS itself is open source; Heartcore is a hosted service) |
| Main Features | REST API, GraphQL API, preview API, webhooks, Umbraco Forms, CDN through Cloudflare, multiple environments, Umbraco Cloud hosting |
| Pricing | Starter €60, Standard €300, Professional €1,100 per month; Enterprise on request |
| Best For | .NET teams and agencies that already know Umbraco and want a managed headless backend |
| Replaces | Contentful |
Detailed Review
Heartcore takes the Umbraco back office, which the vendor says has been used on more than 730,000 websites, and runs it as a managed service that exposes content only through APIs. Umbraco A/S is registered in Odense, Denmark, and its general terms name it as the contracting party.
Teams get a content delivery layer without maintaining a separate codebase, because the vendor operates the back office and the API for them.
What the Plans Include
Four plans are published: Starter at €60, Standard at €300 and Professional at €1,100 per month, plus Enterprise on request. Starter has one environment, one language and one user role, while higher plans have unlimited languages and roles and two or three environments.
Fair-use limits cover data transfer (up to 50, 600 and 2,000 GB across the three priced plans) and API rate limits of 25, 50 and 75 requests per second.
APIs and Preview
Content is exposed through a managed REST API, and a built-in GraphQL endpoint lets front ends fetch exactly the fields they need. A preview API shows editors unpublished content on every connected platform, and webhooks post to a URL you define when content changes.
Delivery and Hosting
Delivery runs through a Cloudflare CDN, and hosting is on Umbraco Cloud, which the vendor describes as Azure-based with automatic upgrades included.
Limitations to Consider
Heartcore is a hosted service only, so you cannot run the headless edition on your own servers, and the Starter plan allows a single user role and a single language. The cloud region is not stated on the pages checked. Teams not working in the Umbraco ecosystem will find fewer community resources than around Storyblok, and the jump from Standard (€300) to Professional (€1,100) is steep.
Who Should Use Umbraco Heartcore
Agencies and in-house teams, especially on .NET, that know Umbraco and want a managed headless backend from a Danish A/S with euro pricing.
Pros and Cons
Pros
- Prices published in euros
- REST and GraphQL APIs
- Preview API for editors
- Built on the long-running open-source Umbraco core
- Danish A/S with a clear contracting entity
Cons
- Hosted only
- Starter limited to one language and one user role
- Steep step from €300 to €1,100
- Cloud region not stated on pages checked
Alternatives to Umbraco Heartcore
Other European headless cms worth comparing before you decide:
Prepr
Netherlands · Headless CMS with built-in personalization and A/B testing
Caisy
Germany · Stuttgart-built CMS with typed GraphQL API and live co-editing
Squidex
Germany · MIT-licensed event-sourced CMS, cloud hosted in Frankfurt
Storyblok
Austria · Headless CMS where editors work in a visual page editor
See all European headless cms or compare them directly against Contentful on our alternatives page.
Frequently Asked Questions
Umbraco CMS is the open-source system you host yourself. Heartcore is the managed headless edition: the vendor runs the back office and exposes content through REST and GraphQL APIs.
The pricing page lists Starter at €60, Standard at €300 and Professional at €1,100 per month, with Enterprise on request.
The contracting party is Umbraco A/S in Denmark, which is within the EU. The pages checked do not state a hosting region, so confirm that in the data processing agreement.