corpusctl vs Contentful: what changes when nobody meters your traffic
Contentful bills per API call, record and user. corpusctl serves reads from the edge, so there is no call to meter. An honest side-by-side.
Other languages:TürkçeDeutschFrançais简体ä¸æ–‡æ—¥æœ¬èªžItaliano
Contentful is a good product. It is also a product that charges you more the better your content performs — and, since June 2026, a product owned by Salesforce.
Both of those facts should be in the room when you choose.
The pricing model is the whole argument
Contentful meters. API calls, records, users, spaces, locales — each is a line with a limit, and each limit has an overage price above it. The model is internally consistent and easy to bill against. It has one consequence people discover late:
A successful launch is indistinguishable from a billing incident.
The day a post gets picked up, your API call count goes up. Nothing about your content changed, nothing about your infrastructure changed, and nothing about the work you did changed. Only the number of people who read it changed — and that is the number on your invoice.
corpusctl does not have that line, because it does not have the call.
When you hit publish, the build pipeline writes the rendered content to an immutable, hash-addressed file in object storage and refreshes a manifest. The visitor's client resolves the slug to a manifest shard, then fetches that immutable address from the nginx edge cache. Two HTTP requests, both cacheable for thirty days, neither of which touches the API or PostgreSQL.