Cosmic vs. Payload

Payload vs Cosmic: self-hosted code vs a managed content platform

Payload and Cosmic can both power a Next.js site. They start from opposite assumptions.

Payload is an open-source CMS you run as a Next.js application. Collections are TypeScript. The admin UI is generated from your schema. The database is MongoDB or Postgres. That is a strong fit when the CMS should live in your repo.

Cosmic is a fully managed headless CMS. You model content in the dashboard (or via API, MCP, or agents), query it with the REST API and TypeScript SDK, and skip the database, deploy pipeline, and patch cycle.

Payload joined Figma, and Payload Cloud paused new projects

If you are evaluating Payload as a managed service, this changes the decision.

Payload announced that it joined Figma. On Payload's Cloud update page, the team states that deployment of new projects is currently paused, while existing Cloud projects continue running as normal. The same page confirms Payload remains a self-hosted solution, so you can bring the app to any hosting provider, and that the open-source core continues under Figma. Cloud customers will need to migrate eventually.

Sources: Payload Cloud Update and the announcement.

If you want a managed content platform you can start on today, that is what Cosmic does. See the longer write-up: Payload CMS Alternative.

AI: four agent types vs application code you write yourself

Payload gives you a TypeScript app you can extend however you want, including calling AI APIs from hooks or custom endpoints. That is flexibility, not a productized agent layer.

Cosmic ships agents as part of the platform:

Content Agents create, edit, and manage content. Give an agent a topic and it can research, write, generate images, and save a draft. Run them on a schedule.

Code Agents connect to GitHub, read the repo, commit, branch, and open pull requests.

Computer Use Agents browse the web, fill forms, and capture screenshots for research, QA, or monitoring.

Team Agents connect to Slack, WhatsApp, and Telegram so the team can request content from chat.

Multi-agent workflows chain those together. The MCP server lets Cursor, Claude, and other MCP clients read and write the same bucket.

Developer experience

Payload: define collections in TypeScript, run Next.js, point at MongoDB or Postgres, deploy the app. Access control and custom endpoints are code. The feedback loop is the same as the rest of your Next.js stack.

Cosmic: create a Bucket, define Object Types, query with @cosmicjs/sdk. No database, no Docker, no schema migrations. Agents, MCP, and the CLI can create content and types without opening the dashboard.

import { createBucketClient } from '@cosmicjs/sdk'

const cosmic = createBucketClient({
  bucketSlug: 'your-bucket-slug',
  readKey: 'your-read-key',
})

const { objects: posts } = await cosmic.objects
  .find({ type: 'posts' })
  .props(['title', 'slug', 'metadata'])
  .depth(1)

Pricing

Cosmic

No credit card on Free. Additional team members are $29/user/month. Full pricing.

Payload

The core is free and open source. That is a real advantage if you want to self-host. There is no public managed-tier price for new customers, and Payload Cloud is not accepting new project deployments.

Self-hosting cost is infrastructure plus engineering time: application host, MongoDB or Postgres, object storage or a CDN, monitoring, and upgrades. Compare against your actual cloud bill, not against $0.

Why teams choose Cosmic over Payload

You can start today without standing up a stack. Payload Cloud is paused for new projects. Cosmic is a hosted API you can sign up for in minutes.

AI agents are product, not a weekend project. Content, code, computer use, and chat agents ship with the platform. Cosmic's AI runs on Claude.

Media is included. imgix-backed CDN, plus AI image and video generation. No separate storage account to wire up.

MCP and agent signup. Connect Cursor or Claude to a bucket, or let an agent provision a project for someone who has no Cosmic account yet.

Collections map cleanly onto Cosmic Object Types. Step-by-step: How to migrate from Payload CMS to Cosmic. Related: Payload vs Strapi.

Why teams choose Payload over Cosmic

The CMS is application code. Admin UI, access control, and hooks live in the repo and deploy with the app.

Open source and self-hosted. Audit the core, run it in your VPC, keep the database you already operate.

Direct database access. MongoDB or Postgres is yours. If that is a hard requirement, self-hosting is the right answer.

"Cosmic is: us never having to ask a developer to change anything on the backend of our website." Maximilian Wuhr, Co-Founder at FINN.

Start for free or book a meeting with Tony.