What is Payload?
Payload is an open-source content management system and application framework built with TypeScript and Next.js. Developers define the content structure in code; Payload provides the editing interface, APIs, authentication and access controls around it.
“Headless” means the content is separate from its presentation. Your website can have a completely bespoke design, and the same content can serve an app or another channel. Payload itself runs within Next.js; a separate frontend can consume its APIs.
What your content team gets
Editors work in a browser-based admin panel. The interface can be tailored to your content: articles, products, people, events or reusable page sections. Your team can update the fields and layouts prepared for them without editing code.
Drafts, version history and previews support day-to-day publishing. Live Preview can show a page alongside its editing fields, including changes before they are published. Your implementation team configures this connection and the editing experience.
Before signing off the build, ask to try a real task: create a page, replace its image, preview it on mobile and publish it. That is a useful way to judge whether the CMS has been shaped around your team.
Where Payload fits
Payload is worth considering when you need a custom website, structured content shared across brands, or a product with its own content and business logic. Its use cases extend to commerce, internal tools and digital asset management.
For a small site that fits comfortably into a ready-made website builder, compare the delivery approach before choosing a CMS. Start with what your editors and visitors need, then decide how much flexibility your project will use.
Hosting and ownership
A production setup includes the Payload application, a supported database and storage for uploaded media. These can run on infrastructure chosen for your organisation. The frontend may share the application or be hosted separately.
Your agency can handle the setup and ongoing support. Agree who controls the repository and hosting accounts, where data is stored, and who looks after updates, monitoring, backups and recovery. Put those responsibilities in the proposal so the handover is straightforward.
Payload’s deployment guide ↗What belongs in the budget
Separate the implementation fee from recurring services. A useful agency quote covers design, the content model, editorial setup, integrations, migration, testing and launch. Hosting, support and any paid features should be listed with their own assumptions.
For a migration, include content and media volumes, old URL redirects and checks after launch. For editorial work, specify the page sections, languages and approval process your team needs. This makes competing quotes much easier to compare.
Choose a team for your kind of project
Look for relevant work and ask who will actually deliver yours. A newsroom, a multi-brand platform and a membership product have different requirements, even when they use the same CMS.
This directory lets you filter by project experience and compare up to three agencies. You can save the shortlist as a PDF and add a separate set of agency interview questions for your first calls.
Product documentation checked 1 October 2026. This guide is published by WAYF; it is not official Payload documentation.