Application
Atlas CMS philosophy is simple — keep complex things simple and reliable so you can focus on your business.
Below are the main features you get with Atlas CMS.
Run multiple projects from a single Atlas CMS account. Switch between client sites, product apps, and internal tools without logging in and out. Each project has its own content models, media library, and API—so you get clear separation and no cross-contamination. Ideal for agencies and teams shipping several products or white-label solutions.
Design your content schema without writing code. The visual model builder lets you create models, add fields, set validations, and define relationships through an intuitive interface. See your content structure at a glance and iterate quickly. Perfect for content designers and developers who want to move fast and keep the content layer flexible for future changes.
From plain text and rich text to numbers, dates, booleans, media, relations, and custom types—Atlas CMS gives you over 30 field types out of the box. Use lists and repeatable components for flexible layouts, tags for taxonomy, and maps for location data. Editors get the right input for each field, so content stays consistent and your APIs stay predictable.
Components are reusable building blocks you can attach to one or more models. Define a block once—e.g. a hero, a CTA, or a testimonial—and reuse it everywhere. Change the structure in one place and it updates across all models. This keeps your schema DRY and makes it easy to build page builders, landing pages, and modular content without duplication.
Query exactly the fields and relations you need in a single request. Atlas CMS exposes a full GraphQL API with filters, sorting, pagination, and nested relations. Frontends and apps can request minimal payloads, reducing over-fetching and round trips. The API is auto-generated from your content models, so it stays in sync as your schema evolves.
REST endpoints for every content type, with standard HTTP verbs and predictable URLs. Create, read, update, and delete entries; filter and sort with query parameters; and paginate large result sets. Integrate with any stack—mobile apps, legacy systems, or serverless functions. REST and GraphQL coexist, so you choose the right API for each consumer.
Filter content by any field: text search, exact match, ranges, relations, and more. Combine conditions with and/or logic and sort by one or more fields. Same filter capabilities in both GraphQL and REST, so you can build dynamic listing pages, search UIs, and admin tools without custom backend code.
Trigger HTTP callbacks when content changes. Fire webhooks on create, update, delete, or publish—and optionally filter by content type or stage. Use them to invalidate caches, sync to search engines, notify internal tools, or run pipelines. Payloads include the changed entity and event metadata so your endpoints can react without extra lookups.
Work with draft and published stages so editors can prepare content before it goes live. Draft content is available through a dedicated preview API with the same filters and relations as the public API. Publish when ready; roll back if needed. Content stages keep production stable while enabling fast iteration and safe previews for static or dynamic sites.
Add as many locales as you need—no hard cap. Each field can be localized so you store translations per language. Query content by locale in the API and let the frontend switch language without changing structure. Fallbacks and optional locales give you flexibility for regional sites, micro-copy, and gradual rollout of new languages.
Upload and organize images, documents, and videos in a folder-based media library. Attach assets to content via media fields; reference the same file in multiple entries. Filenames and alt text are editable, and the API exposes URLs and metadata so frontends can render responsive images and download links. Folders keep large libraries manageable.
When editors upload a file, Atlas CMS can extract metadata automatically: dimensions and format for images, duration and codec for video, and more. This metadata is stored and available in the API, so you can build dynamic galleries, enforce aspect ratios, or drive CDN and transformation logic without manual tagging.
Edit images inside the admin panel: crop, resize, rotate, and adjust orientation. No need to open external software—editors can fix assets before publishing. Changes are non-destructive where possible, and the API still exposes the original and derived URLs so you control how images are used on the frontend.
Serve optimized images via URL parameters: width, height, crop mode, format (e.g. WebP), and quality. The image server handles resizing and caching so frontends request the exact size needed for each breakpoint. Reduces payload size and improves LCP and CLS without pre-generating dozens of variants per asset.
Invite team members to the Atlas CMS admin and assign roles that define what they can do: manage content, edit models, manage users, or full admin. Permissions are granular so you can give clients access only to their project and content types. Audit who changed what and when, and revoke access in one click.
Project users are end-users of your product—not CMS editors. Define custom roles and permissions and use the API to authenticate them (e.g. via API tokens or your IdP). Build member areas, gated content, and personalized experiences. Roles map to your business logic so you can enforce who sees what at the API level.
Issue API keys that act like a user: they inherit the same permissions as an admin or project role. Use them for server-to-server integration, headless frontends, or mobile apps. Keys can be scoped to read-only or specific content types. Rotate keys without changing app code, and revoke compromised keys instantly.
Add teammates and clients to projects and assign roles so everyone has the right level of access. Multiple editors can work on content at once; drafts and content stages reduce conflicts. Collaboration is built into the workflow—no extra tools required—so distributed teams and agencies can ship content together.
Official SDKs give you type-safe access to the API from your favorite stack. Query content, resolve relations, and work with localized fields without hand-rolling HTTP calls. SDKs are designed for the way developers build today: with TypeScript, async/await, and clear conventions. Use them in Next.js, Nuxt, or any Node or browser environment.
Atlas CMS keeps evolving: more field types, more integrations, and more control over your content layer. Explore the docs, try the API, and get in touch if you need something specific. We build for developers and content teams who want a headless CMS that stays out of the way and scales with their product.
