People ask what Mercury Local is, and I give them the short version: it’s the company behind The Charlotte Mercury, The Farmington Mercury, and Strolling Ballantyne. That’s true. It’s also incomplete.

Mercury Local is a publishing platform — a single shared infrastructure that powers every publication we operate. One codebase. One database. One deployment pipeline. The Charlotte Mercury and The Farmington Mercury don’t run on separate systems that happen to share a name. They run on the same system, rendered differently based on which domain you’re visiting.

The Old Model Was Expensive by Design

A custom WordPress news site costs $10,000 to $25,000 to build and another $2,000 to $5,000 a year to maintain. That’s per publication. If you’re running three publications in three different markets, you’re paying that bill three times — three separate hosting environments, three separate design systems, three separate sets of plugins and security patches. Every new publication doubles the overhead before you write a single story.

That model made sense when publications were standalone businesses with standalone revenue. But most local publications aren’t standalone businesses anymore. They’re coverage gaps that need filling, and the economics of filling them don’t support redundant infrastructure.

Mercury Local was designed to eliminate that redundancy. Every publication on the platform shares the same architecture. When I improve the article template, every publication gets the improvement. When I add a feature to the hub page system, it’s available everywhere. The investment compounds instead of fragmenting.

Same Foundation, Different Newsrooms

Each publication on the platform has its own domain, its own visual identity, its own editorial voice, and its own audience. They draw from a shared foundation — but they look and read like independent publications, because they are.

The system knows that The Charlotte Mercury covers Charlotte city government and The Farmington Mercury covers a Connecticut town council, and it renders the right content on the right domain without anyone managing two separate websites.

Hub pages — our beat-level landing pages — are a good example. A hub page on cltmercury.com pulls Charlotte sports articles. The same hub page architecture on strollingballantyne.com pulls Ballantyne neighborhood coverage. Same code. Different data. Different audience. Zero duplication.

One person maintains all of it. When I fix a rendering issue at midnight, every publication is better by morning. When I ship a performance improvement, nearly 900 published articles across three publications load faster — from one commit. That’s not a staffing limitation. That’s a design decision.

The Scaling Argument

Here is the part I think about most.

If launching a new publication requires building a new website, hiring a new developer, and standing up new infrastructure, the math limits you to the publications you can individually afford to run. That’s a small number for most operators — and it’s why the local news crisis keeps getting worse despite no shortage of people who want to solve it.

If launching a new publication requires configuring a domain and populating a database, the math changes. The marginal cost of the next publication is a fraction of what the first one cost. The editorial investment stays real — you still need reporting, voice, and local knowledge. But the infrastructure cost approaches zero.

The Charlotte Mercury was the proof of concept. The Farmington Mercury proved the model worked in a different market. Strolling Ballantyne proved it worked at the neighborhood level. Three publications, three different geographic scopes — a metro daily, a small-town weekly, and a single-neighborhood outlet — all running on the same infrastructure I maintain once.

What This Has to Do with Local News

There are 213 counties in America with no local news outlet at all. Another 1,500 have only one source left. The problem in those places is not a lack of people willing to do the work. It’s that the infrastructure cost of starting a publication is still calibrated to a business model that died fifteen years ago.

Mercury Local is my answer to that. Not a grant. Not a nonprofit. Not a chain buying up distressed assets. A platform that makes the infrastructure cost low enough that the journalism becomes the only hard part — which is how it should be.

Every city that lost its paper needs what Charlotte has now. They don’t need someone to hand them a check. They need someone to hand them an architecture.