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.
Feature · Run anywhere
For Ever Works, location means where things run — not where people are. A Work’s website can go live on managed hosting, on your own Vercel account or on a Kubernetes cluster you own, under your own domain. The platform itself can run in the Ever Works cloud, on your own servers or on a single machine, and your Agents can do their work on machines you enrol. Each of those is a choice you make, and you can make them independently.
Pick the target when you create a Work or later on its Deploy tab. Domains and database settings are kept on the platform, so switching targets re-syncs them rather than losing them.
No kubeconfig to paste, no registry to wire, no DNS zone to own. The Work gets a namespace on the shared cluster, a public address at <slug>.ever.works and a PostgreSQL database of its own.
Paste your own Vercel API token, verified on save. Deploying pushes the site to its GitHub repository and Vercel serves it from its global CDN with HTTPS already on.
Paste a kubeconfig for any cluster on 1.27 or newer — EKS, GKE, AKS, k3s or on-prem. Ever Works probes it on save, each deploy is a server-side apply, and cert-manager issues the certificates.
On the Work’s Deploy tab, add a hostname and copy the exact DNS record to create. Verify DNS runs a live lookup and can promote the domain to the Work’s primary address; with the Cloudflare DNS plugin configured, the record is written for you.
The same applications — dashboard, API, MCP server and docs — however you choose to host them, and as many machines as you want to lend your Agents.
Sign in and start building. Background workers, the database and the deploy pipeline are operated for you.
Self-host the full stack from the public container images, or start with the SQLite demo that runs with one command and needs no other infrastructure.
The repository carries the dev, stage and prod manifests the platform itself is deployed with. Apply them and pin your own image tags.
Install ever-works-node on a laptop, workstation or server and it joins your fleet over an outbound-only channel, with nothing exposed to the internet. Nodes of your own Kubernetes cluster appear in the same Fleet view.
The API, the dashboard, the job runtime and a database in one app on your own machine. Installers are built by CI in the open-source repository; there is no public download page yet.
Decide what an Agent’s runs may reach: an Environment pins the packages that must be present and can limit outbound networking to the hosts you list. Assign it to an Agent and every run starts from it.
Two deployment plugins exist for Works — Vercel and Kubernetes — alongside Ever Works managed hosting. That is the whole list, and a few things people often expect are not on it.