Build full-scale websites with Onepage CMS. Operate and scale them with AI.
The CMS has been one of Onepage’s most requested features for years.
The timing could hardly be better: a traditional CMS used to take considerable effort to set up and manage. With an AI agent in Onepage, anyone, regardless of prior experience, can now build a large, powerful website simply by describing what they need in a prompt.
You describe what you need, and the agent builds templates (with vibe-coding or no-code), configures them, fills them with content, and keeps them up to date.
Onepage now covers the full lifecycle of a best-in-class website (build, scale, maintain) through a single agent and MCP interface.
No other tool on the market offers all three in one suite.
Beta testing terms
To keep testing fair and transparent, here's how the beta works:
CMS usage is completely unlimited for everyone during the beta. There are no access restrictions. You can create as many collections, records, and websites as you want during the beta.
The beta lasts about one month. Depending on what we find together, it can extend to three months.
The beta is rolled out gradually. You'll find more information in the release plan below.
💡An important note: Until the official release, any project you modify with CMS features opens only at beta.onepage.io. Avoid using the beta on projects with active client work, unless your clients are comfortable accessing their projects through this domain for a few months.
In return, we ask you to share what you find: both the issues you hit and the wins you achieve.
What is Onepage CMS
Onepage CMS is deliberately classic in its design. It's built on the proven model you know from other content systems, with a modern AI layer on top. If you have CMS experience, you already know how to use it.
The core concepts:
Collections hold structured content: blog posts, team members, products, or any shape you define with custom fields.
Records are the entries inside a collection. Each published record becomes a real page on your site, with its own URL and its own SEO metadata.
Bindings connect page elements to collection fields, so one page design renders every record.
The CMS can do far more than just a blog
Anything with a repeatable data structure works: GEO landing pages at scale, product and service catalogs, portfolios, case studies, job listings, event pages, etc.
You can also combine several collections on one page, for example a landing page that pulls from both a services collection and a testimonials collection.
All of this works both with code and without code. You can build everything by hand in the builder with native grids and field bindings, or let an agent model the collections, write the records, and generate the sections for you.
Right now the CMS is a sandbox: you configure it from scratch.
Via MCP and the AI agent this is quick, while the manual setup takes a bit more time. The user experience will improve significantly before launch.
For example, we are planning a feature that will allow you to set up a complete blog with just one click.
Release plan
Phase 1: MCP and manual setup - Launched on September 8, 2026
No in-app chat yet. Raw functionality with little polish.Phase 2: the chat agent arrives - Launched on September 25, 2026
An agent inside the interface, more polish, implemented feedback, and better SEO.Phase 3: full polish - Date to be announced
Templates, an improved agent, and most of your feedback implemented.
The date for Phase 3 will be announced shortly. This is powerful, but it's still a beta:
Expect bugs and rough edges. We haven't tested this at scale yet, so don't apply results directly to live client projects.
Best practice: create a new project for testing. Once you're happy with a result, copy it into your real project.
The chat currently works at the section or element level.
How to get started
As soon as you add CMS elements to a live page, that project stops opening at app.onepage.io until the official release. It opens at beta.onepage.io instead, which is identical. If something goes wrong, reset and start fresh. It's often the fastest way to a good result.
⚠️ Important Note on Claude Links
When clicking a beta.onepage.io link generated by Claude, your browser may automatically redirect you to app.onepage.io. If this happens, the CMS project will not load correctly.
Solution: Check your browser's address bar after clicking. If the link changes to app.onepage.io, manually replace app with beta (so it reads beta.onepage.io/...) and press Enter. The editor will load your project as expected.
Don't use the beta on projects where customers or third parties have access and active work is happening.
Create test projects first.
There are three ways to use the CMS in Onepage:
Through the Account-Agent - set it up quickly and easily.
Through MCP - set it up especially quickly and easily with just a single prompt.
Manually in the Onepage Editor - create and configure it step by step directly in the editor.
If you're not sure where to start, ask the agent for ideas first:
"I'm just getting started with Onepage CMS. Come up with ideas for how I can use it for [Project X]."
Example: Creating a blog
There are three ways to create a blog. Below you'll find detailed articles, each describing one method in detail.
Option 1: Account Agent
Via the AI agent. Click here to see the detailed guide.
Option 2: Via MCP
Via MCP with a single prompt (the easy option). Click here to see the detailed guide.
Option 3: Manually (currently still limited)
Manually in Onepage. Click here to see the detailed guide.
What you can build
A blog, a team page, a product catalog, a portfolio with dozens of projects, GEO landing pages for every city you serve, an FAQ, an events calendar.
Build anything with a repeatable structure, or ask the AI what it can implement on your existing projects.
What makes this different from other AI builders
1. The hybrid approach
The CMS supports both vibe-coded and no-code elements. You can customize deeply through code where you need it, while everything stays easily editable for the people who manage content day to day.
2. The full growth cycle
Onepage is the only builder where you can build, grow, and maintain a large website through an agent or MCP. Elsewhere the scope is limited: either the MCP doesn't support building, or the agent knows nothing about maintenance and content, so you keep switching how you work. Here you have the whole cycle, whichever surface you work in.
3. A true sandbox
This one isn't for everyone, but if you're used to the flexibility of top headless CMS platforms, you'll find about 80% of those capabilities in Onepage. It goes far beyond a blog and can handle demanding use cases.
What NOT to expect
This is a beta, not a finished product. Keep these limitations in mind:
It's not a full-stack app builder. There's no general-purpose application database yet. The CMS manages content that renders on pages, not arbitrary app data.
Results vary. Some prompts produce great results, others need iteration. The better your prompt, the better the output.
Polish is still coming. There will be bugs and inconveniences, and we'll fix them together.
This is the biggest capability we've ever released!
We've spent months working on a system in which AI code generation and visual editing don't compete with each other. They work hand in hand, and we're convinced this is the future of building an online presence.
Now it's your turn: test it, push its limits, and tell us what you think. Your feedback directly shapes what we release publicly. Thank you!
Best regards,
Nik, Marcel, and the Onepage team.