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
Subscription publishing platform + creator network
Substack is the hosted publication, email list, payments and discovery network in one — you write, it distributes, and it takes 10% when you earn. Ever Works generates the blog from a template into Git repositories you own and keeps agents working on it on a schedule — an open-source runtime rather than a rented network.
Substack is the default answer to “I want to publish and get paid for it”: a hosted publication that is a blog and an email newsletter at once, Stripe-backed paid tiers with a paywall you can place anywhere in a post, and — the part no self-hosted site gets for free — a discovery network of recommendations, Notes, leaderboards and apps that Substack says now supplies more than 30% of its paid subscriptions. It costs nothing until you earn, then takes 10% of subscription revenue (roughly 13–16% all-in once Stripe’s fees are counted), and it has spent 2025 and 2026 building media rather than site tooling: podcast hosting, native video, browser livestreaming, a Recording Studio and a TV app. What it deliberately does not give you is the site itself — no code, no repository, no theme source, no write API, no self-hosting, and a design that stays inside its theme editor. Ever Works is the inverse shape: an open-source (AGPLv3) runtime that generates a Next.js blog from a template into Git repositories you own, re-runs its research pipeline on a schedule under budgets, quality gates and a merge policy, and gives named Agents a per-Work Knowledge Base to write from — with the honest caveat that the Blog kind is early, so today’s recurring run is the directory-shaped items pipeline and a specific post you want written is an Agent task rather than a cadence. Substack wins on audience, monetization, media, the writing surface itself — Ever Works has no in-app post editor or preview — and time-to-first-post; Ever Works wins on who owns the site, the repo and the automation that keeps running between your sessions — and it hands you no readers.
Substack’s ownership promise is real and narrower than it sounds: your intellectual property, your subscriber list and your Stripe relationship are yours, and both the list and the posts export at any time. The site is not yours — there is no code, no theme source, no repository, no build step and no write API; the public Developer API returns profile and publication metadata only, and design customization stops at the theme editor’s layouts, colors and fonts. Ever Works generates the blog from a template you can fork — the Next.js `web` template (App Router, React 19, Tailwind CSS v4) with a Markdown blog and marketing pages, or the static Astro `web-minimal` variant — into Git repositories in your own account, so posts are Markdown and YAML in the data repository, the site code is a repository you can change, and every agent edit is a commit or a pull request you can diff, review and revert. The runtime itself is AGPLv3 with no feature held behind a paid tier, self-hosts on Docker Compose or Kubernetes, runs on the AI provider you choose from 11 provider plugins — including local models through Ollama, LM Studio and vLLM — and is addressable through a REST API with long-lived keys, an MCP server and a CLI. A domain you own attaches at no platform fee; Substack unlocks one for a one-time $50 per publication.
Substack automates delivery: a post you finished goes out on the web and by email at the time you chose, welcome and drip sequences fire on subscriber events, and headline A/B testing is built in. Nothing works on the publication between your sessions. Ever Works is built around the opposite default. Scheduled Updates re-run a Work’s generation pipeline on seven cadences from hourly to monthly, retry after 15 minutes and pause themselves after repeated failures; named Agents wake on their own cron heartbeat, decide the next useful action and take it, under a per-Agent spend cap enforced before every AI call and permission flags that default to off; and quality gates plus a merge policy decide whether their output lands on its own or waits for you in the Pull requests tab. The website layer has its own loop, opt-in per Work: if you switch on automatic template updates — which needs a connected Git provider — an hourly pass checks the website repository against its upstream template and applies what has moved, leaving the last check, the last update and any error on the Work’s Deploy tab. The honest caveat: on a Blog Work that recurring run is today’s items pipeline — the one built for directories — so it refreshes the Work’s generated content rather than commissioning a post per interval, and a specific post you want written well is a Task you hand to the Work’s Agent, not a cadence you set. The blog’s `generation.cadence`, `topics_prompt` and `posts_per_run` settings are stored and validated but not yet consumed, while dedicated post writers roll out.
Substack has chosen not to generate text: its AI features are production aids — transcription, text-to-speech narration, clip selection, in-editor image generation — and since July 2026 it ships an authorship detector and a disclosure statement rather than a writer, which makes human authorship a trust signal on the platform. That is a coherent position, and this page does not answer it with a “writes the posts for you” row. What Ever Works ships is a research pipeline that discovers, extracts, validates and writes sourced entries, categories, tags, collections and comparison pages for directory-shaped Works, plus a per-Work Knowledge Base whose typed documents — brand, style, personas, glossary, SEO, legal — are injected into every run so agents write in your voice rather than from a blank prompt. For a Blog Work the same pipeline feeds the Posts tab, marketing copy is edited in the repository or delegated to an Agent task, and a dedicated long-form post writer is the next thing the kind gets. If you want the runtime to research and write today, a Directory or Awesome Repo Work is the mature path; a Blog Work gets the template, the deploys, the schedule, the Agents and the Git ownership now.
Substack’s structural advantage is the network: recommendations, Notes, leaderboards, a referral program and apps that supply a real share of paid conversions — at the price of a shared look you can adjust but not redesign, a thin SEO surface with no structured-data authoring and no control over URL structure, reach that shifts when the feed algorithm does, and a revenue share that grows with you for as long as you publish (at $10,000 a month of subscriptions, about $1,000 a month). Ever Works has no discovery network; every Work starts from zero traffic and earns it through the site. What it has instead is the model around the blog: a Mission keeps proposing Ideas, accepted Ideas become Works from prebuilt templates, Agents with budgets, heartbeats and permission flags keep each Work moving, and Work Members collaborate as Manager, Editor or Viewer — so one topic can grow into a blog, a directory, a marketing site and comparison pages that link to each other, with stores and whole companies on the roadmap. Where the two overlap on the site itself, be precise about the template: the generated directory site carries newsletter capture through Resend or Novu with admin statistics, comments with ratings, checkout across Stripe, Lemon Squeezy, Polar and Solidgate, JSON-LD, three feed formats and llms.txt; a Blog Work’s `web` template ships a Markdown blog and marketing pages; and neither has a post paywall or a campaign sender yet.
Ever Works vs Substack, head to head.
| Feature | Ever Works | Substack |
|---|---|---|
| Prompt → working app/site | ✓ | Hosted publication, no code |
| Researches the topic for you | Directory-style research today | – |
| Writes the content (copy, posts, SEO) | Directory data today; posts rolling out | You write; production aids only |
| Generated code from a template base | ✓ | – |
| Ongoing autonomous maintenance | Scheduled | Scheduled sends only |
| Content version-controlled in Git | ✓ | Export (CSV + HTML) |
| Code in your Git | ✓ | – |
| Open source | ✓ | – |
| Self-hostable runtime | ✓ | – |
| In-app post editor with preview | – | Rich-text editor, drafts, scheduling |
| Paid tiers & post paywall | No (checkout ships in the directory template) | ✓ |
| Email newsletter sending | No sending (capture ships in the directory template) | Post-as-email, drip, ad-hoc sends |
| Built-in discovery network | – | 30%+ of paid subs in-network |
| Programmable (API, MCP, CLI) | ✓ | Read-only metadata API |
Choose Substack when the job is a paid newsletter with an audience still to find: you will write every post yourself, you want payments, a paywall, email delivery, podcast and video hosting and a mobile app working the day you sign up with no infrastructure and no bill until you earn, you value a network that can send you paying readers more than you value owning the site’s code, and a 10% share of subscription revenue plus a one-time $50 for your own domain is a fair trade for never touching a repository, a deploy or an AI provider.
Visit Substack ↗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.