Your CMS vendor got acquired. That is an uncomfortable email to read on a Monday, and the honest answer to "what do we do now" is: probably nothing urgent, but you do need a plan.
Here is what we could verify directly from Payload's own pages, what it means in practice, and how to decide whether to stay put or start looking.
What actually changed
Payload has joined Figma. Payload's Cloud update page states that "deployment of new projects is currently paused," while existing Cloud projects "will continue running as normal." The same page confirms that Payload remains a self-hosted solution and that the open source core continues under Figma. It also notes that Cloud customers will need to migrate eventually.
Separately, payloadcms.com/pricing returned HTTP 404 when we requested it on September 1, 2026. The URL that now carries the Cloud information is payloadcms.com/cloud-pricing, which serves the acquisition notice rather than a price list.
Sources, both fetched September 1, 2026:
What did not change
This part matters just as much, and a lot of the commentary is getting it wrong:
- Payload is not dead. The open source project continues, with Figma stating a commitment to it.
- Self-hosted Payload is still a real, good product. If you run it yourself, your setup works today exactly as it did last month.
- Existing Cloud projects keep running. There is no shutdown date announced for them.
- Payload says no pricing changes are currently planned for existing Cloud customers.
If you self-host Payload and you are happy, there is no fire. Close this tab and get on with your week.
Who actually has a decision to make
Three groups are affected, in descending order of urgency.
1. You were about to adopt Payload Cloud. This is the group with a real, immediate problem. The managed path you were planning to buy is not open to new projects. You either self-host, or you pick a different managed platform.
2. You are running on Payload Cloud today. You are fine right now. Payload has said existing projects continue and that migration will be needed eventually, without a published date. The reasonable move is to find out what self-hosting your instance would cost and how long it would take, so the number exists before you need it. Do the spike now while there is no deadline attached to it.
3. You self-host Payload. Nothing operational changed. The question is strategic: are you comfortable with the roadmap of an open source project now owned by a design company whose core business is not content infrastructure? Reasonable engineers land in different places on that. Figma has committed to the OSS core, and Payload has a real community. It is a judgement call, not an emergency.
Acquisition risk is a legitimate reason to migrate
It is also frequently overstated, so it is worth being precise about what the risk actually is.
The risk is rarely that the software disappears. Open source code does not evaporate on acquisition. The risk is slower and less dramatic:
- Roadmap drift. Features that serve the acquirer's strategy get built. Features that serve your use case wait.
- The hosted tier is the first thing to go. Running a managed cloud is expensive and operationally distracting. It is the most common casualty of an acquisition, which is exactly the pattern here.
- Maintainer attention shifts. The people who answered your GitHub issues now have a different employer's priorities.
- Your escape hatch becomes work. "We can always self-host" is true and also a project with a headcount cost.
Against that, the honest counterweight: acquisitions frequently mean more resources, not fewer, and Figma is a well-capitalized company with a genuine interest in the design-to-content pipeline. Payload may well be better resourced a year from now.
The useful question is not whether the acquisition is good or bad. It is whether your team can absorb the operational work if the hosted path stays closed. If the answer is yes, stay. If the answer is no, you need a managed platform.
If you need a managed platform
This is where Cosmic fits. We are a fully managed, API-first CMS, so the infrastructure question does not land on your team at all.
No servers. There is no application host to run, no MongoDB or Postgres instance to operate, no upgrade path to schedule, no backups to configure. You create a Bucket, model your content, and call the API.
REST API and TypeScript SDK. Content access is a few lines:
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);
Everything in the SDK is available over the REST API.
Media is included. An imgix-backed CDN for optimized global delivery, plus AI image and video generation. No separate storage bucket or CDN bill.
AI agents are part of the platform. Team Agents you can talk to in Slack, WhatsApp, and Telegram. Content Agents that generate and bulk-manage content on a schedule. Code Agents that connect a GitHub repo and open pull requests. Computer Use Agents for browser automation. An MCP Server is included, so MCP-speaking tools can read and write your content directly.
Your Payload model ports over conceptually. Payload collections map onto Cosmic Object Types, and fields map onto metafields. The frontend swap is replacing your Payload local API or REST calls with SDK calls.
Where staying on Payload is the better call
We would rather you pick correctly than switch and regret it. Self-hosted Payload is the stronger choice when:
- The CMS must run inside your own VPC or on your own hardware for compliance reasons
- You want the admin UI in your repository, versioned and modified as application code
- You need direct database access and full control of the data layer
- Your team already operates Next.js infrastructure and wants the CMS in the same deployment
- Owning the source matters to you more than offloading the operations
Those are good reasons. If any of them are hard requirements, self-host Payload and ignore the rest of this page.
What Payload costs now
A lot of people are searching for this, so here is a straight answer.
Self-hosted Payload: the core is free and open source. Your actual cost is infrastructure and engineering time: application hosting, a MongoDB or Postgres instance, object storage or a CDN for media, monitoring, and the hours spent on upgrades and incidents. Those line items are real even when the license is $0, and they are the numbers to compare against, not zero.
Payload Cloud: there is no public price list to point you at right now. payloadcms.com/pricing returned a 404 on September 1, 2026, and payloadcms.com/cloud-pricing currently serves the Figma acquisition notice instead of pricing. New project deployments are paused. Existing customers should refer to Payload's own communications, since Payload has said no pricing changes are currently planned for them.
We are deliberately not quoting historical Payload Cloud prices here. They describe a product you cannot currently buy, and repeating them would be misleading.
Cosmic, verified against cosmicjs.com/pricing on September 1, 2026:
| Plan | Price | Buckets | Team members | Objects |
|---|---|---|---|---|
| Free | $0/month, forever | 1 | 2 | 1,000 |
| Builder | $99/month | 2 | 3 | 5,000 |
| Team | $299/month | 3 | 5 | 20,000 |
| Business | $499/month | 5 | 10 | 50,000 |
| Enterprise | Custom | Custom | Custom | Custom |
The Free plan needs no credit card. Additional team members are $29/user/month. Optional add-ons are $99/month each, or $199/month bundled.
Side by side
Every Payload row links to a Payload page we fetched on September 1, 2026.
| Cosmic | Payload | |
|---|---|---|
| Hosting model | Fully managed | Self-hosted (source) |
| Managed cloud open to new projects | Yes | Paused (source) |
| Open source core | No, hosted product | Yes, continues under Figma (source) |
| You operate the database | No | Yes, MongoDB or Postgres (docs) |
| Public pricing page | Yes | /pricing returned 404 on Sep 1, 2026 |
| Free tier | Yes, no credit card | Core free to self-host |
| Media CDN included | Yes, imgix-backed | Via storage adapters (docs) |
| Built-in AI agents | Team, Content, Code, Computer Use | See Payload docs for current features |
Common questions
Is Payload CMS shutting down?
No. Payload joined Figma, and Payload states that the open source project continues and that existing Cloud projects keep running. New Cloud project deployments are paused.
Can I still use Payload for free?
Yes. The open source core is free to self-host.
Do I have to migrate off Payload Cloud?
Payload has said existing projects continue running as normal and that migration will be needed eventually. No public deadline has been announced. Check Payload's Cloud update page for the current position.
What is the closest managed equivalent to Payload?
If what you valued was the hosted convenience rather than owning the codebase, a managed API-first CMS like Cosmic covers that. If you valued the code-first admin panel living in your repo, self-hosted Payload remains the closest thing to itself.
How hard is a migration to Cosmic?
Collections map to Object Types and fields map to metafields, so the content model ports conceptually. The work is the data move plus swapping frontend queries to the SDK. We wrote up the process in How to Migrate from Payload CMS to Cosmic. Migration assistance is available on Business and Enterprise plans.
What teams say
"Cosmic is: us never having to ask a developer to change anything on the backend of our website."
Maximilian Wuhr, Co-Founder at FINN
Cosmic is backed by Y Combinator (W19).
Try it
The Free plan is genuinely free and needs no credit card, so you can model your content and see whether it fits before making any decision about Payload.
Start for Free Book a Demo with Tony
Related
- Payload vs Cosmic
- How to Migrate from Payload CMS to Cosmic
- Sanity Alternative
- Contentful Alternative
- Drupal Alternative
Last verified: September 1, 2026. Payload claims on this page were checked in the same session against payloadcms.com/cloud-pricing and payloadcms.com/blog/payload-is-joining-figma; payloadcms.com/pricing returned HTTP 404. Cosmic pricing was checked against cosmicjs.com/pricing.
