Works with Claude Code, Cursor, Codex and more
The things you won't find together in any other git-based CMS.
Every publish is still a git commit, but your site doesn't wait for CI. It picks up the new content straight away. Skip builds for content-only commits and revalidate after each publish, and editors never wait on a deploy again.
Add one component to your layout and every page previews drafts as editors type. No per-component wiring, no preview routes, and server components render the draft on the server.
<body>
{children}
<cms.previews widget />
</body>Alinea installs 4 packages. Other CMSs pull in hundreds.
Packages and disk size of a clean npm install, excluding React and Next.js. Measured September 2026.
Rebuilt on React Aria Components: keyboard navigation, focus management and screen reader support throughout.
Decide who can create, edit, publish or upload, scoped by workspace, root, type, field, entry and locale.
Build custom views with the same accessible React components the dashboard is made of, from alinea/components.
Field.localiser keeps every locale of a value in one field, with fallbacks, next to fully translated pages.
Renamed pages keep their old URLs for redirects, and every entry shows what links to it.
Rewrite changes before they are committed, or revalidate, notify and deploy after.
The basics every team needs, without a database to run or a vendor to depend on.
Every entry is a JSON file in your repository. Review, branch and roll back content like code.
Query types come straight from your schema. No generate step and no stale types.
Content is indexed in SQLite, bundled with your site. Fast, fuzzy search in the dashboard.
Run the backend on your own database with one of eight drivers, or let Alinea Cloud handle it.
The docs ship with the package as Markdown, so AI agents know the API of the installed version.
MIT licensed and developed in the open on GitHub.
Three steps, all in your own repository. Nothing to migrate, nothing extra to host.
const BlogPost = Config.document(
'Blog post', {
fields: {
title: Field.text('Title'),
cover: Field.image('Cover'),
body: Field.richText('Body')
}
})Describe types and fields in TypeScript, right in your codebase. No migrations, no separate admin project.
Editors get a generated dashboard with drafts, previews and media. They never see a line of JSON.
Publishing writes a commit to your repository, and your site deploys like any other change.
Query content from server components with an API that knows your schema. Your editor autocompletes every field, and the compiler catches the rest.
export default async function Post({params}) {
const {slug} = await params
const post = await cms.get({
type: BlogPost,
url: `/blog/${slug}`,
select: {
title: BlogPost.title,
publishDate: BlogPost.publishDate,
body: BlogPost.body
}
})
return <Article {...post} />
}const post: { title: string publishDate: string body: TextDoc}
The dashboard ships with your app and deploys wherever Next.js runs. You stay in control of authentication and access.
Connect your GitHub repository and invite editors. Cloud handles sign-in and commits published content back to your repository.
A ready-made Next.js template with a production-ready Alinea setup, so you can start from a working site.
Blog with archive
Categories and authors
Built with Next.js and Tailwind CSS
Can't find what you need? Ask on GitHub.
Not for your content. It is stored as JSON files in your repository, and Alinea builds an SQLite index from those files for querying and search. With Alinea Cloud there is no database to run at all. If you self-host the backend, you do need one for the dashboard's users and roles and for uploads until they are committed: PostgreSQL, MySQL, SQLite or PGlite.
Yes. Alinea is built for the Next.js App Router. You query content directly in server components, and live previews render drafts on the server as editors type.
Yes. The dashboard ships with your Next.js app and deploys wherever Next.js runs. Run the backend yourself on your own database, or let Alinea Cloud handle sign-in and publishing.
They do not have to. Every publish is a git commit and your site picks up the new content without waiting for a build. Content-only commits can skip the rebuild, and static pages can be revalidated after each publish. See instant publishing.
Follow the upgrade guide, which walks through moving an existing 1.x project to 2.0.
Add Alinea to a Next.js project in a few minutes. Open source and MIT licensed.