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 Cloud is the open-source platform, operated for you at app.ever.works. Background workers, databases and the deploy pipeline run on our side, so the first thing you do is describe what you want rather than provision a server. Every Work still lands in Git repositories you own, so starting in the cloud never means staying there.
The hosted app takes care of the parts that usually come before the interesting work. Each managed piece is independently available, so you can adopt them one at a time.
Type a prompt on this site and you land in onboarding with a guest session already minted, so your first Work generates before you sign up. Add an email and password to keep it — unclaimed guest work is cleared after three days by default.
The setup wizard starts on Ever Works AI, a managed repository, a database provisioned per Work and hosting on Ever Works — nothing to configure. Swap any of them for your own Git provider, PostgreSQL, Vercel or Kubernetes cluster, one short step at a time.
Deploy to Ever Works hosting and the platform supplies the namespace, a public address at <slug>.ever.works with the DNS record already behind it, and a PostgreSQL database for the Work. No kubeconfig to paste, no registry to wire, no DNS zone to own.
Add your own hostname on the Work’s Deploy tab, create the record the page shows you, and press Verify DNS. It works on managed hosting, Vercel and Kubernetes alike, and with the Cloudflare DNS plugin the record is written for you.
The REST API answers at api.ever.works with an ew_live_ key from Settings → API Keys, and a hosted MCP endpoint at mcp.ever.works/mcp lets an MCP-compatible assistant drive your Works using your own sign-in token.
From a sentence to a live site that keeps itself current, using the screens as the product names them.
Create an account at app.ever.works, or type your idea into the prompt box here and decide about an account later. Either way you land on the dashboard with the setup wizard open.
Ten steps, every one skippable, each answer mapped to a Settings page you can change later. With a prompt in hand, the last step reads Ready to generate — press Generate now.
Open the Work’s Worker tab to watch progress stream, and cancel mid-flight if the brief was wrong. When it looks right, deploy from the Deploy tab — the first deploy is always your call.
Arm a schedule, hourly to monthly, and the Work re-runs itself, pausing rather than burning credits if something is genuinely broken. Add an Agent from the catalog so someone is minding it between runs.
Usage in the cloud is metered in credits. What each plan includes is on the pricing page; this is how the metering itself works.
Cost is attached to the run that caused it, and every credit added or spent is a line in a ledger you can trace back to a session — your balance is the sum of that ledger.
A free allowance lands every day, so light use stays free. A paid plan adds a monthly allowance on top.
Point the platform at your own model keys and those runs cost no credits at all.
Billing shows your plan, balance, invoices and the ledger. Usage & Credits breaks a 7-day, 30-day or calendar-month window down by day, model, agent and Work, and exports it as CSV.
The cloud runs the same open-source platform you can run yourself, from the same published images. That is what keeps the hosted app honest: every Work’s code and content sit in repositories you own, your account exports as a file, and the self-hosted stack is always one decision away.