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.
Build type · App
Ever Works researches, ships and maintains content-rich websites and Git repositories. Apps take the second half further: an App is a Work whose code is an existing repository you choose, rather than a site Ever Works generates. Ever Works will link it, fork it or make a private copy in your own GitHub account, build and run it, and let your Agents keep evolving it through pull requests. Apps are in active development and switched off by default — none of this is available to use yet.
In the platform an App is a Work of kind App — an App Work. It keeps what makes a Work a Work, such as the Memory tab, the Deploy tab and your Agents, and drops what only makes sense for generated content, such as items, categories and content pipelines.
Paste a GitHub URL. Before anything is created, Ever Works will show what it found: who owns the repository, whether you can push to it, whether you already have a fork, its licence, and whether a ready-made Blueprint exists for it.
Link a repository you can already push to. Fork one you cannot, into your own GitHub account or an organization you belong to — never a shared platform organization. Or make a private copy, which cannot propose changes back to the original project. Deleting an App later never deletes the original project, and your fork only if you ask.
Everything needed to build and run the app lives in your repository, in the spec block of .works/works.yml: how to build the image, the components to run, the databases it needs, its settings, jobs, scheduled calls, health checks, smoke tests and the checks a change must pass. You can edit it by hand like any other file.
Images will be built by a workflow Ever Works writes into your repository, on GitHub Actions, and pushed to GitHub’s container registry with the image digest checked against the registry. Builds run on the repository owner’s GitHub Actions minutes, so they count against that account.
Pick a deploy target: None, to evolve the code without running it, or your own Kubernetes cluster through the same kubeconfig your website Works deploy with. Each App gets a namespace of its own with network policies around it, and its address is your verified custom domain or a managed subdomain.
Once an App is live it will appear as a tile in the App Launcher in the top bar, next to any other Works you choose to show there. You can pin, hide and reorder tiles for yourself. The launcher opens the address in a new tab; it never signs you in.
For a well-known open-source app you should not have to work out the build yourself. An App Blueprint is a ready-made App spec for one project, kept in its own public repository and listed next to the other Ever Works templates.
Each Blueprint lives in a public repository named ever-works/<app>-template with the topic ever-works-app-blueprint. It holds metadata only — never the app’s source code. Your App’s code is your own fork or copy of the original project; the Blueprint records how to build and run it.
The public ever-works/templates repository on GitHub is the listing. It holds no app code, only the rows that point at each Blueprint’s own repository, the licence registry and the checks every entry must pass.
The first Blueprints cover a web analytics app and a scheduling app, and the Template Catalogs page names them. Both are drafts: neither has been verified on a cluster yet, and they will be marked that way until they have.
Before anything runs, Ever Works reads the project’s licence and sorts it into a class. Green licences run on your cluster without an extra step. Amber and red licences, and any licence Ever Works cannot identify, will run on your own cluster only after you confirm that your use is allowed — and you will be asked again if the licence changes. A repository whose licence GitHub cannot name is treated as red. The classification is an automated reading of the licence files, not legal advice.
The point of an App is that it keeps changing in your direction. One honest caveat from the build: for now, a run in the Ever Works cloud commits changes to an App without pushing them, until an isolation check for those runs lands; runs on your own Fleet machines push their branch.
In chat, as a Task, as a Goal, or as a whole Mission — “build my own booking product on top of this app”.
Changes happen on a branch of your repository, and every push is checked against the App’s rules, which keep protected branding files read-only to agents.
The checks your App spec declares will run first, and the change will arrive as a pull request you review in your own Git.
When the pull request is merged, the App will be built again and redeployed to its target.
None of this can be used on the hosted platform today, and the switches behind it are off by default. A good part of the engine is already built, behind those switches. The rest is still being built, and Apps will stay marked coming soon until you can create one from the dashboard.
The buildable unit — websites, blogs, directories, landing pages — researched, written, coded, deployed, and kept fresh.
Learn more →Every Work is generated from a template — production-grade Next.js and Astro bases — so you never start from a blank page.
Learn more →Every catalog Ever Works ships — website and Work templates, Mission playbooks, twelve starter Agents, a public Skills library and more than thirty prebuilt companies.
Learn more →Where a Work deploys, where the platform itself runs, which engine executes background work, and where uploads, data and vectors live — each one a plugin you pick.
Learn more →Run Ever Works in the cloud, self-host the platform with Docker Compose or Kubernetes manifests, and deploy your Works to Ever Works hosting, Vercel, or your own cluster.
Learn more →A plugin is a capability the platform does not have on its own — a model, a search engine, a Git host, a deploy target — and Ever Works ships 102 of them.
Learn more →Describe what you want to build. Ever Works researches it, ships it, and keeps it improving — content and code, owned in your own Git.