Templates, cloning & resizing

Reusable environments without accidental credential sharing.

Roadmap · Physical capacity and licensing constraints apply

Templates

Build clean, versioned application images containing software and configuration, not customer browser sessions, API keys or personal files. Pin dependencies, scan builds and record provenance. Inject customer secrets at provisioning time.

Clone

A clone needs another available host for a dedicated rental. It cannot create physical capacity out of the first ThinkCentre. Copy only authorized customer data, create new credentials and require a separate paid allocation. Cloning applications may have licensing consequences.

Resize

RAM on a physical host is bounded by installed hardware. Moving from an 8 GB host to a 16 GB host requires free compatible capacity and a migration/reboot workflow. Do not offer unlimited instant vertical scaling or promise live migration without testing it.

Multi-screen

Additional virtual displays require driver support and more encoding/memory capacity. The planned API must validate dimensions and per-computer limits. Browser resolution changes and physical GPU capabilities are distinct concerns.