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.
Run it locally · Early access
Ever Works Desktop runs all of Ever Works locally as a single application — the API, the dashboard, the background-jobs runtime, and the database, bundled and shipped as one app. A guided installer walks you through first run, including which job runtime to use. Build Works, run Agents, and operate Missions on your own machine — then connect out to external services whenever you want. It is early access: the app and its installers are built and tested in the open-source repository, but there is no public download page yet.
The full Ever Works API runs locally — no separate server to host.
The web frontend runs inside the app.
The jobs runtime that powers schedules and agent runs, built in.
A local database bundled in — your data on your machine.
The installer asks a short set of questions and configures the stack for you.
Take the installer for your OS from a Desktop App Build workflow run in the open-source repository, or build one from a checkout. There is no public download page yet — that is the one part of this still to come.
Run the whole stack on this machine, or use the app as a native window onto an instance that already runs somewhere else.
Pick how background work runs — bundled locally, or pointed at a runtime you already operate.
Connect an account, or run entirely on this machine with local data.
Create a Work, start an Agent, and watch the run in a live terminal.
Start fully local, then connect outward when you want: point it at an external database or a self-hosted jobs backend, bring any AI / search / deploy / email provider through plugins, and push to your Git and deploy targets exactly as in the cloud. Move pieces to the cloud as you grow, without changing how you work.
The desktop app is early access, and it is worth being exact about which half is which. Both applications are in the open-source repository and unit-tested: the Electron shell with its install wizard, runtime picker and local service supervisor, and a separate, deliberately small app that enrols a machine as an execution node. Continuous integration packages real Windows, macOS and Linux installers on every push that touches them, and keeps each one for fourteen days. What is missing is the last mile: there is no download page, no release channel and no automatic updates, and a build is unsigned unless the run that produced it had the signing certificates. So today you either take an installer from a build run or produce one from a checkout — both are documented step by step in the platform docs.
Turn any machine into an execution node with Ever Works Node, and see every node — including your own Kubernetes nodes — in one Fleet view.
Learn more →Code and content both live in your own Git, and the platform is open source under AGPLv3 — nothing is locked in.
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 →Watch an agent work in real time. Attach, detach, reconnect — and read back the whole session afterwards.
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.