Keep every client website accountable.
Organize website ownership, environment access, domains, releases, and migration decisions across a client portfolio.
The operational problem
A growing website portfolio creates repeated work: finding the right credentials, identifying what changed, and knowing which customer owns each domain. The workflow should keep those relationships visible.
The recurring problem
Client credentials, domain renewals, and website changes are tracked in separate places.
The first useful change
Inventory each client, isolate access, and move one staging website before scheduling the wider portfolio.
Start with one representative application
Select an application with known ownership and a recovery path. Inventory its runtime, database, file writes, domains, queue workers, and scheduled jobs. A staging rehearsal reveals missing requirements before the migration affects customers.
Keep client access separate from platform operations
The client should see the websites and domains they are authorized to manage. Agency staff need a documented approval path for production changes. Registrar and node credentials remain outside the customer panel.
Define completion before moving traffic
Agree on the pages and business workflows that must work, the evidence to collect, and the condition that triggers rollback. Track the deployment result and persistent data recovery separately. Production availability must be confirmed before a migration is scheduled.
| Recurring problem | Orisite workflow |
|---|---|
| Unclear ownership | Workspace, website, environment, and domain relationships |
| Manual server changes | A fixed source revision and versioned release configuration |
| Unknown recovery point | An artifact reference and a separate data recovery plan |
Bring your PHP application, choose the runtime it needs, and keep releases, domains, and operations together in your Orisite panel.
