{ "id": "sanity-vs-contentful", "ids": [ "sanity", "contentful" ], "title": "Sanity vs Contentful: dataset access and content models", "heading": "Sanity vs Contentful", "kicker": "CMS buying comparison", "deck": "Compare Sanity and Contentful by publishing scope, licensing, migration work and the operating responsibilities of a live site.", "description": "Compare Sanity and Contentful by publishing scope, licensing, migration work and the operating responsibilities of a live site.", "answerHeading": "Which CMS model fits the publishing team?", "answer": "Compare Sanity and Contentful through content structure, editing governance and production access. Both supply managed content services with a separate frontend. Sanity Free includes public-only datasets and constrained roles. Contentful Free is restricted to learning and testing rather than commercial production. Choose the eligible service model and access boundary before investing in a custom editor or migration.", "checkedAt": "2026-10-15", "researchTag": "CMS buying comparison", "researchLimit": "Product capabilities and access terms are compared. The evaluation briefs are hypothetical; they do not imply a hands-on benchmark or measured vendor result.", "datasetDescription": "Seven CMS differences, four hypothetical buying briefs and a four-row migration acceptance checklist.", "type": "workflow-buying", "rows": [ [ "Content service", "Hosted real-time content database", "Hosted structured-content platform" ], [ "Editing setup", "Customisable Sanity Studio", "Platform editorial tools and content models" ], [ "Data organisation", "Datasets and schemas", "Spaces, environments and content types" ], [ "Free data access", "Public datasets only", "Learning/testing use only" ], [ "Free business assumption", "Assess public data, roles and usage carefully", "Commercial use excluded on current Free plan" ], [ "Governance decision", "Roles, dataset privacy and plan features", "Roles, locales, spaces and plan features" ], [ "Delivery scope", "Frontend and hosting supplied separately", "Frontend and hosting supplied separately" ] ], "scenarios": [ { "name": "Public marketing site", "question": "Which information is actually safe to expose?", "left": "Review every field before choosing a public dataset.", "right": "Scope a commercial subscription for the intended live service.", "note": "A hidden frontend component does not make publicly queryable content private." }, { "name": "Custom editing interface", "question": "Who maintains the editor as schemas change?", "left": "Prototype the required Studio customisations.", "right": "Prototype the required models and supported editorial extensions.", "note": "Evaluate editor task completion rather than comparing only API examples." }, { "name": "Multiple markets", "question": "Can content be reused without accidental language changes?", "left": "Model locale relationships and required permissions.", "right": "Map locale and role entitlements in the selected plan.", "note": "Demonstrate an approval and rollback path for one translated update." }, { "name": "Application integration", "question": "How will content changes reach the live experience?", "left": "Specify query, preview and delivery behaviour for the application.", "right": "Specify API, preview and delivery behaviour for the application.", "note": "Give the team an observable way to diagnose stale content and failed builds." } ], "exampleTable": { "caption": "Proposed CMS acceptance checklist; these are evaluation requirements, not measured product scores.", "headers": [ "Requirement", "Evidence to collect", "Acceptance condition" ], "rows": [ [ "Content migration", "A sample export and import covering references, media and languages", "The approved sample preserves meaning and editable structure" ], [ "Publishing control", "A demonstration using the intended editor and reviewer permissions", "Unauthorised changes cannot reach the live site" ], [ "Delivery ownership", "An architecture naming CMS, frontend, hosting and integration owners", "Every production dependency has a support and recovery owner" ], [ "Commercial scope", "A quote for the required licence, capacity and operating services", "The estimate includes renewal and implementation responsibilities" ] ] }, "sections": [ { "id": "visibility-boundary", "title": "Treat dataset visibility as an architecture decision", "navLabel": "Treat dataset visibility as an architecture decision", "paragraphs": [ "A public dataset should contain only information that may be public, including records not currently linked from the website. Removing a field from a page template does not establish a private storage boundary. Decide which data belongs in the CMS and which belongs in another protected service.", "Sanity Free has public-only datasets. If the content model requires private data or more specialised editorial roles, resolve the commercial plan before onboarding editors. For Contentful, establish a commercially eligible plan separately from any successful learning project." ] }, { "id": "editor-maintenance", "title": "Compare the editor that the team will actually use", "navLabel": "Compare the editor that the team will actually use", "paragraphs": [ "Prepare a realistic model containing reusable content, linked media, several content statuses and a translated record. Ask an editor to find a record, change it safely, preview the result and request approval. This makes the cost of custom Studio work or platform configuration visible.", "Include the lifecycle of schemas and integrations in the estimate. A field change can affect the editor, frontend queries, previews and exports. Require a review process that identifies all those consumers before a developer changes a production model." ] } ], "faqs": [ { "question": "Are Sanity Free datasets private?", "answer": "No. Current Free entitlements specify public-only datasets. A frontend that omits a field is not a substitute for dataset access control." }, { "question": "Can Contentful Free support business production?", "answer": "Current Free usage terms permit learning and testing, not commercial use. Plan a commercially eligible subscription." }, { "question": "Does either CMS host the whole website automatically?", "answer": "Both provide content services. The website or application frontend, its deployment and its operating costs require a separate plan." } ], "sources": [ { "url": "https://www.sanity.io/pricing", "facts": "Current Sanity product, access or operating scope used in this comparison." }, { "url": "https://www.sanity.io/docs/studio", "facts": "Current Sanity product, access or operating scope used in this comparison." }, { "url": "https://www.contentful.com/pricing/", "facts": "Current Contentful product, access or operating scope used in this comparison." }, { "url": "https://www.contentful.com/help/admin/usage/usage-limit/", "facts": "Current Contentful product, access or operating scope used in this comparison." } ], "relatedLinks": [ { "path": "/guides/cms-migration-checklist/", "title": "Plan a CMS migration without losing key content" }, { "path": "/guides/software-total-cost/", "title": "Build the complete software cost estimate" }, { "path": "/categories/headless-cms/", "title": "Browse headless CMS products" } ] }