Instances and Resource Delivery
The primary delivery object in PayIncus is an Incus-backed LXC / KVM instance. The user portal handles customer self-service, while the admin console handles global operations and troubleshooting.
Delivery Flow
- The user selects a plan, image and host.
- The backend validates balance, plan limits, host capacity and quotas.
- The system creates order and billing records.
- The backend calls Incus or the host Agent to create the instance.
- Success syncs state, network information, limits and billing status.
- Failure triggers compensation so the user is not charged for an undelivered resource.
User Features
| Feature | Description |
|---|---|
| Create instance | Create LXC / KVM instances from plans, images and hosts. |
| Instance list | View status, resources, expiry and actions. |
| Instance detail | View CPU, memory, disk, network, IPv6, mappings and runtime status. |
| Lifecycle actions | Start, stop, reboot and delete. |
| Web terminal | Connect through /api/ws. |
| Snapshots and backups | Use snapshot or backup features when configured. |
| Traffic | View usage, reset state and limit notifications. |
Admin Features
- View and manage all customer instances.
- Create instances manually for delivery correction or migration.
- Manage hosts, images, initialization commands and storage settings.
- Troubleshoot failed delivery through logs, Agent reports and task state.
Backend Modules
instances,instance-billing,instance-destroy.terminal,snapshots,backups,traffic.agentfor host heartbeat, resource reporting and instance state reporting.
Risks
- Failed creation must compensate billing state.
- Deletion must clean Incus resources and local records.
- Terminal WebSocket must verify identity and instance ownership.
- Admin operations must be audited.
- Stale Agent state can affect capacity decisions.