deco CMS

deco CMS is best suited to commerce teams that need business users to publish storefront changes while developers retain repository-level control. Its appeal is that visual editing and code changes share a workflow; teams seeking a standalone page editor may find that approach more than they need.

Overview

Non-technical staff can create, edit, and publish without tickets, while design-system components and tokens can stay locked. An AI agent handles other changes on the customer’s stack, guided by system prompts, design-system references, and repository skills. TypeScript typing can stop invalid data-layer commits, a useful guardrail when code changes enter the publishing flow.

Content and code stay in the repository as changesets with shareable previews, and the page says rollback takes one click. That gives teams a reviewable path for editorial and code changes, but means the repository is central to the workflow rather than an optional implementation detail.

Key features

The CMS works over Shopify, VTEX, Wake, VNDA, and headless or custom stacks. Teams can create audience variants by country, state, or UTM and run A/B tests at the edge, with results exportable to Google Analytics 4. These capabilities make deco a stronger fit for storefront teams iterating on audience-specific content than for organizations that only need basic publishing.

Studio supports Deno, including Fresh and HTMX; moving to TanStack is not required. The FAQ also says deco handles gradual migration from the old admin, which was scheduled for discontinuation on October 30, 2026. That migration support matters to existing users planning a transition.

Pricing

Open source core: free. The core is free forever and self-hosted on your infrastructure. It suits teams able to run the software themselves, but does not include the full Studio product.

Studio: $20 a month, billed $20 /user/month. It includes agents, CMS, workspace, automations, one site diagnostic every week, and $5/user per month in AI credits. This is the practical paid option for teams wanting the complete product; its per-user charge makes seat count relevant to the budget.

Enterprise: $10,000 a month, billed $10,000 /month. It includes managed SaaS or assisted self-hosting, SLA support and direct engineering access, onboarding and training, and dedicated maintenance engineers. The included services suit enterprise operations that need ongoing technical support, at a substantial fixed monthly price.

Outcome operation: custom pricing, billed fixed + % of growth. The 12-month plan includes 24/7 agents and embedded engineers, with goals and baseline set for the term and impact measured by production A/B tests. It is aimed at teams buying an outcome-oriented operating engagement rather than only CMS software.

Platforms

deco supports API, macOS, self-hosted, and web. Hosting can be self-hosted or managed, so teams can choose between running the open-source core on their own infrastructure and the managed SaaS option in Enterprise.

Who it's for

Commerce teams and enterprise operations managing storefronts across platforms and sites are the clearest fit. The visual editor serves business teams, while repository changesets, previews, and agent guardrails give developers a role in the same workflow. A team without a need for commerce integrations, experimentation, or repository-backed changes may be better served by a simpler CMS.

Pros and cons

• Pro: Business users can publish without tickets, while design-system components and tokens remain protected.
• Pro: Changesets, previews, repository storage, and one-click rollback give teams a review and recovery path for changes.
• Pro: Commerce integrations, audience variants, and edge A/B testing support storefront experimentation.
• Con: Studio is priced per user, so costs rise with the team; its included AI credits are capped at $5/user per month.
• Con: The free core is self-hosted, putting infrastructure responsibility on the team.
• Con: Enterprise costs $10,000 per month, which is a major commitment for teams that do not need its managed hosting and support.

Alternatives

Git-Based CMS is a useful category to explore if repository-oriented publishing is the main requirement and you want to compare options.

Quiqr is a free, open-source choice for readers who want a forever-free product across desktop and web platforms. Mattrbld offers an official hosted instance for small-scale private projects, with no availability guarantee; its self-hosted plan may suit readers evaluating that route. Decap CMS is another freemium, self-hosted option, with a free plan that includes one site and one seat.

HugoCMS is worth considering for readers seeking an open-source, multilingual option with unlimited updates on its free plan. Keystatic is a freemium alternative whose free plan supports up to three users per team. Kiln offers a free, open-source self-hosted plan, but the user runs the worker and GitHub App and provides the site host.

Netlify may suit readers looking for a broader web platform with a free plan capped at 300 credits per month, one concurrent build, and one team owner. Siteleaf is another freemium option, with a free Developer plan capped at 100 MB and 100 pages and limited to public GitHub repositories.

Verdict

Choose deco CMS if commerce teams need business-user publishing tied to repository-based changes, previews, and storefront experimentation. Its strongest case is combining those workflows with an AI agent and technical guardrails; look elsewhere if you need a lightweight editor, cannot take on self-hosting, or do not need Studio’s per-user product or Enterprise’s costly support package.