Payload CMS visual website builder

Structured collections in Payload. Visual page building in ChaiBuilder.

Payload CMS gives your engineers a clean, code-first headless CMS in Next.js, but non-technical customers still struggle to build and lay out pages from raw form fields. ChaiBuilder drops into the same Next.js app and PostgreSQL or SQLite database, giving your customers a white-label visual canvas wired directly to your Payload collections.

White-label, multi-tenant, self-hosted inside your product. One yearly license for every customer site.

One Next.js deployment. One database. Zero coupling lock-in.

In our public starter and multi-tenant Pro setup, Payload CMS and ChaiBuilder run side by side inside the same Next.js application, sharing your database while keeping their tables cleanly separated.

  1. 01

    Pre-wired collections and page types

    Use Payload CMS for structured records (blogs, product catalogs, team directories, legal docs) and bind those collections directly into ChaiBuilder visual page templates via server-side data providers. See integrations

  2. 02

    Shared authentication and site scoping

    Map Payload user logins and API keys directly into ChaiBuilder's context resolver so users log in once and see only the customer site and permissions assigned to them.

  3. 03

    Automatic cache-tag revalidation on save

    When a record is updated in a Payload collection, automatic cache-tag invalidation refreshes only the customer pages displaying that record, with no full-site rebuild.

  4. 04

    Independent tables: Payload is optional, never mandatory

    ChaiBuilder stores its pages and block JSON in its own independent database tables. Use Payload where you want structured collections, or bind ChaiBuilder directly to your existing SaaS database tables.

Low-code, not no-code

Your developers set it up once. Your customers run their sites.

Closed no-code builders hit a wall the moment a customer site needs your platform's live data or custom widgets. ChaiBuilder runs as code inside your app, so your engineers keep full control while your customers get effortless visual editing.

For your developers

A plugin in your Next.js stack

Integrate once. Register custom React blocks, bind pages to server-side data providers, pass your existing auth session, override routing, and expose custom MCP tools. No closed black box.

For your onboarding and account team

Fast setup and review

Spin up new customer sites pre-populated from your database, adjust design tokens, review drafts created by AI agents, and roll back any page in one click.

For your customers

Guardrailed self-service

Customers log in inside your product, update their own copy and promotions visually or by chatting with AI, preview changes, and publish live without opening a ticket to your team.

One module inside your product. Zero engineering tickets for day-to-day site edits.

Built-in MCP server

Your customers' AI can do the busywork. A person still approves it.

Anyone with an account and permission on a customer site can connect Claude, Cursor, VS Code, or any MCP client to /api/mcp. The agent updates pages, translates content, and fixes SEO with that user's exact permissions, and every change lands as a draft until a person reviews and publishes it.

  • Visual builder for people

    Customers and onboarding staff build and publish pages visually inside your product, with an AI chat assistant beside them.

  • 33 built-in MCP tools for agents

    Connect Claude, Cursor, or VS Code to find pages, edit blocks, translate content, audit SEO, manage redirects, and compare revisions, plus custom MCP tools your developers register for your platform's data.

  • Drafts first, zero collisions

    Agent edits save to drafts with a preview link and never overwrite a page someone currently has open in the visual builder.

  • Runs on your site and their AI keys

    The MCP server runs inside your own deployment and database, and agents run on the AI subscriptions you or your customers already pay for, with zero ChaiBuilder AI credit fees.

Connect any MCP client with your own API key

// .mcp.json in Claude, Cursor or VS Code

{

"mcpServers": {

"customer-site": {

"url": "https://your-platform.com/api/mcp",

"headers": {

"Authorization": "Bearer YOUR_API_KEY"

}

}

}

}

What the agent hands back

You: Translate the pricing page into French and tighten the meta description.

Agent: Done. Saved as a draft, nothing is live. Preview: /fr/pricing?preview=draft. Publish when you have reviewed it.

Built to sit inside your stack, not beside it

Hosted white-label builders keep your customers' websites on their cloud and tax you per site as you grow. ChaiBuilder runs inside your own application, so your customer data, your servers, and your margins stay with you.

Own your database

Bring your own PostgreSQL or SQLite database. All customer pages, registered users, revisions, and actions live inside your database alongside your core product records. ChaiBuilder has no access to any of it.

Own your infrastructure

ChaiBuilder is delivered as code you deploy on your own stack. There is no vendor-hosted runtime in the request path, and a lapsed license never takes a live customer site down.

One license, zero feature tiers

A single yearly Pro license unlocks the entire product: multi-tenancy, your brand in the builder, and the MCP server included. No feature flags, no per-site fees, no per-seat pricing, and no AI credits.

Ownership is not a plan tier or an add-on here. It is the architecture.

Pricing

One license. Every customer site on your platform.

SaaS platforms license chaipro with one predictable yearly fee for the whole platform, however many customer sites it runs, built on an open-source core you can inspect on GitHub today.

Pro

Unlimited customer sites

chaipro, for SaaS platforms

One yearly licenseunlimited sites

chaipro built into your SaaS product so every customer gets a website under your brand, plus Build Services to get you live.

  • Multi-tenancy and your brand inside the builder
  • Server-side data binding to your database (PostgreSQL or SQLite)
  • Roles, revisions, multilingual, AI assistant, and the MCP server included
  • Build Services: pilot integration, custom blocks, migration, and rollout
Book a demo

White-label, built into your product, self-hosted on your infrastructure.

Open Core

chaicore

FreeBSD-3-Clause license

The chaicore open-source visual builder foundation for Next.js.

  • Core visual builder, custom React block SDK, and runtime renderer
  • SQLite page storage
  • Open source on GitHub, self-hosted anywhere

Every Pro deployment includes 100% of the feature set and the built-in MCP server. One yearly license for your whole platform: no per-site fees, no per-seat pricing, no AI credits, and no feature tiers.

Frequently asked questions

Anything else, bring it to a 30-minute demo call.

Book a demo
How is ChaiBuilder licensed and priced?

SaaS platforms license chaipro with one flat yearly fee for the entire platform, covering unlimited customer sites, quoted to your scale on the demo call. Build Services for initial integration, custom blocks, and site migration are scoped and billed separately. There are no per-site fees, no per-seat charges, no AI credit fees, and no feature tiers. If you only need a site or two, the open-source core (chaicore) is free under the BSD-3-Clause license.

What is the difference between the open-source core (chaicore) and Pro (chaipro)?

The open-source core (chaicore) is a single-site Next.js visual builder with SQLite page storage and runtime rendering. The commercial chaipro package adds everything a multi-site SaaS platform needs in production: multi-tenancy, PostgreSQL support, white-label branding in the builder, RBAC roles and permissions, revisions and restore, multilingual management, URL redirects, media management, the full in-builder AI assistant, and the built-in MCP server.

Our core product is not built on Next.js. Can we still use ChaiBuilder?

Yes. If your main SaaS runs on Rails, Laravel, Django, Go, or .NET, ChaiBuilder runs as a companion Next.js website service in your cloud (serving customer custom domains and the embedded editor) while its server-side data providers read live records from your existing backend API or primary database.

Can AI agents like Claude or Cursor update customer websites safely?

Yes. Every Pro license includes the built-in MCP server at /api/mcp. Users with the mcp:use permission connect Claude, Cursor, or VS Code using their personal API key. The agent operates strictly within that user's permissions, saves changes as drafts for human review before publishing, and respects real-time page locking so it never overwrites a page someone has open.

How does Bring-Your-Own-AI work?

The in-builder AI chat assistant connects directly to your own Vercel AI Gateway, OpenRouter, or custom AI provider credentials configured in your deployment, and MCP agents run on the AI subscriptions your team or customers already use. ChaiBuilder never sits in the middle or charges AI token credits.

How do we validate fit before signing a platform contract?

Every engagement starts with a 30-minute architecture and product demo call, followed by a scoped pilot where we integrate ChaiBuilder into your app on a small set of customer sites. Your engineers can also inspect the open-source core (chaicore) on GitHub at any time.

See it running inside a product like yours.

A 30-minute walkthrough. We look at your product, your data model, and how many customer sites you run, and show you ChaiBuilder running multi-tenant under your brand.

Only building a site or two? Start with the free open-source core

lockup-horizontal-light.png

The website builder for agents and humans. Owned by you. The website module for platforms and agencies that run many sites, self-hosted on Next.js.

© ChaiBuilder. All rights reserved.