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.
Platform · Extensibility
Open Plugins in the dashboard sidebar and you see every plugin your install carries: 102 packages across the 19 categories that ship with a plugin today. Enable the ones you want, configure them with your own keys, and choose which plugin serves each capability — for your whole account, or for a single Work.
Every plugin declares exactly one category in its manifest, so the counts below account for all 102 of them — nothing double-counted, nothing left over.
Anthropic, OpenAI, Google Gemini, xAI Grok, Groq and Mistral, plus the local runtimes Ollama, LM Studio and vLLM — and the OpenRouter and Vercel AI Gateway routers on top. They all sit behind one interface, so changing which model writes your content is a setting, not a rewrite.
The pipeline is the thing that actually builds a Work. Choose the default 15-step generation pipeline, the agent pipeline, or a coding agent — Claude Code, Claude managed agents, Codex, Gemini CLI, OpenCode, Hermes Agent — alongside the go-to-market pipeline and bridges to Zapier, Make, Composio, Activepieces and SIM AI.
Nine search engines feed the research pass: Brave, Bright Data, Exa, Firecrawl, Linkup, Perplexity, SerpAPI, Tavily and Valyu. Six extractors turn a page, a PDF (with OCR fallback), a Word, Excel or PowerPoint file, or a Notion doc into clean text, and ScreenshotOne, Urlbox and the Apify data source cover the rest.
GitHub is the Git provider, connected over OAuth, so code and content land in repositories you already own. Vercel and Kubernetes are the targets a Work can publish to, and Cloudflare DNS writes the records behind a custom domain.
Uploads go to local disk, AWS S3, MinIO, or a GitHub repository with optional Git LFS. Each deployed Work gets a Postgres database of its own, and Knowledge Base embeddings live in pgvector or Qdrant.
Five email providers — Postmark, Resend, Mailgun, SendGrid and Mailchimp Transactional — carry your agents’ mail. Five notification channels deliver events to Slack, Discord, Telegram, WhatsApp or Novu, and eleven connectors stream activity in from Slack, Discord, Linear, Notion, Jira, Zoom, Google Workspace, HubSpot, Pipedrive, Bluesky and Mastodon.
Stripe, Google Analytics, PostHog and a custom HTTP collector read the real numbers your Goals are measured against. Background work runs on BullMQ, pg-boss, Temporal, Trigger.dev, Inngest, or the execution nodes in your own fleet.
Seven secret stores — HashiCorp Vault, Kubernetes, AWS Secrets Manager, GCP Secret Manager, Azure Key Vault, Doppler and Infisical — resolve a reference at run time instead of keeping the credential in the platform database. Ten utilities cover agent memory, browser automation, comparison generation, the skills provider, the task tracker, Langfuse prompt management, local and sandboxed task workspaces, and the terminal host behind live agent terminals.
It all happens on the Plugins page in the dashboard sidebar. There is no install step to hunt for — enabling is the whole lifecycle.
The search box matches a plugin’s name, description, category and capabilities. Category chips and an “Enabled only” toggle narrow the grid when you already know roughly what you want.
Press Enable on the card, then confirm in the dialog. Leave “Also enable for all works” ticked and every Work you own can use it; untick it and the plugin stays account-level until you switch it on inside a Work.
Open Settings on the card and fill in the plugin’s form. GitHub and Vercel connect over OAuth instead, and Codex signs in with a device code. Enable before you save — Save is blocked while a plugin is off, and stored keys come back masked rather than in full.
A Work’s Plugins tab carries a Capability Providers panel. Pick which enabled plugin serves each capability for that Work, and override the plugin’s settings for that Work alone.
Nothing about which provider does what is hardcoded. A capability call resolves its plugin at the moment it runs: an Agent’s pinned provider first, then an explicit override, then the Work’s Capability Providers choice, then whichever enabled plugin declares itself the default for that capability. Change the answer and the next run uses it — no redeploy, no edit to the Work itself.
27 plugins are core: bundled in every image, including the default pipeline, local storage, all six job runtimes and all seven secret stores — so a fresh install works with no registry to reach. The other 75 ship in the image today as well, and are published as @ever-works/<id>-plugin packages that an install running in dynamic mode fetches on demand, behind an allowlist platform admins control. That dynamic path is still rolling out: the packages are published restricted for now, and bundled mode stays the default.
Drive the platform from Slack, get pull requests reviewed against your knowledge base, and turn meetings into memory.
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 →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 →Manage Works from any MCP-compatible assistant — 127 API tools plus Knowledge Base tools, authenticated with an API key, over stdio or HTTP.
Learn more →Named runtime sandboxes you assign per Agent, credentials resolved from your own secret store, and a registry of the external MCP servers and repositories your agents may reach.
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.