Model the content
Build a content type by dragging fields, or paste the schema as JSON. Text, rich text, media, relations, links, dates, numbers, selects, booleans, buttons, repeatable groups. One entry for a homepage, or many for a blog.
Websites
One CMS for every site you run
Model the content, author the entries, stack the modules, then pull it into any frontend through the read API. The page you are reading right now was built that way, baseassist.com runs on Base Assist Websites
Content in, API out
Structure it once. Author it in the Websites app. Render it wherever the site lives.
Blocks editors can stack
Define a module once, give it variants, then drop a module zone on the page type. Editors stack hero, pricing, FAQ, whatever you built, in any order, as many times as they want.
Published, Planned, Archived
Live pages sit in Published. Everything still being written sits in Planned, so you can see what is coming before the public does. Retired pages go to Archived. Publish one, or a hundred at once.
Ship it as a release
Group the pages that should go live together into a named release, put a date and time on it, and walk away. It publishes itself. A preview key lets a staging build read the whole thing first.
Media that stays organized
Upload images, video, and files into folders. Alt text per locale. Replace a file and every entry using it gets the new one. Check where an asset is used before you delete it.
Ship it in every language
Set the locales per site and mark which fields are localized. Missing copy falls back down the chain instead of rendering blank. Auto translate a batch of entries when you need a first pass.
One read API, one SDK
Issue API keys per site with read or preview scope, set an expiry, revoke one anytime. Install the npm package and fetch entries, singletons, media, and locales, with a rich text renderer included.
Hosted, on the way
Let us run the site instead. Custom domain, SSL, global CDN, redirects, and publish straight from the entry. Same CMS underneath, so a headless site can move over later without touching the content.
How it works
Model it. Author it. Plan the launch. Fetch it. Watch the traffic.
Model
Set up the site.
Create a site, pick the locales, then define the content types. Fields go in a Main section, meta title and description in an SEO section.
- 01Create the site and set the default locale.
- 02Build content types with the field canvas or JSON mode.
- 03Add a module zone where editors should be able to stack blocks.
Author
Fill it in.
Write the entries, upload the media, stack the modules, switch locales as you go. Save a draft, publish when it is ready.
- 01Create an entry and fill the fields.
- 02Pick modules from the sidebar and order them.
- 03Publish, or auto translate the localized fields first.
Connect
Point your frontend at it.
Create a read key, install the SDK, and fetch published content server side. Next.js, Astro, Nuxt, anything that can call an HTTP API.
- 01Issue an API key with read scope.
- 02Install @base-assist/content-management and create the client.
- 03Render the modules however your design needs.
Measure
See what the site is doing.
Add the tracker and the same site gets its own stats. Pageviews, visitors, sessions, top pages, referrers, locales, devices.
- 01Drop the tracker into the site layout.
- 02Open Stats on the site in the Websites app.
- 03Export the content anytime if you need it elsewhere.
Wire the site to the office
The Websites app renders the pages. What a visitor sends lands in the app that handles it.
Headless CMS pricing
Billed per site, not per seat.
Free
Free
1 editor, 1 locale, 250K API calls, 25 GB bandwidth. Enough to build the thing and see if it works.
Starter
$19/ site / month
3 editors, 3 locales, 1M API calls, 100 GB bandwidth. Preview keys, media library, export.
Studio
$49/ site / month
10 editors, 5 locales, 4M API calls, 500 GB bandwidth. Auto translate and site stats.
Scale
$149/ site / month
Unlimited editors, unlimited locales, 10M API calls, 1 TB bandwidth. For the site the whole company reads.
$0.25 per GB over the included bandwidth. Pass the API call limit and the site moves up to the plan that covers it, so nothing goes dark mid month.
Every site picks its own plan, so a landing page and the main marketing site do not have to pay the same rate. Editors are the people with access to that site in the Websites app. Content types, entries, modules, and media are unlimited on every paid plan.
Need more than one app? Estimate a monthly total.
Hosted pricing
On the way. Prices are not final yet.
Preview
Free
A Base Assist subdomain to share the build. Not meant for production traffic.
Hosted
$25/ site / month
Custom domain, SSL, global CDN, redirects, forms, and site stats. Publish straight from the entry.
Hosted Plus
$49/ site / month
More bandwidth, more locales, site search, and a password protected staging domain.
Hosted plans are still being finalized. Bandwidth is expected to work the same way, at $0.25 per GB over the included amount.
Hosted is the same CMS with the site running on us: custom domain, SSL, global CDN, redirects, and publish from the Websites app instead of a build pipeline. Start a site headless today and switch it to hosted later. The content does not move.
Need more than one app? Estimate a monthly total.
Questions
How the Websites app is set up in Base Assist.
Headless is live. Content types, entries with draft and publish, stackable modules, a media library, locales, API keys, site stats, and export. You bring the frontend. Hosted sites, where we run the site for you, are on the way.
Anything that can call an HTTP API. There is an npm package, @base-assist/content-management, for fetching entries, singletons, media, and locales, plus a renderer for rich text. Keys are read only or preview only, and they stay on the server.
Because a campaign landing page and a marketing site with a blog are not the same workload. Each site picks the plan that fits its traffic, its locales, and how many people edit it. Run five sites on five different plans if that is what makes sense.
Yes. Add locales to the site and mark which fields are localized. Auto translate runs a first pass over localized text and rich text so an editor is correcting copy instead of writing it twice. Anything still missing falls back down the locale chain.
Add the tracker to the site and the stats show up next to the content: pageviews, visitors, sessions, engaged time, top pages, referrers, locales, and devices. Bots and do not track requests are filtered out.
Any time. Export a whole site, one content type, or a set of entries as JSON, with the content types, modules, and media that go with them.
Help with the Websites app
Content types, modules, entries, media, locales, API keys, and the SDK.