Sanity vs Strapi

Sanity

A visual editorial calendar exists as a Studio plugin with schedule, reschedule and unschedule actions, but the captured page notes the plugin is deprecated, tied to the deprecated Studio v2, and it does not perform publishing by itself — the documentation advises an external cronjob or webhook script to fire the publish event. Current planning strength sits in Editorial Workflows, which shows stages, assignments, actions and history beside the documents people edit. We found no public information on campaign grouping, briefs carrying goal, audience and keywords to the writer, workload or deadline views per person, or coverage-gap reporting; briefs appear only as a do-it-yourself schema example for image production.

Strapi

We found no public information on editorial planning: the campaign-management page, the pricing page and the review-workflow documentation confirm no calendar, campaign grouping, briefs, due dates or workload views. The closest facts are publishing releases and server cron jobs, which are delivery mechanics rather than a view of what is due, late or missing.

Sanity

Comments and Tasks ship on all paid plans, stored in a parallel dataset with documented permission requirements, and Editorial Workflows adds configurable stages, assignments and durable history that can be driven from the CLI or custom interfaces. A complete history of all changes to a dataset, including deleted documents, is retained for a plan-dependent period. The full audit trail with the History API, custom roles and access control, and SAML single sign-on are listed as Enterprise-plan inclusions, and we found no public information on mandatory reviewers, freelancer access limited to assigned pieces, or scheduled publishing that waits for approval.

Strapi

The review machinery is real and documented: any number of custom stages per content type, per-stage role permissions governing who can move content, assignees, and a required stage that blocks publishing — with stage, assignee and workflow changes automatically written to audit logs. It all lives on the Enterprise plan, though, with content-history retention shown as 14 days on Growth and 'custom' on Enterprise, and we found no public information on inline comments, suggested edits, or guest and freelancer access limited to assigned pieces.

Sanity

Content lives as structured JSON in the Content Lake behind a model defined in TypeScript or JavaScript, with references between entries, unlimited content types and unlimited locales on every plan, plus variants for A/B testing and one-click AI translation described. On exit, the terms promise subscriber data in Sanity's standard database export format within thirty days of termination, with no obligation to maintain data past that point. We found no public information on field-level localisation with fallback languages, translation workflows with status per locale and named translation-service connectors, or documented re-importable migration tooling in both directions.

Strapi

The export is the strongest documented part: a command-line export ships content, relations, assets, schemas and configuration in documented formats, self-service, with content-type filtering and automatic splitting of large datasets, and import and transfer are listed alongside it. The model side holds up too — components, dynamic zones, six relation types, custom fields, unlimited locales with per-content-type internationalization. We found no public information on field-level localisation with fallback languages, translation workflows with status per locale or named translation connectors, and the export expressly leaves out admin users and API tokens; version history's place in the export is not stated.

Sanity

This is API-first delivery: GROQ and GraphQL, a Live CDN, GROQ-powered webhooks, a CLI and named framework integrations from React and Next.js through Astro and Eleventy, with content consumable by anything that can consume an API. The named integrations are delivery frameworks rather than CRM or analytics tools, and the uptime SLA appears as an Enterprise-plan inclusion. We found no public information on published API rate limits, a public status page, an API deprecation policy, or performance data pulled back per piece from analytics.

Strapi

The API story is unusually well documented: REST and GraphQL endpoints generated per content type, an OpenAPI specification, bearer-token authentication with content private by default, a client library, and webhooks whose event semantics are spelled out down to which events carry fully populated entries — plus a marketplace of reviewed plugins. We found no public information on published rate limits, a public status page, delivery SLA terms beyond an Enterprise support mention, or content performance pulled back from analytics; the named integrations are frontend frameworks rather than CRM or analytics connectors.

Sanity

The AI terms name OpenAI, L.L.C., Anthropic, PBC, Pinecone Systems Inc. and Google Inc. as third-party providers receiving input data, and state that all configurations explicitly prohibit or disable model training on data transferred to them, with uploaded data possibly persisting for a few days in provider archives and caches. Usage is metered in AI credits at $0.05 PER AI CREDIT, with agent queries and actions costed at 4 and 2 credits and monthly allocations that expire without rollover. We found no public information on ownership of generated output assigned in the terms, admin-level switch-off of AI features, EU processing locations for AI, or marking of generated content for EU AI Act transparency.

Strapi

The AI terms are candid where it counts: input is transmitted to third-party AI provider APIs, output 'might not be copyrightable' by the customer and 'might be the same or similar output provided to Strapi or a third-party AI provider', the integration is as-is with warranty and SLA excluded, and termination can come without notice or refund. We found no public information on the model provider's name beyond a pointer to the privacy policy's provider list, whether customer content trains models, where AI processing runs, retention of prompts and outputs, an admin off-switch, or EU AI Act labelling of generated text. The one governance hook is a bring-your-own-AI-key topic in the documentation, with credits that reset monthly and overages billed monthly in arrears.

Sanity

A data processing addendum is offered, the privacy policy runs under Norwegian and EU GDPR with standard contractual clauses for transfers outside the EEA, and content is processed on Google Cloud Platform with the server region not stated, while generative AI input data goes to the US providers named in the AI terms. The agreement is governed by California law with exclusive venue in the state courts of San Francisco. We found no public information on EU hosting for content and assets, a subprocessor list with locations and purposes, or a self-hosting or European cloud option.

Strapi

The agreement is with Strapi Inc., a Delaware corporation, under California law, while the privacy policy names a Paris address and an Article 27 GDPR representative and states primary storage in the United States and the EEA, with region selection on the cloud and self-hosting offered for full control over data residency. A third-party provider list is published and SOC 2 and GDPR compliance are claimed with breach-notification procedures. The captured pages give no subprocessor locations, ownership is not established, and the AI processing location is not stated.

Sanity

Free at $0 and Growth at $15 PER SEAT / MONTH are public with the billing period, unlimited locales and content types on every plan, viewer seats free, and overage rates stated for API requests ($1 PER 25K), CDN requests ($1 PER 250K), bandwidth ($0.30 PER 1GB), assets ($0.50 PER 1GB), documents ($299 FOR 50K IN TOTAL), embeddings and AI credits ($0.05 PER AI CREDIT), with SSO, the audit trail and the SLA named as the Enterprise plan. The Enterprise plan itself is CUSTOM PRICING, invoice payment and annual billing are Enterprise-only, and the terms reserve the right to change AI consumption rates at any time with immediate effect, alongside one-year auto-renewing terms with sixty days' non-renewal notice. We found no public information on the cost of the export after termination.

Strapi

Community is 'Free Forever' and Growth is '$45 per month' with 'Includes 3 seats (+$15/month/seat)', single sign-on is a '$150 /month (+$50/month/seat)' add-on, and AI is explicitly priced: 1,000 credits per month on Growth, 'Additional credits: +$1.50 per 100 credits', overages billed monthly in arrears with a 15-day dispute window and no rollover. Locales, entries and API calls are unlimited on the priced plans, so the third locale and the API overage never arrive on the invoice. The gap is Enterprise — where review workflows and audit logs live — which carries no public price, and the offline-licensing and premium-support add-ons are named without figures; taxes are added at checkout.