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 · Blog builders
Autonomous AI SEO & auto-blogging agent
SEObot fills a blog you already own — keywords, articles, internal links and publishing into ten CMS destinations, on autopilot. Ever Works builds the blog and its code in Git you own and keeps it running on a schedule, while a dedicated post writer is not built yet.
SEObot and Ever Works overlap on exactly one thing — getting a blog that produces its own posts — and they approach it from opposite ends. SEObot is a hosted SEO agent for a site you already run: connect a CMS and it picks keywords, plans topics, writes articles of up to 4,000 words with tables, images and source citations, interlinks them, publishes on a cadence and re-links the whole library monthly, on autopilot by default with an optional approve-or-decline email. It builds no site, generates no code and creates no repository. Ever Works builds the blog and its code — a Next.js site generated into Git repositories you own, deployed on your domain, re-run on a schedule and staffed by named Agents — but its blog kind is early: there is no dedicated post generator yet, so a Blog Work’s Posts tab runs on the shared items pipeline and long-form writing is delegated to Agent tasks until a post writer is built. If your site exists and you need it filled, SEObot is usable today and Ever Works is not the tool for that job. If you need the site itself, the code, the ownership and an autonomous team around it, that is what Ever Works ships.
SEObot assumes the site exists; its whole product is the content that goes into it. Ever Works starts from the other end. Give it a topic and it researches the domain with the search and extraction plugins you enable, generates the site from a template into repositories you own (a Blog Work defaults to the general-purpose Next.js web template, with a static Astro variant opt-in), deploys it to Vercel, Kubernetes or managed hosting, and puts it on your own domain. The honest caveat sits on the writing side: the blog kind is wired end to end — the chip, the persisted kind, the per-kind configuration with a posting cadence and topic prompt, the schedule — but the generation pipeline behind it is the same items pipeline every Work gets. There is no dedicated blog-post generator yet, so long-form pieces are commissioned as Tasks for a Work-scoped Agent; a post writer is still to come. SEObot writes the posts and cannot build the blog; Ever Works builds the blog and does not write the posts for you yet.
Both products keep working after launch, which is rarer than it sounds. SEObot publishes on a cadence and re-links the library every month; Ever Works re-runs its generation pipeline on seven cadences from hourly to monthly, retries a failed run after fifteen minutes, pauses a schedule after repeated failures and recovers stuck runs on its own. The difference is what surrounds the autonomy. SEObot’s control is an approve-or-decline email. In Ever Works, every Agent-executed Task can get its own branch and private checkout, quality gates run real build, test, lint and type-check commands and send red work back to the Agent instead of to you, and a configurable merge policy decides whether an Agent may land its own pull request — so unattended changes to a live site are reviewable by default and self-merging is something you opt into. What Ever Works does not do yet is revisit the prose of an already-published post, insert links across the corpus, or pick keywords: a prebuilt SEO Auditor agent can review a Work and produce a prioritized fix list, but the repair half is on the roadmap.
SEObot is proprietary cloud software with no self-hosting; the only open component is the MIT client library, which reads articles from its API and runs none of the generation. Its articles land in your CMS, which is where they stay if you leave — the pipeline, the keyword plan and the link graph stay with the vendor. Ever Works creates three repositories in your own Git account for every Work — data, markdown and website — so the content, the generated code and even the Knowledge Base your Agents read are version-controlled by you. The runtime itself is open source under AGPLv3 with no paid feature tier, runs on Docker or Kubernetes, ships 100+ plugins, and uses the AI provider you choose — including local Ollama or vLLM — with spend caps enforced before every call at the Work, Mission, Idea, Agent and account level. That also changes the cost shape: SEObot meters per article, so five blogs are five article budgets; Ever Works is a platform with budgets you set. One row Ever Works cannot claim on this page: the sitemap, structured data, feeds and hreflang scaffolding its documentation describes in detail ship on the directory template, and are not documented for the web template a Blog Work uses.
SEObot’s scope is content, and it is deliberately narrow: it cannot touch your site’s code, design, taxonomy or deployment. Ever Works organizes around a goal. A Mission proposes Ideas, accepted Ideas become Works, and named Agents with a scope, a budget and a heartbeat keep each one moving — a blog next to a directory, a marketing site or a landing page, with stores and whole companies planned. Every Work carries a typed, Git-backed Knowledge Base — brand, style, personas, glossary, legal copy, SEO constraints — injected into every run, so editorial voice accumulates instead of resetting per article. That is the structural answer to the question every auto-blogging buyer asks about consistency; SEObot’s own guidance is that article quality varies by audience and subject matter, and third-party reviewers add that output benefits from occasional moderation.
Ever Works vs SEObot, head to head.
| Feature | Ever Works | SEObot |
|---|---|---|
| Prompt → working app/site | ✓ | Fills a site you already have |
| Researches the topic for you | Web research; item-shaped today | Keyword + SERP research |
| Writes the content (copy, posts, SEO) | Items pipeline today; no post writer yet | Articles up to 4,000 words |
| Generated code from a template base | ✓ | – |
| Ongoing autonomous maintenance | Scheduled | Autopilot + monthly re-linking |
| Content version-controlled in Git | ✓ | Lives in your CMS |
| Code in your Git | ✓ | – |
| Open source | ✓ | Client SDK only (MIT) |
| Self-hostable runtime | ✓ | – |
| No vendor lock-in | ✓ | Articles stay in your CMS |
| Publishes into a CMS you already run | – | Ten CMS destinations + API |
| Keyword research & content calendar | – | ✓ |
| Automatic internal linking across posts | – | ✓ |
| SEO scaffolding in the generated site | Directory template: full; blog template: not documented | Inherits your CMS |
Choose SEObot when you already have a site on WordPress, Webflow, Framer, Squarespace, Shopify, Wix, Ghost, Notion, HubSpot or Unicorn Platform — or a Next.js app you can wire its client into — and what you need is a steady stream of keyword-targeted, long-form articles landing in it without anyone on your team writing, linking or scheduling. It is the better pick if you will not migrate your site, if you want programmatic SEO pages, video-to-article or news roundups from the same subscription, if per-article pricing that scales with volume suits your budget better than a platform, and if you are comfortable with hosted, closed software and a light moderation pass on the output.
Visit SEObot ↗Give Ever Works a topic and its agents research it, generate the site and its content, deploy it, and keep re-running on the cadence you set — all version-controlled in your own Git. A dedicated long-form post writer is rolling out.