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 · Company builders
MCP-native agent control plane with an agentic CMS
deco Studio is an MIT control plane where agents operate the storefront or content site you already run — through reviewable pull requests, under SSO, tool-level grants and a credential vault. Ever Works starts from an idea: it researches the space, writes the content, generates the site, deploys it, and keeps improving it on a schedule — content and code in your own Git.
Of everything we have researched, deco Studio is the closest thing to Ever Works: both are open source, both are Git-native, and in both an agent’s work reaches the site as a pull request a human reviews rather than a silent write. The difference is where each one starts. deco is a control plane for the agents and the site you already have — every agent published as its own MCP endpoint, one-click OAuth connections into an encrypted vault, OIDC and SAML SSO, a trace of every tool call, and an agentic CMS descended from deco.cx that lets a non-developer edit the live storefront with an in-place preview. Ever Works starts from an idea and runs longer: it researches the niche, writes the publishable content, generates the site from a template, deploys it, and re-runs that loop on a cadence you set. Their enterprise controls and their trace UI are ahead of ours today, their licence is more permissive, and their desktop app is published where ours is still early access. What Ever Works has instead is the front half — research turned into a structured content set — plus a standing goal loop that keeps producing work when nobody opens a card, and budgets that stop spend rather than only measuring it.
It would be wrong to say deco cannot research or write: its org-level pilot has a web-search mode and a deep-research mode that returns a synthesized multi-source report, and its commerce roster lists blog and content authoring alongside technical SEO and catalog enrichment. The narrower and more useful difference is what the research turns into. Ever Works’ pipeline extracts items, generates the taxonomy, validates each item’s sources, curates collections and writes A-vs-B comparison pages with their SEO metadata, then commits all of it to the Work’s data repository — a content set with a shape, not prose returned in a thread. Being straight about where we are: the directory kind is the mature one. There is no dedicated blog-post or landing-copy generator yet, so Blog, Website and Landing Page Works are fed by that same items pipeline while those writers roll out.
Both products run agents unattended, so the honest comparison is the envelope each one gives them. A deco automation is one agent, one prompt, one trigger, inside documented limits: ten concurrent runs per organization, a five-minute run timeout, a five-minute minimum schedule, every tool call auto-approved with no review step, and the automation deactivated outright if the person who created it leaves the organization. Ever Works’ Scheduled Updates re-run the whole generation pipeline on one of seven cadences with retries and an auto-pause after repeated failures, Missions tick on their own schedule and can build the Ideas they propose, and the output lands as commits and pull requests behind quality gates and a merge policy that decides per tenant, organization, Work or Agent whether an Agent may land its own change.
This is the closest row on the page and deserves precision rather than a flourish. Both put agent changes through pull requests and both version site content in Git. deco’s licence is MIT, which is more permissive than our AGPLv3 and genuinely easier if you intend to embed or fork the runtime inside a closed product — a point in their favour, not ours. What Ever Works offers instead is that nothing is gated: there is no paid feature tier, so no enterprise-only module is held back from the repository. Around that, each Work carries its own repositories plus a typed Knowledge Base kept in Git with a review queue that holds agent-authored memory out of context until a human accepts it, and every Task gets a branch and a private checkout. deco’s counterpart is a shared organization filesystem — useful, but untyped and unreviewed.
deco’s unit of autonomy is a trigger on an agent, so a person or its built-in pilot originates every task. Ever Works adds the layer above: Missions are standing goals that keep proposing Ideas, Ideas become Works, and a named, persistent Agent team — with Skills, Teams, scorecards and its own mailboxes — carries them out under budgets that block the next AI call once a cap is hit, at Work, Mission, Idea and account scope. deco measures cost extremely well but still lists spend caps as a roadmap item, so treat that lead as real today and time-limited. The loop also ends in an artifact we ship: the site is generated, deployed and kept. The Store builder is still coming soon and company incorporation through a formation provider is planned, so today that shipped artifact is the site and the repositories behind it.
Ever Works vs deco Studio, head to head.
| Feature | Ever Works | deco Studio |
|---|---|---|
| Prompt → working app/site | ✓ | Operates the site you bring |
| Researches the topic for you | ✓ | Web search + deep research |
| Writes the content (copy, posts, SEO) | Directory data today; posts rolling out | Blog and SEO agents |
| Generated code from a template base | ✓ | Agents edit your repo |
| Ongoing autonomous maintenance | Scheduled | Automations, 5-min runs |
| Content version-controlled in Git | ✓ | ✓ |
| Code in your Git | ✓ | ✓ |
| Open source | AGPLv3, no paid tier | MIT |
| Self-hostable runtime | ✓ | ✓ |
| No vendor lock-in | ✓ | ✓ |
| Enterprise SSO (OIDC / SAML) | Work-level roles | ✓ |
| Per-tool-call trace with payloads | Partial | ✓ |
| One-click OAuth MCP install | – | ✓ |
| Published desktop app | Early access | ✓ |
Choose deco Studio if the site already exists and the job is to govern the agents that change it — especially an enterprise commerce or content team on their stack, where the agentic CMS gives non-developers visual editing of the live storefront and the packaged roster covers technical SEO, catalog enrichment, per-pull-request Lighthouse checks and error-spike detection. It is also the better answer to a security review today: OIDC and SAML SSO, custom roles composed from an allowed-action list, scoped API keys, and a per-tool-call trace with inputs, outputs and duration are all shipped, and none of them are things Ever Works can match yet. Add one-click OAuth installs for MCP servers, an agent you can run on your own coding-CLI subscription, a desktop app installable from a Homebrew cask, two-way Jira board and sprint sync, per-PR deploy previews, an MIT licence that is friendlier than AGPLv3 for embedders, and the option to have them operate the site under an outcome-based contract — and for that buyer the case is strong.
Visit deco Studio ↗Give Ever Works an idea and its agents research the space, write the content, generate the code, deploy it, and keep it improving — all version-controlled in your own Git.