NODE 01 · Content Studio | Core CMS

A CMS born out of frustration

We built sites in WordPress for years and grew tired of the same list: updates that break things, plugins that get in each other's way, and arguments about whose fault it is. Content Studio | Core CMS does what a business site needs, and nothing else.

Request a demo response within 1 working day
NODE 02 · The problem

Where you are probably coming from

  1. 01

    The update merry-go-round

    Core, theme and thirty plugins, each with its own rhythm. Miss it once and you fall behind; keep up and you test your own site every month.

  2. 02

    Plugins that clash

    Two extensions that work on their own but not together. One maker points at the other.

  3. 03

    Nobody responsible

    When something breaks it's the theme, or the plugin, or the hosting. Never anything one party can be held to.

  4. 04

    Slowness you can't get rid of

    A page builder that loads twenty files. You can put caching on top, but it only works around it.

NODE 03 · What's inside

Complete, without the ninety percent you never touch

Pages

Managing content

Click where the text is, type, save. No builder with fifty settings per block.

Languages

Multilingual out of the box

No separate translation plugin that duplicates the menu. Our own site runs on it.

Permissions

Roles and permissions

Who may publish what. An editor can't break what they are not allowed to touch.

Versions

Preview and history

See how it will look before it goes live, and go back to yesterday if it wasn't right after all.

Shop

Web shop in the same system

No second system bolted onto the first. What your shop needs to do — payment methods, VAT, stock, returns — we set up for your situation, not a standard package.

API

Open at the back

An API other systems can connect to — headless too, if you want to build the front end yourself.

NODE 04 · Speed

Measured, not claimed

Two sites we built ourselves: our new site on Core CMS, and our own 'outdated' website that we built in WordPress. Same makers, different system. Three measurements per site, clean cache, median, 25 September 2026.

Measurement Core CMS WordPress Note
Largest element in view 732 ms 1980 ms Standard 2500 ms
Fully loaded 778 ms 3734 ms
Server responds 241 ms 202 ms WordPress is faster here
Requests to the server 5 71
Code: CSS and JS 27 KB 1234 KB In 2 versus 44 files

The first byte actually arrives slightly faster with WordPress — that is caching, and anyone can do that. The difference is in what happens after that: fetching and running 44 code files versus 2. No caching can make up for that, because those files have to go through the browser either way.

NODE 05 · Accessible

Meets WCAG 2.1 AA

Since 28 June 2025 the European Accessibility Act applies to web shops and online services, among others. A site that doesn't comply is not just inconvenient for your visitor.

Our output is built for it: contrast, keyboard operation, alternative texts and a structure a screen reader can follow. We test that automatically at every delivery — and because such a test only catches part of the criteria, we can also have a manual check done.

NODE 06 · Integrations

Plugins that already exist

Realworks

Property listings from Realworks

Your listings appear automatically on your own site, in your own design.

Claude

Updating from Claude

You say in plain language what needs to change; it happens in your CMS. Without logging in.

Maps

Interactive floor plans

Clickable areas on an image, each with its own destination.

There is no plugin store where anyone can just put code — that is exactly where the problems come from with other systems. We build the integrations. Want to build something yourself or bring in your own developer? That's possible: on your terms and under your responsibility, just like any other custom code in your environment.

All plugins →
NODE 07 · Ownership

Who owns what

From you

Your content and your data

Everything you put in is yours. Always exportable, in a format that can be read elsewhere — your products, orders and media too.

From us

The system itself

Core CMS is our intellectual property and stays that way. You use it, you don't buy it. Your own custom work and your own plugins are a different story; we put that in writing per assignment.

Leaving

Is possible, and you should know that up front

You get your domain with the transfer code, your data in an export. We don't hold on to anything to keep you.

NODE 08 · Limits

When you had better not choose this

  1. 01

    You want a simple brochure site

    Five pages, no integrations, no editorial team. WordPress is cheaper for that, and we would rather say so ourselves than have you find out later. We then simply host and maintain that WordPress site for you — see maintenance and hosting.

  2. 02

    You need one specific plugin

    If it only exists for WordPress and you can't do without it, we either rebuild it or you stay where you are. We will tell you honestly what that costs.

  3. 03

    You want to work in the core yourself

    Core CMS is closed. If you want to modify the system itself, it isn't a fit — although you can build your own plugins for it.

NODE 09 · Price

What it costs

From € 50 per month excl. VAT, including hosting of your website.

No separate server bill, no separate maintenance agreement for the system itself. That amount covers an average business website. Not an extensive web shop: there the specifications determine the price, and we calculate it up front. Integrations and custom work are separate.

Support: response within four hours during office hours, Mon–Fri 9.00–17.00. A daily backup, kept in a different Dutch data centre from the one your site runs in, and at least monthly we restore one to see whether that works. Outside office hours: with an SLA.

Where it runs: in DigitalOcean's Amsterdam data centre; the daily backup is kept in a different Dutch data centre. So your data stays in the Netherlands — not just the live site, the copies as well, and not in the same place. That belongs here because hosting is included in the price: you are also buying a place where your data lives.

Switching

Moving off WordPress is the most common reason. We bring along pages, media and URL structure — the latter is what protects your rankings in Google. What doesn't come along are plugins without an equivalent; we name those up front.

Two to three weeks on average. That is longer than taking over a site as it is, and rightly so: in a migration the content moves to a different system, and we check that page by page.

NODE 10 · Contact

Half an hour costs you nothing

Tell us which process takes the most manual work. We will tell you honestly whether AI is the right answer — and sometimes the answer is: fix your integration first. Then you have that too, without an invoice.

Let's talk about AI

or call 040 340 0010

response within 1 working day