Ecommerce agency hosting where staging is not a data breach.
Cloning a client's store to staging copies every order, every address and every email on it. Most agencies do this weekly without thinking about it.
A store clone is a data copy.
Everything that makes agency work on ordinary sites routine becomes a liability once the database holds customers.
Personal data left behind on clone
Staging copies of a store contain real names, addresses and order history. Customer data is scrubbed as part of cloning rather than left for somebody to remember.
Test gateways that stay test
A staging store with live payment keys can take a real payment from a test order. Gateway configuration is kept separate between environments so that cannot happen by accident.
Freeze windows that hold
Nobody deploys to a store in late November. Change windows are agreed per client, so the freeze is enforced rather than remembered.
Peak capacity per client, not shared
Your clients' busy periods overlap. Capacity is allocated per store so one client's sale is not another client's outage.
Restore a store, not the account
Backups and restores are per site, so recovering one client's mistake never involves touching anybody else's.
You hold their customer list.
An agency running client stores is a processor of everybody else's personal data. That is a different position from building brochure sites, and it changes what staging has to do.
- Customer data removed during environment cloning
- Payment keys isolated per environment
- Deployment freezes enforced per client
- Per-store capacity and per-store restores
Everyone's busy week is the same week.
Agency risk concentrates because client peaks coincide. The measure is whether twenty stores can all have their best day at once.
What we change for ecommerce agencies
The difference from ordinary agency work is that every database you touch belongs to somebody's customers.
| Setting | What we do | Why |
|---|---|---|
| Environment cloning | Customer and order data scrubbed as part of the copy | A staging clone of a store contains real names, addresses and purchase history, and agencies create those weekly without treating them as copies of personal data. |
| Payment configuration | Kept separate per environment with live keys excluded | A staging store carrying production gateway credentials can take a genuine payment from a test order, which is discovered by the customer rather than by you. |
| Deployment freezes | Enforced per client rather than agreed verbally | Nobody intends to deploy during Black Friday, but a freeze that lives in a calendar invite is not a control. |
| Capacity allocation | Per store rather than pooled across clients | Retail peaks coincide, so pooled capacity means every client's best day is also every client's riskiest one. |
| Restore granularity | Per site, never account-wide | Recovering one client's mistake must not put another client's store into a rollback they never asked for. |
Simple, transparent pricing.
Every plan includes free migration, daily backups, SSL and 24/7 support.
- 1 WordPress site
- 10 GB NVMe disk
- Free SSL
- Daily backups
- One-click deployment
- Support tickets
- 5 WordPress sites
- 50 GB NVMe disk
- Free SSL
- Daily backups
- One-click deployment
- Priority support tickets
- 20 WordPress sites
- 200 GB NVMe disk
- Free SSL
- Daily backups
- One-click deployment
- Dedicated support
Questions, answered.
Is it safe to clone a client store to staging?
Can a staging store take a real payment?
How do we stop deploys during Black Friday?
Will one client's sale affect another's store?
Handle client stores properly.
Move the client stores across - migration is free, every store included.