Thinking...

    Skip to content

    News Apparatus vs. WordPress for publishers

    WordPress is a capable content management system, and plenty of publishers run on it well. The difference is what sits around the content. A working publication needs source monitoring, an editorial queue, a newsletter, push notifications, reader accounts, advertising, and increasingly education — and on a self-assembled stack each of those is a separate plugin or service with its own data model, its own login, and its own upgrade path. News Apparatus is built as one workspace where those parts already share the same articles, the same audience, and the same permissions.

    Where the two approaches diverge

    On a plugin stack, the article is the only shared object. Your newsletter tool has its own copy of your subscriber list, your membership plugin has its own idea of who a reader is, and your ad setup knows nothing about either. Every workflow that crosses two of those systems becomes a manual export, a webhook someone maintains, or a habit that only works while one person remembers it.

    In News Apparatus those systems are one system. A story moves from ingestion to an editor's queue to publication, and the same story is available to the newsletter, to web push, to a members-only gate, and to the ad placements on the page it renders in — without an integration step in between.

    • Source monitoring and ingestion feed the same editorial queue your writers already work in.
    • AI-assisted drafting produces drafts for a human editor; nothing publishes itself.
    • Newsletters and web push send from the content you already published, to the audience the platform already knows.
    • Reader accounts, memberships, and paid content read from one profile rather than several.
    • Advertising placements, house promotions, and sponsorship live alongside editorial instead of beside it.
    • Education and course delivery are part of the same workspace on the plans that include them.

    What you keep

    Your brand and your domain. Sites run on your own domain with your own logo, colors, and typography, and readers never see platform branding. Your content is your content: it stays exportable, and your archive is not a hostage.

    Your editorial control also stays where it belongs. Automation drafts, tags, and summarizes; editors decide. Nothing reaches a reader without a person approving it.

    What you stop maintaining

    Plugin compatibility, the update window nobody wants to own, the separate hosting decision, the four dashboards, and the integration glue between them. Hosting, updates, and the connections between features are part of the product rather than a project your team runs on the side.

    That trade is the honest one to weigh: a self-assembled stack gives you maximum freedom to pick each part, and costs you the work of holding those parts together. A workspace gives you fewer choices per part, and hands back the time you spent on the seams.

    Who this fits

    Small and mid-sized publications that publish daily or weekly, run a newsletter that matters to them, want reader relationships rather than only pageviews, and would rather spend their attention on reporting than on infrastructure. Specialty and medical publishers in particular tend to need memberships, events, and education next to their editorial — which is exactly where a single workspace saves the most effort.

    Common questions

    Can we move our existing content over?
    Yes. Existing articles, authors, categories, and media can be imported, and your published URLs can be preserved or redirected so search engines and existing links keep working.
    Do we still use our own domain?
    Yes. Your publication runs on your own domain with your own branding. Readers see your brand, not ours.
    Does the AI publish without human review?
    No. AI assists with drafting, summarizing, and tagging. An editor reviews and approves before anything is published.
    Does this replace our advertising setup?
    It can. Direct campaigns, house promotions, and sponsorship placements are managed in the workspace, and programmatic partners can be used alongside them.
    What happens to our archive if we leave?
    Your content remains yours and can be exported. Nothing about the archive is locked to the platform.

    Where to go next

    Compare what each plan includes, read the full list of questions publishers ask us, or walk through the workspace with us.