Know what changed. Know what is running.
Bring application ownership, release history, resource policy, and domain state into a single operational workflow.
One operational record for every website
The panel connects a website to its workspace, environment, release, runtime, and domains. Operators can distinguish a requested change from a runtime observation before deciding what to do next.
A release does not become ready
The new runtime fails readiness or has no current observation.
Investigation
- Confirm the intended artifact, PHP engine, and document root.
- Check startup errors, required extensions, mount permissions, and secret resolution.
- Keep the existing release serving until the replacement is verified.
DecisionRecord the failure and prepare a corrected release. Missing evidence must remain visible.
An application reaches its capacity limit
Errors, latency, or resource observations indicate pressure.
Investigation
- Compare CPU, memory, process, and storage use with the assigned policy.
- Inspect queue backlog, external service latency, and application logs.
- Measure a staging change before increasing capacity or changing worker settings.
DecisionDistinguish a capacity problem from a slow query, a provider failure, or an application defect.
A domain is not serving securely
Ownership, DNS routing, or TLS does not match the intended configuration.
Investigation
- Verify the domain owner and the current authoritative nameservers.
- Inspect the application target and DNS records without assuming propagation.
- Check certificate issuance and renewal state independently of deployment health.
DecisionRestore the correct route only after ownership and TLS checks pass.
Restore the previous application release
A verified release introduces a regression after traffic has switched.
Investigation
- Identify the last suitable artifact and its runtime configuration.
- Confirm database schema and persistent data remain compatible.
- Record the approval, execute the recovery procedure, and check the resulting endpoint.
DecisionA successful application rollback needs fresh runtime evidence and a separate data recovery decision.
| Record | What it answers |
|---|---|
| Website and environment | Who owns this application and where should it run? |
| Release and artifact digest | Which code and runtime configuration are being deployed? |
| Health and observation | Has the node actually reported the expected result? |
| Audit and rollback reference | Who changed it, and which known release can be restored? |
Bring your PHP application, choose the runtime it needs, and keep releases, domains, and operations together in your Orisite panel.
