Content Management

Your content model, live as an API

Anythink works as a headless CMS: model content types, edit them in the Anythink dashboard, and serve them to your website through a public REST API.

The same task, three ways

Create an articles content type your website can read.

The Anythink dashboard

Model the content type, then your editors write in the same place.

  1. ›Data Model → Add Entity: articles (public)
  2. ›Add Field: title (varchar, required, searchable)
  3. ›Add Field: body (text, rich text)
  4. ›Add Field: hero_image (file)
  5. ›Add Field: status (select: draft, in_review, published)
  6. ›Create Entity
  7. ✓GET /entities/articles/public/items is live

The Anythink CLI

The same content type, scriptable and repeatable.

$ anythink entities create articles --public$ anythink fields add articles title --type varchar \--required --public --searchable$ anythink fields add articles body --type text \--display rich-text --public$ anythink fields add articles hero_image --type file \--display file --public$ anythink fields add articles status --type varchar \--display select --options draft,in_review,published --public
  • ✓Entity articles created, public
  • ✓Fields added: title, body, hero_image, status

Claude, through MCP

Describe the content type. The assistant runs the same commands.

you › “Create an articles content type for our blog with a required, searchable title, a rich-text body, a hero image and a status of draft, in review or published. Make it publicly readable so our website can fetch published articles.”

  • ✓Entity articles, publicly readable
  • ✓Title is required and searchable
  • ✓Body is rich text, with a hero image
  • ✓Status: draft, in review, published

What makes it work as a CMS

Content types are entities, so every part of Anythink works with them.

Public API

Your website reads content without a key

Mark a content type and its fields public, and /entities/articles/public/items serves them without sign-in, with paging, sorting and field filters. Fields you don't mark public stay private.

Media

Upload a video, get its duration

A worker probes each upload with ffprobe and writes duration, dimensions, bitrate, size and a hash back to the file record. Your site can show a running time without reading the file itself.

Editorial

Kanban columns from your status field

The kanban view groups any content type by a status field. Moving a card updates the record, so the board and the API never disagree about what's published.

Automation

Publishing can start a workflow

Trigger a workflow when an article's status changes to published: post to Slack, email your subscribers or call a webhook to rebuild your site.

A CMS that is also your backend

Content types are ordinary Anythink entities, so the same project holds your content, your users and your app data.

Rich text next to structured fields

Give a text field the rich-text display and editors write long-form copy in the dashboard. The body sits on the same record as its title, author, category and hero image, so your site can query on any of them.

In practice

Read, search and secure your content

fetch published articles.ts
GET https://api.my.anythink.cloud/org/{org_id}/entities/articles/public/items?status=published&sortBy=id&sortDirection=desc&page=1&pageSize=10

How it works

01

Model your content types

Create an entity for articles, case studies or products and add the fields each one needs, including rich text, files and relationships to authors or categories.

02

Give editors a role

Create an editor role with read, create and update permissions on your content types, then invite your writers to the Anythink dashboard.

03

Run the editorial board

Editors write in the dashboard and move content through draft, in review and published on the kanban view.

04

Fetch it from your site

Your website calls the public endpoint for each content type and asks for published records only. A field you add in the dashboard appears in the response straight away.

Editorial board

Move content through draft, review and published

Switch the articles entity to Kanban View and drag cards between statuses.

Flexible data views →

Frequently Asked Questions

Is Anythink a headless CMS?

Yes. You model content types as entities, editors manage them in the Anythink dashboard, and your website or app reads them through a REST API. Public content types can be read without an API key.

Because it's also a full backend, the same project can hold sign-in, subscriptions and workflows for the product the content supports.

Does Anythink support drafts and version history?

No. There's no built-in draft copy of a record and no revision history to roll back to. Most teams use a status field (draft, in review, published) and have the website request only published records.

If you need full revision history or scheduled preview environments, a dedicated CMS is the better fit today.

Is Anythink a page builder?

No. Anythink stores, secures and serves structured content, and your front end (Next.js, a mobile app, a static site generator) decides how it looks. There's no drag-and-drop page layout editor.

Is Anythink a Strapi or Directus alternative?

For API-first content, yes: custom content types, a REST API, roles, files and search. Anythink adds native subscriptions, push notifications and a visual workflow engine in the same project.

It's fully managed, so there are no servers to run or upgrade, and Enterprise customers can have a dedicated stack.

Still have questions?

Get in Touch

More in the same project

Every feature reads from the same data model, so each one you add works with the rest.

Documentation

Guides and reference at docs.anythink.cloud.

Let's start creating

All the tools you need to start small and create something big