We’re building Ever Works in public. Some things may be incomplete, missing, or broken while we continue improving the platform.We’re building Ever Works in public — expect a few rough edges.
Compare · Store builders
Open-source headless commerce platform
Saleor is a GraphQL commerce engine for engineering teams — catalog, checkout, payments and orders behind an API you build a storefront on. Ever Works researches a topic, writes the content, generates the site and keeps it improving on a schedule, content and code in your Git — with its Store builder still coming soon.
Saleor is a composable, GraphQL-native commerce platform: a BSD-3-Clause Python and Django core covering catalog, channels, pricing, promotions, carts, checkout, orders, fulfilment and payment orchestration, with a separate React dashboard and a storefront you build or fork. It is deliberately infrastructure rather than a builder — no drag-and-drop, no describe-it-and-get-a-store — and its own positioning is about owning your commerce stack instead of renting it, while conceding that hosted SaaS platforms win on app-marketplace breadth and on launching with no engineers at all. Through 2026 it added the pieces that make a store legible to software: configuration declared as code and applied from a CLI, structured attributes on products and now customers, 160+ webhooks, and the first implementation of the Agentic Commerce Protocol among open commerce platforms. Its AI story is access, not labour: the developer docs describe pointing an MCP GraphQL server at the schema and publishing an llms.txt index, and state plainly that Saleor ships no built-in LLM features — the shopper-facing conversational search layer is a cloud pilot and the merchant analytics surface announced in July 2026 is cloud-only and not yet generally available. Ever Works is on the other side of that line: it supplies the workforce — agents that research a topic, write the content, generate the site from a template, deploy it and keep working on a schedule under budgets, quality gates and a merge policy — but it does not sell anything yet, because the Store Work kind is coming soon and there is no catalog, checkout or payment path today. The honest split, and it is a wide one: Saleor runs real commerce at real GMV and Ever Works does not, while Ever Works produces researched content and unattended upkeep that Saleor has no equivalent for — and since the planned Ever Works Store is designed to connect to a self-hostable open-source commerce backend, a hosted platform, or your own, the two may end up stacked rather than opposed.
Saleor is explicit that it ships no built-in LLM features: its AI documentation is about letting your agents read and mutate the commerce schema over MCP, and its shopper-facing conversational search is a cloud pilot. Nothing inside it studies a niche, drafts copy or decides what to change next. Ever Works is the opposite shape — its pipeline analyzes a domain, discovers entries through web search, extracts and deduplicates them, validates sources, assigns categories and tags and then writes descriptions and SEO metadata, reading each Work’s Knowledge Base for voice, brand and persona on every run. Be precise about the state of that today: it is deepest for directory-style content, the Blog, Website and Landing Page kinds are wired end to end but still fed by that same items pipeline while dedicated post and landing-copy writers roll out, and the catalog research and product copy described on the Store builder page are planned, not shipped.
Saleor’s configuration-as-code applies the store you describe in files — a real improvement over clicking through an admin, and a mature version of a pattern Ever Works only has for site configuration — but it still applies your decisions, on your command. Ever Works makes the loop the default: scheduled updates on seven cadences from hourly to monthly with retries and auto-pause after repeated failures, Agent heartbeats on a cron, and scheduled Missions that keep proposing Ideas. Around that loop sit the controls unattended work needs — spend caps enforced before an AI call runs, quality gates that send red work back to the Agent instead of to you, branch-and-checkout isolation per Task, and a merge policy that starts conservative with Agents opening pull requests for people to merge.
Both projects are open source and self-hostable, and the fair comparison is about gating rather than permissiveness: BSD-3 is more permissive than AGPLv3 for anyone embedding the code, and Saleor Core is complete under it. The asymmetry is above the core — the storefront foundation a merchant actually forks is published under a Functional Source Licence that converts to Apache 2.0 after two years rather than an OSI-approved licence, the announced merchant analytics surface is cloud-only and not yet generally available, and the conversational shopping layer is a cloud pilot. Ever Works is plain AGPLv3 with no feature behind a commercial tier, runs on the model provider you choose across eleven provider plugins including local models, and self-hosts on Docker Compose or Kubernetes. Every Work gets repositories in your own GitHub account holding the content, the configuration, the Knowledge Base and the generated site code, so an overnight run is a diff you can review and revert.
Saleor assumes a team: Python and Django engineers to extend the core, frontend engineers for the storefront, and DevOps capacity if you self-host, with a managed entry tier priced for a merchandising budget. Ever Works assumes one person with a goal: a Mission keeps proposing Ideas, accepted Ideas become Works built from prebuilt templates, and named Agents with their own budgets, heartbeats and per-tool grants keep each Work moving, organized into Teams alongside people with Manager, Editor and Viewer roles. Where that model does not reach yet is commerce itself — the Store Work kind is coming soon, and when it lands it is designed to connect a commerce backend you choose through deployment plugins rather than to replace one, which makes an engine like Saleor as plausible a partner as a rival.
Ever Works vs Saleor, head to head.
| Feature | Ever Works | Saleor |
|---|---|---|
| Prompt → working app/site | ✓ | You build the storefront |
| Researches the topic for you | Web research; item-shaped today | – |
| Writes the content (copy, posts, SEO) | Items pipeline today | – |
| Generated code from a template base | ✓ | Storefront foundation to fork |
| Ongoing autonomous maintenance | Scheduled | Apps and webhooks you build |
| Content version-controlled in Git | ✓ | Store config as code |
| Code in your Git | ✓ | ✓ |
| Open source | AGPLv3, no paid tier | BSD-3 core; storefront FSL |
| Self-hostable runtime | ✓ | Docker Compose |
| No vendor lock-in | ✓ | Core is portable |
| Catalog, checkout and payments | Planned | ✓ |
| Product, variant, price and stock model | Planned | ✓ |
| Agentic-commerce protocol (ACP) | – | ✓ |
| Enterprise SSO / RBAC | Work-level roles | ✓ |
Choose Saleor whenever you actually need to sell something and you have engineers to point at it. It is a production commerce engine with catalog, channels, multi-warehouse stock, checkout, payment orchestration, tax and shipping, promotions, returns and B2B patterns already solved, exposed through one coherent GraphQL API, extended through apps and 160+ webhooks, and configurable as code — with a permissive BSD-3 core you can self-host on Docker for no licence fee, free non-commercial sandboxes to prototype in, and a managed cloud with named delivery support and a compliance posture when procurement asks, priced from about $1,599 a month for up to $200k monthly GMV with an overage above that. It is the right pick over Ever Works for anything transactional today, because Ever Works has no commerce at all: its Store builder is coming soon, and nothing in the platform takes a payment. Saleor is candid about its own limits too — it says it is not built for merchants who want every decision preconfigured for them, it concedes hosted platforms have far larger app ecosystems, reviewers call it the most operationally complex of the open-source commerce engines, and Saleor itself says a team that wants to start selling in a weekend without developers should choose a hosted SaaS platform instead.
Visit Saleor ↗Ever Works already researches a topic, writes the content, generates the Next.js code, deploys it, and keeps re-running on the cadence you set — all in your own Git. The Store builder (storefront, catalog, checkout) is on the way, and the sites the runtime generates today already carry subscription checkout, per-plan gating, sponsor ads and promo codes.