SP

SysPanel

Control plane MVP

Live control planeEnv: productionUptime: 31m

Operator console

One screen for tenants, nodes, and live cPanel restore work.

This dashboard now reads directly from the SysPanel control plane on the VPS. What you see here is the current tenant inventory, node health, restore queue, and asset surface being served from the live `/v1` API.

Inspect restore jobsCheck health endpoint

Current state

Ready For Execution

Demo restore ready for execution.

Agent ping2007s

Average heartbeat across connected nodes.

Preview drift2 warnings

2 unsupported items in the selected restore preview.

Managed tenants

2

2 plans, 1 active restore job

Servers online

2

2/2 agents connected, 2007s avg heartbeat

Restore queue

2

0 analyzing jobs, 0 executing, 1 ready

Open alerts

1

1 partial-success restore and 0 disconnected agents

Operator actions

Provision tenants and hosted resources from the live panel.

These forms post straight to the running control plane. When a request succeeds, the page refreshes against the live `/v1` API so the new state appears immediately.

Tenants

Create tenant

POST /v1/tenants

Sites

Create site

POST /v1/sites

Databases

Create database

POST /v1/databases

Mailboxes

Create mailbox

POST /v1/mailboxes

Restore controls

Create a restore job and drive it through preview, execution, and cancellation.

The restore request uses the live source sites already tracked by the control plane. Defaults follow the spec: rename collisions, mail off, DNS off, and `php81-compat` as the runtime fallback.

Restores

Create restore job

POST /v1/restores
Requested features

Operator notes

Live workflow
  • Use `Analyze` first when you want to inspect warnings, renames, and unsupported items before execution.
  • `Execute` can also resume a created job because the backend will analyze it automatically if needed.
  • `Cancel` leaves completed and partial-success jobs untouched and only stops in-flight work.

Tenants and plans

Capacity by customer and service tier.

Plan enforcement and asset usage now come straight from the live control plane instead of mock samples.

Acme Hosting

Starter plan · 1 / 2 sites

Ready For Execution
1 server1 DBs · 1 mailboxes · 1 restores

Blue Orchard

Growth plan · 1 / 10 sites

Active
1 server1 DBs · 1 mailboxes · 1 restores

Growth

10 sites

20 DBs · 40 mailboxes · sites, databases, mailboxes, ssl, cron, dns

Starter

2 sites

4 DBs · 6 mailboxes · sites, databases, mailboxes, ssl, cron

Servers and runtime profiles

Keep the Linux edge simple and visible.

Agent status, heartbeat age, region, and server capacity are all coming from the running control plane.

control-node-01

eu-north · control-01.local

34m ago
Agent 0.1.0ConnectedActive
Sites1/50
Databases1/100

Mailboxes 1/200

restore-node-01

eu-west · restore-01.local

33m ago
Agent 0.1.0ConnectedActive
Sites1/50
Databases1/100

Mailboxes 1/200

PHP 7.4

Legacy

PHP 7.4 · Legacy compatibility profile

PHP 8.0

Preferred

PHP 8.0 · Default runtime for older sites

PHP 8.1 Compatibility

Fallback

PHP 8.1 · Fallback profile used during restore

Restore wizard

Compose a safe restore before anything touches a server.

The selected restore below is live data. Preview details, warnings, and unsupported items reflect the current control-plane state.

1

Source archive

acme.example.com selected for restore

2

Target tenant

Acme Hosting, restore to control-node-01

3

Collision policy

rename, DNS off, mail off, php81-compat fallback

4

Preview

5 actions, 2 warnings, 2 unsupported

5

Execute

Current step: Ready For Execution

Domains1
Databases1
Mailboxes1
Unsupported2

Restore jobs

Watch jobs progress, checkpoint, and validate.

These cards come from the live restore queue on the control plane, including progress and validation outcomes.

restore_1

Ready For Execution · Ready For Execution

Ready For Execution

Demo restore ready for execution.

restore_2

Partial Success · Validation

Partial Success

Web and database restore succeeded, but validation reported a mismatch.

Restore events

restore_1
  • 22:09:56 · analysis.started · Restore analysis started.
  • 22:11:56 · analysis.completed · Restore preview is ready.

Sites, databases, and mailboxes

The customer surface remains visible underneath the platform.

The asset inventory below is being read from the live `/v1/sites`, `/v1/databases`, and `/v1/mailboxes` endpoints.

Sites

acme.example.com

Acme Hosting

Active
orchard.example.net

Blue Orchard

Active

Databases

acme_wp

acme.example.com

mysql
orchard_app

orchard.example.net

mysql

Mailboxes

admin@acme.example.com

acme.example.com

Active
hello@orchard.example.net

orchard.example.net

Active

Live API source: http://127.0.0.1:8080 · Refreshed 23:11:37