Xenon at work
Name a collection.
Or try
const recipes = defineCollection({
slug: "recipes",
admin: { useAsTitle: "title" },
fields: {
title: text({ required: true }),
servings: number({ min: 1 }),
photo: media({ relationTo: "media" }),
method: richText(),
},
});Recipes
New recipeTitleServingsPhotoStatus
No recipes yet
Create the first recipe. It stays a draft until you publish it.
For the peoplewho write
Editors never see the code. They get the fields your site needs and nothing it doesn’t, in an admin that stays out of the way.
Try the adminTypes that follow the schema
Add a field and every query, form and response knows about it. No codegen, no client to configure.
const { docs } = await getXenon(config).find({
collection: "posts",
where: { featured: { equals: true } },
});Install to publish
One package, one config file and two routes. There’s no service to sign up for and no second server to run.
Install
- Add the package
- Pick a database
Describe
- Your collections
- Get the types
Mount
- The API route
- The admin page
Publish
- Create the first admin
- Invite your editors
A CMS in your repo3 files, 1 setting
Runs on what you own
Data
- PostgreSQLany server
- PGliteembedded, no setup
- Drizzlebring your own instance
Files
- Local diskserved by the API route
- Amazon S3signed requests
- Cloudflare R2S3-compatible
People
- BetterAuthsessions you host
- Rolesadmin and editor
- API keysfor scripts
Delivery
- Local APIno HTTP hop
- REST/api/xenon
- RichTextno client JavaScript
- Cache tagsexpired on publish
Like Payload, it lives in your Next.js app. Like Sanity, editors get a focused studio. Unlike a hosted content lake, every document stays in your database. MIT licensed.
Your schema.Your admin.
Needs Next.js 16 and React 19. Then open your app’s admin page and create the first account.