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.
For Remote Teams
A distributed team already works asynchronously; what costs it is the handoff — the update nobody wrote, the question that waited a day for the right time zone. Ever Works takes most of those handoffs out of the work around your product. Works refresh on their own schedules, Agents wake on heartbeats, anything that needs a person waits in that person’s Inbox, and the whole team works in one Organization on repositories in your own Git.
The structure lives in the product, not in a wiki page somebody has to keep current.
Invite colleagues by email from Settings → Organization → Members. Each link is single-use, bound to the address you invited and valid for seven days by default; revoke a pending one and it stops working at once. Switch between Organizations from the top of the sidebar.
Every Work has its own roster: Owner, Manager, Editor and Viewer. Managers invite and change roles, Editors change content and trigger generation, Viewers read, and only the Owner can delete the Work — so a collaborator on another continent can edit exactly one site and nothing else.
Nested teams hold people and Agents on one roster, with a manager Agent and the Works, Tasks, Missions and Ideas each team owns. The Org Chart draws all of it live, so “who looks after the docs site?” has an answer anyone can look up, whatever the hour.
Each Work keeps a Knowledge Base on its Memory tab — brand voice, glossary, research — and Agents read it on every run. Sidebar → Memory gathers every Work’s documents into one searchable list, and decisions are recorded as proposed, accepted or rejected, so a teammate starting their day reads the same context the Agents do.
What happens between one person logging off and the next one logging on.
Works refresh on one of seven cadences, hourly to monthly. Agents wake on a cron heartbeat and pick the single most useful next action even with nothing assigned, and recurring Tasks spawn on schedule. Activity → Schedules lists every timer in the account with its owner, cadence and next run.
An Agent that cannot proceed asks instead of guessing. The question lands in its owner’s Inbox with one-click options, one of them marked Recommended, and the run stays parked until the answer arrives — then picks the reply up and carries on.
Anything flagged destructive, cross-scope, high fan-out or a budget override queues for a human, whatever the Agent’s mode. Approve or reject from the dashboard home or from the same item in the Inbox; a decision is final and lands in the activity log.
Digests summarize the last day or week from real records — agent runs, tasks that moved, pull requests opened, events from connected sources — composed at 07:15 UTC. A personal digest covers your own work; an organization digest is one shared briefing that can carry an AI-written summary on top of the counts.
Asynchronous work only holds up when everyone knows exactly who is asked what. Most of that is in place today. A few parts are coarser than a large distributed team might expect, and they are worth knowing before you plan around them.