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.
Lifecycle · Step 4
Once content and code are ready, the deploy pass ships the Work to your target of choice. Managed hosting, Vercel, or a cluster you own — all wired up through the platform’s deployment providers. Your domain, your provider, your control.
The platform-managed target. No credentials to paste — hosting, certificates and DNS are operated for you.
Zero-config deployment with custom domains and a global CDN.
Deploy a Work to your cluster for scale and control — manifests generated for you.
Run the Kubernetes target on EKS, GKE, AKS, k3s or on-prem — one kubeconfig, any cluster. There are no separate AWS, GCP or Azure deploy plugins: those names appear in the plugin catalog as secret-store resolvers.
You don't reach into deploy configs by hand. The runtime knows which target each Work uses and ships there when you deploy. There is no preview-then-promote step: a deploy goes to the live site, and a redeploy is a rolling update of the same site.
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 →Production-grade Next.js code, generated alongside the content — your repo, your stack.
Learn more →Runs on a schedule. Keeps content current, code patched, dead links fixed — long after launch.
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.