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
The Ever Works Store builder is coming soon — storefront, catalog and checkout are planned, not shipped. Here is what the runtime already does around a store: research the topic, write the content, generate the code, deploy it, keep re-running on a schedule, and ship monetization inside the site it generates — subscription checkout, per-plan feature gating, sponsor ads with an approval workflow and promo codes — with content and code owned in your own Git.
Commerce platforms give you a store to fill and run. Ever Works is the runtime around it: research, written content, generated code, and scheduled upkeep that arrives as pull requests. The sites it generates already take money, too — subscription checkout across four payment providers, per-plan feature gating, sponsor ads with an approval workflow and promo codes — so selling a placement or a membership is shipped. The store itself — catalog, cart, checkout, orders — is the part still on the way, and every block below says which side of that line it sits on.
Planned. Product-level research — sourcing, specs, pricing context — lands with the Store builder. What ships today is the same research pipeline pointed at directory-shaped items, which is why the directory pages are the honest proof of the machinery.
Planned. Product descriptions, collection pages and store SEO are part of the Store builder. Today the runtime writes directory items, categories and tags, with dedicated post and landing-copy writers rolling out.
Planned as a store template. The generator itself is shipped: Ever Works produces production Next.js code from a template base and commits it to your repo — today for content-rich sites rather than storefronts.
Planned. Cart, checkout, payments, orders, tax and shipping are not part of the runtime yet. If you need to take money this quarter, one of the platforms on this page is the right answer — and each one-on-one page says so plainly. Worth drawing the line precisely, though: that gap is the store’s checkout, not the site’s. The directory and content sites Ever Works generates today already ship subscription checkout across four payment providers, per-plan feature gating, sponsor ads with an approval workflow and a promo-code system — all listed on /platform/whats-included — so selling a placement or a membership on the site works today, and selling a physical product with a cart, orders, tax and shipping is what the Store builder adds.
Shipped. Pick a cadence and each run re-runs the pipeline, opens a pull request, and merges under your merge policy — with retries and auto-pause after repeated failures. The same scheduler will drive catalog refreshes once the Store builder lands.
Shipped. Content and code are committed to your own Git, the runtime is open source (AGPLv3) with no paid tier, and it is self-hostable with your own model providers — including local ones.
The Ever Works Store builder is coming soon. Every store-specific cell below says "Planned" — this page shows how Ever Works will compare, and what it already does around a store today.
| Feature | Ever Works | Shopify | BigCommerce | WooCommerce | Medusa | Saleor |
|---|---|---|---|---|---|---|
| Scope & outputWhat the tool produces from your idea. | ||||||
| Topic → researched content | Directory data today | You supply the catalog | – | – | Extracts products you point it at | – |
| Writes the copy (pages, posts, SEO) | Directory data today; product copy planned | Product copy via Sidekick | Apps; enrichment announced | You write it | Captures existing product copy | – |
| Generated site code (Next.js) | ✓ | Themes + AI code edits | Stencil themes; Catalyst | WordPress theme, not generated | Scaffold + starter storefront | Storefront foundation to fork |
| Commerce — Store builder coming soonEver Works does not ship a store yet; every cell in this group is Planned. | ||||||
| Storefront, catalog and product model | Planned | ✓ | ✓ | ✓ | ✓ | ✓ |
| Cart, checkout and payments | Planned | ✓ | ✓ | ✓ | ✓ | ✓ |
| Orders, tax, shipping and fulfilment | Planned | ✓ | ✓ | ✓ | ✓ | ✓ |
| LifecycleWhat happens after the first launch. | ||||||
| Ongoing autonomous maintenance | Scheduled | Standing AI loops | Admin assistant, announced | You maintain it | In-editor agent sessions | Apps and webhooks you build |
| Scheduled runs arrive as pull requests | ✓ | – | – | – | – | – |
| Budgets, quality gates and merge policy on agent work | ✓ | – | – | – | – | – |
| Ownership & opennessWho controls the data, the code, and where it runs. | ||||||
| Content version-controlled in Git | ✓ | – | – | Your database; export or API | Catalog in PostgreSQL | Store config as code |
| Code in your Git | ✓ | Theme code, two-way sync | Catalyst storefront (MIT) | ✓ | ✓ | ✓ |
| Open source | AGPLv3, no paid tier | Platform closed; Hydrogen MIT | Storefront only; engine closed | GPLv3 | MIT; RBAC/SSO commercial | BSD-3 core; storefront FSL |
| Self-hostable | ✓ | – | – | Self-hosted only | ✓ | Docker Compose |
A "–" means the capability isn't a focus of that product, not that it's impossible. Each tool is strong at what it set out to do — see the individual pages for the honest, full picture.
Hosted commerce platform with an agentic layer
Shopify runs the transactional stack — checkout, payments, orders, POS, B2B — and now syndicates catalogs into AI shopping surfaces on a plan that costs nothing per month. The Ever Works Store builder is coming soon; what ships today is the research, the sourced directory content, the generated code, and a schedule that keeps improving them, all in your own Git.
Read the comparison →Hosted SaaS commerce platform
BigCommerce runs a working shop from the day you sign up — catalog, checkout, payments, tax and shipping, with B2B depth sold as a separately quoted add-on on the top tier. Ever Works researches the topic, writes the directory content, generates the site and keeps it improving on a schedule, with content and code in your Git. Its Store builder is coming soon.
Read the comparison →Open-source WordPress commerce engine
WooCommerce is the open-source commerce engine for WordPress — a free core, no revenue share, self-hosted, and assembled by you. Ever Works researches the niche, writes the content, generates the site into repositories you own, and keeps working on a schedule. Its Store kind is still coming soon, so this compares an engine with a workforce.
Read the comparison →Open-source headless commerce platform
Medusa is the open-source commerce engine a store gets built on — MIT modules for cart, payments, orders and inventory, a durable workflow engine, a managed cloud, and a browser build surface. Ever Works researches a topic, writes the content, generates the site and keeps it running on a schedule; its Store builder is coming soon.
Read the comparison →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.
Read the comparison →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.