TECHPERFORMANCE
Solution · WordPress editorial multisite

More titles, one technical team.
Continuous deploy, archive preserved, SEO intact.

Multi-title editorial networks operated with an opinionated stack and a single operating model, from single site to multi-million network.

Talk to an architect See the stack
The problem

Running a multi-title network is a different problem from running a site.

01
// anti-pattern · editorial multisite

Managed hosting that crumbles on the first viral article.

It works fine while everything is fine. Then a story breaks, the edge cache expires, and only the backend is left to hold. That is when you see if your hosting was really "managed".

02
// anti-pattern · editorial multisite

Deploys that block the newsroom.

Maintenance windows, editorial freezes, "we go offline for three minutes". For a newsroom publishing dozens of pieces a day, that is time you don’t get back.

03
// anti-pattern · editorial multisite

Causes of slowdowns discovered after the fact.

Slowdowns during peaks get diagnosed the day after, reading logs piecemeal. Without per-title observability, optimizing turns into guessing.

How we run it

One newsroom, one network, one operations team.

Same operating model from a single site to a 40+ title network. Per-title isolation, continuous deploy, dedicated observability. The newsroom publishes as always, we do the rest.

  • →Same team from single site to HA cluster.
  • →Response within 1h with an SRE, not a dispatcher.
  • →Entirely EU infrastructure.
stack · editorial multisite
network-grade
  • Per-title isolation
    each site in a dedicated container, guaranteed resources, no "noisy neighbor"
  • Reverse proxy with per-domain routing
    automatic TLS, HTTPS redirect, per-title rules
  • WordPress hardened + replicated database + object cache
    stack chosen for editorial workload, audited plugins, heavy hypertexts handled
  • Self-hosted CI/CD pipeline
    controlled deploys, real staging, tested rollback — multi-title in parallel
  • Perimeter protection + anti-scraping scenarios
    WAF + Crowdsec + iptables, rules shared on the network but per-title customizable
  • Per-title observability
    Grafana + Prometheus + Loki + Uptime Kuma, separate dashboards, targeted alerts
Expected results

Numbers sustained across the network, not just on a single title.

The metric that matters on an editorial network is not a single-day record, it is regularity over 12 months. Below the lines we sign at contract.

99.9%+

monthly uptime sustained on the portfolio, even on aggregated editorial peak days

continuous deploy

multiple windows per day per title, with no service interruption

0 noisy neighbor

a title in crisis does not drag the others down, ever. Isolation by design.

In production

Two editorial networks, two needs, same operating model.

Caffeina Media + NEM is the Italian-international multi-title network (40+ titles, 20M+ visits/month). Hall of Series is an editorial title publishing dozens of articles a day that cannot stop for a deploy.

See all case studies
Caffeina Media + NEM Network · 40+
20M+
monthly visits

“An international network with Italian magazines and foreign-language editions, all on the same operating model. No different providers, one team that owns the whole stack.”

Technical Direction
Caffeina Media + NEM
Hall of Series Editorial · 3y
0 downtime
daily deploys

“We publish dozens of articles a day, we can’t stop for a deploy. Tech Performance made this possible.”

Tech Lead
Hall of Series
FAQ

Questions from people who run more than one title.

If yours is different, write to us: we reply within the day.

How many titles can I put on the same plan?
Depends on aggregate traffic and per-title criticality. On a Network plan we typically operate networks from 10 to 40+ titles on the same operating stack, with different isolation tiers. Above certain thresholds or for single mission-critical titles you move to HA Cluster.
Can I keep using my existing plugins?
Yes. We audit plugins during onboarding: we only block the truly problematic ones (known vulnerabilities, abandoned plugins, pathological behaviour at scale). For the rest, the stack is standard WordPress, no proprietary fork.
What happens during the migration of an existing network?
Coordinated migration: data replication, parallel testing, preservation of archive and SEO ranking, cutover in agreed window. Single site 5-7 days, multi-title network 2-3 weeks, HA cluster up to 30 days. No CMS rewrite, no lock-in.
How do you handle peaks on a single title that explodes?
Capacity preallocated on the network plus burst on available nodes. If a title peaks, you see the pattern on the dedicated dashboard and the SRE already on monitor can scale resources or cut scraping scenarios before the problem spreads.
Free audit

Let’s talk about your stack,
free, no strings attached.

30 minutes with a Romiltec architect. Together we figure out whether Tech Performance is a fit, and if it isn’t, we tell you straight away. No cold pitch, no black-box quote.

Book a call cal.com/romiltec/tech-performance · 30 min call