Payload Kits for agencies and freelancers

Payload Kits installs production-ready blocks with one command.

Curated kits wire schema, render components, generated types, and import-map updates into real Payload v3 repos.

Product proof

Curated kit installPayload-aware wiring

Command line

Install the kit, wire the repo, keep going

$ npx payload-kit init
$ npx payload-kit add hero-pricing-faq
$ pnpm payload generate:types
$ pnpm payload generate:importmap

Detected Payload v3 website starter

Added hero-pricing-faq manifest

Wired block config + render components

Ran generate:types and generate:importmap

Generated files

src/blocks/HeroKit/config.ts

src/blocks/HeroKit/Component.tsx

src/blocks/PricingKit/config.ts

src/blocks/FaqKit/config.ts

Installed surface

Hero Kit

Headline, CTA, proof ribbon, and Payload-safe defaults.

Pricing kit

Full block config, renderer, and docs metadata bundled together.

FAQ kit

Full block config, renderer, and docs metadata bundled together.

Payload v3 only

Next.js App Router

Type-safe installs

Import-map aware

Preview friendly

How it works

A three-command flow built for repeatable delivery, not demo theatrics.

Detect the repo, add the kit, and verify the result before shipping.

CLI

Prepare the repo

Detect the repo shape, confirm it is a supported Payload v3 + Next.js app, and prepare the registry config before anything touches your blocks.

npx payload-kit init

Validates project shape before install

Sets up the Payload-specific registry workflow

Keeps the install path opinionated from day one

CLI

Add a production-ready kit

Install a complete kit with its frontend block, Payload schema, admin-safe defaults, dependency wiring, and the repo changes required to make it real.

npx payload-kit add hero-pricing-faq

Adds the render component and config fragments

Installs peer dependencies and sample content

Runs generate:types and generate:importmap for you

CLI

Verify before shipping

Audit the project after upgrades and repeated installs so you can see version drift, missing peers, and compatibility gaps before they become delivery risk.

npx payload-kit doctor

Flags unsupported versions and missing peers

Surfaces multi-kit conflicts before deploy

Keeps repeatable client builds from drifting

Payload-native moat

The value is not just the block. It is everything required to make the block belong.

Payload Kits is positioned as a kit platform, not a generic component CDN. Every install is meant to feel like a native repo update rather than a pasted screenshot with a schema gap.

Why teams trust the install

Supports the official website-style Payload starter first

Plays nicely with existing blocks in mildly customized repos

Keeps multi-kit installs legible as the catalog grows

Layouts-aware by default

Every kit is designed to drop into Payload layouts instead of fighting them with generic component-library assumptions.

Repo-native integration

Schema wiring, render components, and install tasks stay aligned so block output and repo structure move together.

Type and import-map safe

Installs finish with generated types and refreshed admin imports so teams do not have to remember fragile cleanup steps.

Curated for delivery speed

The catalog stays curated, upgradeable, and consistent across kits, which matters more than chasing visual novelty.

Why this wins

Integration quality is the product.

The moat is that kits understand Payload layouts, type generation, import-map updates, and the repo constraints agencies deal with every week.

Operationally legible

CLI surfaces tell you what changed, what was installed, and what still needs attention.

Built for repeated launches

Curated kits ship with the pieces agencies actually reuse instead of one-off demo fragments.

Catalog tuned for websites first

Testimonials, forms, pricing, hero, and FAQ kits move from idea to Payload-ready code in minutes.

Reliability over novelty

Doctor and post-install checks make the platform feel safer to adopt in real client repos.

Kit catalog

Start with the blocks agencies and freelancers actually install on repeat.

v1 stays deliberately focused on website blocks first: heroes, pricing, testimonials, FAQs, CTAs, forms, proof sections, and the supporting content layouts around them.

Foundation

Curated kits that feel native to Payload.

The pieces that give a new Payload site its backbone fast.

Hero kit

Headline-led hero blocks with strong payload wiring and preview-safe defaults.

hero block

render component

seed content

Proof kit

Stats and logo sections for establishing trust without manual layout work.

stats block

logo cloud

spacing presets

Content kit

Flexible content sections that still feel deliberate in a real client build.

content block

layout variants

docs metadata

Open core business model

Free public trust layer. Paid private registry when the work gets serious.

The public catalog builds trust and adoption. The private Pro namespace unlocks the premium kits and bundles that matter when you are shipping repeatedly for clients.

Open core

Public registry

Use the public registry to evaluate install quality, preview the kits, and adopt a dependable baseline into every new client project.

Free public registry for trust and adoption

Curated starter kits and documentation

Strong SEO footprint for the catalog itself

Paid Pro

Private Pro registry

Unlock the private namespace for premium kits, higher-value bundles, and the install workflows that matter once delivery volume starts climbing.

Private authenticated registry namespace

Premium kit bundles for repeatable site builds

Commercial-friendly path for agencies and freelancers

Reliability

Sell install confidence, not just visual polish.

Make it obvious that reliable installs, clean upgrades, and predictable repo wiring matter as much as the blocks themselves.

Idempotent installs

Repeated installs should finish cleanly without duplicate fragments or mysterious manual cleanup.

Compatibility checks

The CLI should spot unsupported project versions, missing peers, and drift before any fragile changes land.

Entitlement-aware access

Pro kits stay behind authenticated access while the install surface remains predictable for approved teams.

Conflict-aware upgrades

When a repo already has existing blocks, the tool should guide a clean merge instead of blindly overwriting work.

FAQ

Opinionated constraints, answered directly.

The first launch stays narrow on purpose so the install experience can be dependable. These answers set the expectation up front.

Payload Kits

Ship the next client site with kits that already know Payload.

Designed for agencies and freelancers who want install confidence, curated quality, and less manual block plumbing every time a new project starts.

Join the waitlist

Get notified when the first kits are ready to install.

Send one email address straight to the waitlist service. We do not store these signups in Payload.