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 an open-source agentic runtime, not a page builder. You give it a goal; it researches the topic, writes the content, generates the code from a maintained template, deploys the result, and then keeps it current — with code and content committed to Git repositories you own. Four nouns carry the whole model: Missions, Ideas, Works and Agents.
Everything in the product is one of these, and each one feeds the next: a Mission proposes Ideas, an Idea becomes a Work, and Agents keep the Works moving.
A standing goal bigger than any single site — “build out our company presence online”. It runs once or on a cron you set, proposes Ideas that ladder up to the goal, and stays inside a spend cap and a limit on how many unbuilt Ideas may be outstanding.
A single proposal: one Idea becomes one Work. Ideas arrive from a running Mission, on a cadence, on request, or from you typing one. Build it, dismiss it, or rebuild it later — capturing an Idea costs nothing.
The buildable unit: a website, landing page, blog, directory or awesome-list repo. Each one is generated from a production template, lands as Git repositories in your own account, deploys to the target you choose, and refreshes on a schedule.
Named AI workers — a CEO, a Researcher, an Editor — each with a role, a scope, a budget, its own mailbox and tool permissions that start switched off. Give one a heartbeat and it wakes on schedule to take the next useful action; group them into Teams.
Brand voice, legal copy, SEO rules, personas and research live on each Work’s Memory tab, versioned in its Git repository and read by every run — so the tenth generation knows what the first one learned.
This is the runtime’s loop, in the order it happens. The first three steps build the Work; the last one is why it does not go stale.
Before a word is written, agents gather and score sources and produce a brief per page — angle, audience, sources to cite, points to cover. For directory and awesome-repo Works the same pass builds the catalogue of items the Work will list.
A maintained Next.js or Astro base is cloned into a website repository in your account, and the writing pass fills a separate data repository with items, categories, tags, collections, cited references and comparisons.
The first deploy is a human action: to Ever Works managed hosting, Vercel, or your own Kubernetes cluster, with custom domains on any of them. Nothing publishes a freshly generated Work on its own.
Pick one of seven cadences, hourly to monthly, and the pipeline re-researches, rewrites stale pages, re-validates item URLs and redeploys. Repeated failures pause the schedule instead of burning budget, and a Mission with auto-build on keeps proposing the next Work.
Continuous operation is opt-in and bounded. These are the brakes, and they are on the same screens you already use.
Caps per Work, Idea, Mission and Agent, approval rules, limits on items per run and on outstanding Ideas — and pause or resume on any Agent, Mission or schedule.
With task isolation on, each agent Task gets its own branch and checkout, must pass the quality gates you declare, and comes back as a pull request. Out of the box the merge policy leaves the merge to a human.
When an agent needs a call only you can make — a blocking question, an approval, an escalation — it writes to your Inbox, and your reply resumes the run that was waiting on it.
Every generation, deployment and schedule run is in the Activity log, and every change to a Work is a Git commit you can review and revert.
The loop above is live: Missions, Ideas, the five Work kinds, Agents, Tasks, schedules, deploys and Git ownership all work now. The writer behind the kinds is not equally deep yet — directory and awesome-repo Works have the dedicated content generator, while website, blog and landing-page Works are written by that same items pipeline and their kind-specific generators are rolling out. And the loop starts switched off on a new account, so nothing builds until you say so.