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.
Product
Ever Works is developed in the open at github.com/ever-works/ever-works: the API, the dashboard, the CLI, the MCP server, the agent and pipeline packages, the plugins and the documentation, in one monorepo. It is released as the Community Edition under the GNU Affero General Public License v3 — and everything it builds for you, code and content alike, is committed to repositories in your own account.
Not a demo repository next to a closed product: the images the managed deployment runs are built from the repository you can clone.
The NestJS API, the Next.js dashboard, the public CLI, the MCP server, the agent and pipeline packages and 102 plugins — one Turborepo and pnpm monorepo under AGPLv3.
The four container images behind the managed deployment — web, API, MCP and docs — are published publicly under ghcr.io/ever-works, so a self-hosted install runs exactly what the cloud runs.
Every page on docs.ever.works is a Markdown file in the same repository. The Edit this page link opens the exact source file, so a docs fix is an ordinary pull request.
The website templates your Works are generated from are open source and forkable, and the Skills catalog and the prebuilt-company catalog are public repositories in the ever-works organization.
ever-works-cli is published to npm under the MIT license: npm install -g ever-works-cli and the ever-works binary talks to the same REST API as the dashboard.
The default license is the Ever Works Platform Community Edition license, which is the GNU Affero General Public License v3.0. You can use, study, change and redistribute the platform. The AGPL is a strong copyleft license built for network software, so if you run a modified version as a service for others, its complete source has to be available under the same license. Teams that want to keep their changes proprietary can take a commercial license instead — the pricing page covers it.
Open source covers the platform. Ownership covers what the platform makes for you — and that half is the same whether you self-host or use the cloud.
A Work provisions its repositories in your own Git account: a data repository holding the structured content, a readable Markdown mirror, and the website repository that is built and deployed. Every autonomous change is a commit you can read.
Agent work arrives as pull requests on their own branches, and out of the box the merge policy leaves the merge to a human. Anything that did land reverts like any other commit.
.works/works.yml at the data-repository root carries the Work’s name, prompt, model, deploy provider, schedule and plugin choices, with a published JSON Schema behind editor completion. Every successful generation writes the file back with your own fields preserved.
Export your account as versioned JSON with secrets masked, keep it synced to a private GitHub repository, or point a self-hosted install at the same repositories. Turn Ever Works off and every site, post and commit is still yours.
The project takes issues, pull requests and plugins from anyone. This is where each one goes.
Clone github.com/ever-works/ever-works, install with pnpm on Node 22 or newer, and run the dashboard and API locally — or bring the whole stack up with Docker Compose.
Bugs and feature requests go to the issue tracker on GitHub. Security vulnerabilities go privately to security@ever.co, never to a public issue.
Base pull requests on the develop branch and follow the contributing guide in the repository. Documentation changes follow the same path.
Add a capability the platform does not have against the @ever-works/plugin SDK — one manifest, one class, JSON-schema settings — and talk it through with the team on the project’s Discord.