Give them the admin.
Let clients manage their content in the site’s Payload CMS. A familiar admin experience for pages, posts, products and media, with your team looking after the site.
Your clientCMS admin
For developers
Your next project.
Your actual code.
A modern stack you can work with, a CMS you can extend, and an AI that can help across the application. Get past the repetitive rebuild and into the work that makes your project different.
Try it on a client site right now.
Your clients. Your call.
Let clients update their site.
Or manage it for them.
You decide how clients work with their website. Give them a familiar CMS admin, invite them into OffPress, or manage the site for them. Keep the relationship and build the business model that works for you.
Next.js, Payload, and Postgres
Less rebuilding.
More building.
Use Next.js pages and components, Payload collections and APIs, and Postgres records. Your content model is part of the codebase. So is your frontend.
Next.js Payload GitHub
collections/Workshops.tsIllustrative code
import type { CollectionConfig } from 'payload'
export const Workshops: CollectionConfig = {
slug: 'workshops',
fields: [
{ name: 'title', type: 'text', required: true },
{ name: 'date', type: 'date' },
{ name: 'description', type: 'richText' },
],
}The important details
An AI workflow.
A real application underneath.
Inspect the source
Browse the project in the Code view. See how a feature works and review the changes AI has made.
Connect your repository
Connect GitHub and sync the project into your own repository. Keep your code visible and available beyond the builder.
Extend the content model
Define collections, fields, relationships, and hooks in Payload. Build around the business instead of squeezing the business into a theme.
Build frontend and backend together
Ask the AI to implement pages, components, collections, and API routes. Review the code and try the result in your preview.
Start with an existing site
Bring the site’s existing pages and content into the project, then inspect and extend the rebuilt code.
Keep control of the outcome
Use previews, targeted requests, and your own review standards. Check integrations and production behavior before shipping.
Ownership is part of the architecture
Keep your code.
Keep your options.
Your Next.js and Payload project is yours. Sync it to GitHub and continue working with the tools and developers you choose.
Moving to another host?
Code ownership is the starting point. If you move hosting, plan the database, media, environment configuration, authentication, and external service connections too. A repository is one part of a running application.
Read the ownership guideWhat do I hand over to a client?
You choose. Give the client a familiar Payload CMS admin, invite them into OffPress itself, or keep management with your team. The project stays a real codebase, and you can build the delivery and ongoing service model that fits your work.
Is this a proprietary page-builder format?
Your site is implemented as Next.js and Payload source code. The content models, components, and application routes are part of the project.
Can I connect GitHub?
Yes. OffPress provides a GitHub connection so you can sync the project to your own repository. Use the in-product Code view to inspect the source.
Can the AI change backend behavior?
Yes. The assistant can work on the application layer, including Payload collections, fields, hooks, and API endpoints, alongside the frontend. Review generated code and test important behavior before publishing.
Do I have to manage hosting?
OffPress provides managed hosting for the site. If you choose to host elsewhere, you are responsible for provisioning the application environment and moving its data, media, secrets, and service connections.
Keep what matters. Build what’s next.
Build the next thing.
Keep every line.
See how your website looks and works on OffPress. The preview is free, and your original stays live until you’re ready to switch.
Starting with a new idea? Build from scratch