deco

Tap a star to rate

What deco is

deco is an open source CMS and AI agent workspace for commerce teams, with an operating service wrapped around it. The company's site describes two ways in: run Deco Studio yourself ("Open source · self-host ou operado pela deco", in its own words, self-host or operated by deco), or have deco run your site and app with senior engineers, AI agents and proprietary software, "pagos apenas pelos resultados que geramos" (paid only for the results we generate). It is written for e-commerce and digital teams, and the examples on the page involve VTEX and Shopify storefronts. The site's own description says AI agents and senior engineers run the site, app and storefront under the customer's governance, with "Comece grátis" (start free) as the entry point.

What you build and how

The product has three layers, and the page names each one.

CMS Agêntico. The company pitches it as "Edição visual + agentes que codam com a segurança do Git. Na sua stack." In plain terms, visual editing plus coding agents, with changes going through Git, on your own stack. The editor demo on the homepage shows a winter home page with a hero section and a "Mais vendidos" product row. Fields in that hero are marked "Título editável por qualquer pessoa do time" (title editable by anyone on the team), an image field takes an upload or a search in a DAM (digital asset manager), and the background color is limited to "tokens do seu design system, só eles". A lock note reads "Design system travado: componentes e tokens corporativos. O time local muda conteúdo, não o padrão." (Design system locked: corporate components and tokens. The local team changes content, not the standard.) The same demo shows a default version, an Argentina version and an A/B test variant B, so one page can serve different segments, with a default served to all traffic that matches no segment. A Publish button ends the flow. For a blog or content site this is the part to care about: non-developers edit text and images, while developers keep control of components.

Deco Studio. The site calls it "O AI OS da operação" (the operation's AI operating system) and describes it as the place where agents work, with context, permissions, audit trail and cost kept in one place. The demo is a workspace with an inbox, tasks and threads. In one example thread, an agent is asked to find checkout failures from the last deploy, fix the root cause and open a PR. The tools panel lists Sentry (read), Postgres (read) and GitHub (write), and the thread ends with a pull request on a fix branch. The thread card shows a cost of $0.42 and 96k tokens, so spend per task is visible. The agent shown is Claude Code, listed in the Thinking and Agent selectors. The page says the Studio and CMS are open source "no seu Git, com as suas chaves" (in your Git, with your keys), with a "Ver no GitHub" button, and "Self-host na sua infra, com as suas chaves, ou operado por nós".

Agentic Apps. These are packaged specialists: "Vitrines, catálogo, SEO e monitoramento". The tiles read "+10% receita" for storefront listing pages, "24/7 monitorado" for SEO and GEO, "3.2k checks/dia" for site health and "0 regressões" for QA.

The five-step loop

The homepage walks through how the agents work.

  1. You grant access: GitHub, Analytics, Search Console, VTEX or Shopify. The page says read access comes first and "nada muda sem você" (nothing changes without you). The connections demo lists GitHub (3 repositories), Google Analytics 4, Search Console, VTEX and Shopify.
  2. The analysis becomes a plan: "389 verificações sobre os seus dados" (389 checks on your data), producing a work plan prioritized by impact in Brazilian reais. The sample report shows a 67 out of 100 score and an example list of items such as reducing LCP on product pages and making the catalog readable by AI.
  3. You choose what to watch 24/7: SEO (rankings, indexing, schema), performance (field Core Web Vitals), content freshness, checkout funnel, exit signals and tracking integrity. Each monitor can be switched on or paused.
  4. Agents start working. A code improvement becomes a PR for you to review. Anything needing a person becomes a task for your team. The task board shows Backlog, In progress, Needs review and Done columns.
  5. Measure, learn, repeat: "A/B em produção decide o que fica" (A/B in production decides what stays). The sample cycle shows revenue per session going from R$ 4,10 to R$ 4,62, "99% de confiança", and each cycle saves learnings to memory so the next analysis starts smarter.

The managed service

The services list covers experience auditing, site deployment ("storefronts headless de alto volume, no ar em semanas", high-volume headless storefronts live in weeks), app deployment for native commerce apps, a Sales Concierge ("um vendedor de IA que conversa, recomenda e converte"), ongoing support and evolution, integrations with ERP, OMS, CRM and payments, CRO with A/B tests, SEO, GEO and AEO, web analytics, performance, 24/7 observability and automation. Treat this as an agency-style service built around the software, not a self-serve builder. A sample "Operação" feed shows overnight work: an LCP drop from 4,1s to 1,9s on a product page, 84 alt tags generated and reviewed, and a category page variant that won an A/B test.

The evidence from the pages

  • Pricing. The homepage headline is "Operamos sua experiência digital e cobramos pelo resultado" (we run your digital experience and charge for the result). The Farm Rio case lists three points: +10% revenue in key categories, operated by an agent plus deco engineers, and "pago pela receita incremental" (paid from the incremental revenue). The case summary says an agent operating the product experience grew revenue 10%, "medido por A/B em produção". The nav links a Pricing page, but no prices appear on the homepage.
  • Free tool. A free monitoring tool is offered: "Grátis, 2 minutos, sem instalação". You enter a store domain and get a report, with sample findings on mobile speed, AI visibility and reputation.
  • Open source. Studio and CMS are open source, with a "Ver no GitHub" link to the code.
  • Customer voice. A quote from Ágata Esteves, e-commerce at Monte Carlo, says the report confirmed what the team had already identified and showed a deeper path.
  • Content. Recent blog posts include "deco's New CMS - Frequently Asked Questions" (3 Sep 2026) and "Repositioning deco" (3 Aug 2026). The footer links Docs, GitHub, a community and LinkedIn, YouTube and X.

Who it suits and who it does not

deco suits an e-commerce team on VTEX or Shopify that wants its editors to change heroes and banners without tickets, while engineers keep brand tokens locked. It also suits a team willing to hand ongoing optimization, SEO and A/B testing to a service paid on incremental revenue, and teams that want an open source, self-hostable studio kept in their own Git.

It fits a solo founder or a small blog less well. The pitch centers on commerce, storefronts and revenue measurement, and the managed route is quoted by conversation ("Falar com a gente"). The self-host route assumes you already run Git, analytics and a storefront stack, and budgeting starts on the separate Pricing page. The site is also mainly in Portuguese, with an English version available.

More in Visual and Headless CMS

See all