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.
Compare · Company builders
Slack-native AI teammate with a hosted app builder
Lindy is a closed cloud AI teammate that runs internal operations from Slack — and Lindy Build turns a prompt into an app or site deployed on a lindy.site subdomain. Ever Works researches the topic, writes the content, generates the site, and commits both to Git repositories you own.
Lindy is two products sharing one memory. The one it leads with is a Slack-native teammate — a private Lindy in each person’s DMs and a shared one in channels — that runs internal operations: alerts and digests, notes from calls it joins, mailbox triage, CRM and ticket updates, and standing Routines that fire on a cadence or a trigger. The other is Lindy Build, which takes a prompt and produces a full-stack app, an internal dashboard or a marketing site, tests its own work, and deploys it — so the overlap with Ever Works is real rather than theoretical, and it would be wrong to say they cannot ship a site. The line to draw is not who builds; it is what you hold afterwards. Build output lands on a lindy.site subdomain on Lindy’s infrastructure, and no source export, Git push, custom domain or self-host path for it is documented on the Build page or anywhere in Lindy’s product docs. Ever Works commits the content and the code into Git repositories you own, deploys them to your hosting under your own domain, runs on an AGPLv3 codebase you can host yourself, and re-runs the pipeline on a schedule so the site moves forward without a new prompt. Lindy is genuinely ahead on connector breadth, on live meeting attendance and mailbox triage, and on compliance certifications we have not published.
Both products can hand you a live web property, so the honest question is not who can ship one. Lindy Build deploys what it makes onto a lindy.site subdomain on Lindy’s infrastructure, and no source export, Git push, custom domain or self-host path for that output appears on the Build page or in Lindy’s documentation — the operational outputs live inside the product too, so leaving means leaving the work behind. Ever Works commits both the content and the code to Git repositories you own, deploys them to your hosting or to your own Kubernetes cluster with your own registry, and lets you attach your own domain with DNS records verified and the provider subdomain retired for you. The runtime itself is AGPLv3 with no paid feature tier — nothing is held back behind a commercial edition.
Lindy researches well and writes — reports, digests, decks, drafted replies — but that output is delivered to a person: a Slack message, an email, a dashboard to read. It is not the content of the site Build produced. Ever Works treats publishable content as the product: the pipeline researches the niche, validates each source, then writes items, categories, tags, collections, comparison pages and SEO metadata into the Work’s own data repository. Being straight about where we are — the directory kind is the mature one. There is no dedicated blog-post or landing-copy generator yet, so Blog, Website and Landing Page Works are fed by that same items pipeline today.
Both products run standing work on a schedule, and it would be wrong to imply otherwise: Lindy’s Routines are exactly that — standing work that runs on a cadence or a trigger, for one person or the whole team. The difference is what the schedule changes. A Routine produces another alert, digest or dashboard refresh for someone to read. Ever Works’ Scheduled Updates re-run the generation pipeline on one of seven cadences from hourly to monthly, with retries, failure tracking and auto-pause, and the result lands as commits in your repository — new items, refreshed data, updated pages — so the property moves forward without anyone prompting it.
Lindy gives you one teammate shared across the workspace, billed per seat against a pooled credit balance that refreshes monthly and does not roll over. Ever Works gives you a structure: Missions that keep proposing Ideas, Ideas that become Works, and named, persistent Agents with a scope, a heartbeat, Skills, per-tool grants and Git-versioned instruction files, grouped into Teams with an org chart and scorecards. Around that sits governance built for autonomy — quality gates that send work back instead of to you, configurable merge authority over an agent’s own pull requests, a branch and private checkout per Task, and per-Mission, per-Idea, per-Work, per-Agent and account-wide caps enforced before each AI call rather than counted after it. Store and Company builders are still on the way; today the shipped artifact is the site.
Ever Works vs Lindy, head to head.
| Feature | Ever Works | Lindy |
|---|---|---|
| Prompt → working app/site | ✓ | ✓ |
| Researches the topic for you | ✓ | Research reports |
| Writes the content (copy, posts, SEO) | Directory data today; posts rolling out | Drafts and digests |
| Generated code from a template base | ✓ | Prompt-generated |
| Ongoing autonomous maintenance | Scheduled | Scheduled routines |
| Content version-controlled in Git | ✓ | – |
| Code in your Git | ✓ | – |
| Custom domain on the built site | ✓ | Not documented |
| Open source | ✓ | – |
| Self-hostable runtime | ✓ | – |
| No vendor lock-in | ✓ | Output stays hosted |
| Business-tool connectors | 11 native + MCP | 1,000+ claimed |
| Live meeting attendance | Recordings after the call | ✓ |
| Published compliance certification | – | SOC 2 Type II, HIPAA |
Choose Lindy when the job is internal operations inside a company that already runs on Slack. It reaches further into the working day than Ever Works does: a private teammate in every person’s DMs alongside the shared one in channels, a claimed thousand-plus connectors with external MCP servers behind them, a bot that joins live Zoom, Google Meet and Microsoft Teams calls instead of reading the recording afterwards and files them into a searchable meeting library, triage and drafting inside your own Gmail or Outlook mailbox, a virtual desktop for software with no API, inbound and outbound phone calls, iMessage and SMS, and work asked for conversationally in Slack, email or a text message rather than wired up as a workflow graph — none of which Ever Works matches today. The vendor also reports that on connect it crawls your existing Slack, Notion, Confluence and Google Docs history to bootstrap a knowledge graph, so the first answer is already contextual. Our ingest starts from now: a connector’s first sweep brings in new activity rather than history, and the only documented lever is an opt-in window on that first pull — off by default, ninety days at the most, offered by nine of our eleven connectors and not by Slack — so a workspace that skips it starts cold. On procurement it is further along too — SOC 2 Type II, GDPR, HIPAA with a signed BAA on Enterprise and PIPEDA, against our answer of self-hosting rather than certification. And for a throwaway internal dashboard, Lindy Build is honestly less work: a prompt, and nothing to host. Pricing, verified 2026-09-04, is per seat against a shared workspace credit pool that refreshes monthly and does not roll over — Plus $29.99, Pro $99.99 and Max $199.99 per user per month with 3,000, 15,000 and 35,000 credits respectively, Enterprise on request, a seven-day trial and no permanent free plan.
Visit Lindy ↗Give Ever Works an idea and its agents research the space, write the content, generate the code, deploy it, and keep it improving — all version-controlled in your own Git.