All stories
AgenciesFaable Deploy

Thirty client sites, one project each, and a firewall in front of all of them

An agency moved its clients off shared hosting: some sites rebuilt in Next.js, the rest kept on WordPress, installed from Faable's catalogue. One firewall stops the bots before they reach any of them, and each client pays its own plan.

Allplans include the firewall, Free too

Illustrative scenario based on patterns we see across teams building on Faable.

A hand-drawn website wireframe in a notebook next to an orange pen
Photo: Compagnons on Unsplash

The team

A web agency of eight people with around thirty clients: shops, law firms, a training academy. Their sites used to run WordPress on shared hosting. The agency rebuilds some in Next.js; the ones whose editors live in wp-admin stay on WordPress.

The challenge

Bots probe /wp-login.php, /xmlrpc.php, .env and .git on every site, WordPress or not, and every probe wakes the app and fills the logs. The WordPress sites need their files and database kept safe, and editors who sign in without shared passwords. One client's contact form gets bursts of spam. And the agency needed each client kept apart, with its own project, domain and invoice, while still being able to work on all of them.

How they built it

  1. 1

    One project per client

    The agency is a member, the client is the owner and pays for its own plan. Billing is handed over from the member list, and if a client moves on, ownership is transferred in one step.

  2. 2

    A domain per site

    Each site gets its custom domain with free SSL. Clients on Cloudflare set the record to DNS only.

  3. 3

    WordPress from the catalogue

    The sites that stay on WordPress are installed from Faable's catalogue: their files on a volume and a managed database, both backed up every night, and editors who sign in through Faable Auth. On Hobby, a site is the plan plus 10 € a month for its database.

  4. 4

    A firewall on every plan

    Faable blocks scanners for .env files, Git metadata and admin panels at the edge. On the Next.js sites it also blocks any .php and /wp-* request; on the WordPress ones, XML-RPC, wp-config backups and user enumeration, before they reach the site.

  5. 5

    Rules tried before they block

    A monitor rule shows what it would have stopped over the last 30 days. Then a limit rule slows the spam on the contact form, and a sink rule answers an uptime pinger with a 404 without waking the app.

  6. 6

    See what was stopped

    The Firewall tab shows the blocked requests over 24 hours, 7 days or 30 days, by path and by the rule that stopped them. Top client IPs suggests the rule to add.

The result

Bots that never reach the client sites, spam slowed at the edge and quieter logs. The WordPress sites keep their data backed up and their editors sign in through Faable. Each client keeps its own project and invoice, with the agency working across all of them.

Ship your first deploy

Connect your repo, push, and watch it go live — with Zero Ops, your data hosted in the EU and real human support behind you. Free to start, no credit card required.