Before you create a client
Sign in to the Platform Portal as PartnerAdmin or SuperAdmin and open Admin. A client is a tenant workspace, not a host. The New client form always places it on the existing host you explicitly select; it never launches infrastructure.
A PartnerAdmin needs at least one host granted to their own partner by a SuperAdmin. The host must have a free client slot and must not be failed, deleting, or suspended. If host or grant loading fails, creation stays blocked until those lists can be verified.
If no eligible host exists, complete the instance approval workflow first. A new host still needs an explicit partner grant.
Create a client, step by step
- In New client, choose the owning partner (SuperAdmin), or confirm your own partner (PartnerAdmin).
- Enter a required Name. Optionally provide a URL-safe Slug; otherwise the platform generates a unique slug from the name.
- Choose Small, Standard, or Large as the client's Size. This is a platform tier, not a machine specification.
- Choose an idle threshold and decide whether the client must be Always on.
- Select an existing Host with free capacity and submit Create client.
- Verify the saved client record, its owning partner, host assignment, and settings in the Clients section. If the API reports an error, do not assume creation succeeded.
Client form field reference
| Field | Meaning and rules |
|---|---|
| Partner | SuperAdmin chooses the owner. PartnerAdmin is bound to their own partner and cannot switch partners in this form. |
| Name | Required display name, up to 200 characters. |
| Slug (optional) | Up to 60 lowercase letters, digits, or hyphens. Omit it to generate a unique identifier from Name. |
| Size | Small, Standard, or Large client tier. It does not choose the host or specify vCPU/RAM. |
| Stop after idle (minutes) | Per-client inactivity threshold: 5–1,440 minutes; default 30. |
| Host | Required existing host with capacity. PartnerAdmins see only hosts granted to their partner. No server is launched by this field. |
| Always on | Opts this client out of idle-stop behavior. Does not create, select, or resize a host. |
Small, Standard, and Large are not EC2 hardware
Client Size and the instance request's Plan size are platform tiers. Instance type is the exact offered EC2 hardware shape; compare the vCPU and memory shown alongside it when assessing machine capacity.
Automatic sizing uses configurable tier mappings. Current defaults are Small → t4g.medium, Standard → m7g.large, and Large → m7g.xlarge. Deployments can override them. In the reviewed instance-launch workflow, the explicitly selected Instance type determines the machine, independently of the plan label.
The configured Large tier is dedicated when a host is automatically provisioned. That does not mean choosing Large in New client launches or isolates a server: this form uses your chosen existing host. For an explicitly single-client host, use Dedicated (one client) in an instance request.
Do not confuse these infrastructure/client tiers with the marketing site's catalog product-count plans. A tier name alone is not a CPU/RAM specification, a price quote, or a promise of identical resources for every tenant.
Idle-stop: lower compute usage, with wake-up delay
With Always on unchecked, the idle threshold participates in power-saving host stop. Stopping compute retains the persistent host disk and tenant data. Pending or processing jobs and near-term scheduled work can keep a client awake.
A stopped host may need time to wake before responding. Idle-stop is therefore an availability/cost choice, not a data-retention policy. On a shared host, one client's idle setting is not a guarantee that the entire machine stops: other clients' activity and Always on settings matter.
Always on: prioritize continuous availability
Always on prevents this client's idle state from allowing its host to stop. Choose it for users or integrations that cannot tolerate the wake-up delay. The tradeoff is more compute cost while the host keeps running; Always on does not change which host serves the client.
| Need | Suggested setting | Tradeoff |
|---|---|---|
| Intermittent use; delayed first response is acceptable | Leave Always on unchecked and choose an idle threshold. | Compute can stop when eligible; users may wait for wake-up. |
| Immediate responses at any time | Check Always on. | Avoids idle-stop wake-up delay, with higher running compute usage. |
| Data must remain saved, but instant response is unnecessary | Idle-stop can be used. | Persistent disk remains; this is not host termination. |
“Live” can mean either continuously responsive or safely stored. For continuous response, choose Always on; for preserving saved data while compute sleeps, idle-stop can still be suitable. Neither setting guarantees uptime during failures or maintenance.
Client deletion is not host termination
Deleting a client removes its tenant access and may stop the host from serving that tenant. It is not the same as stopping a host, and it does not terminate the host's infrastructure. Do not interpret this guide as a guarantee of client-data recovery after deletion.
Host termination is a separate, destructive SuperAdmin operation that deletes the host disk and requires zero clients. Review the host deletion checklist before using it.
Troubleshoot client creation and power settings
- No host can be selected: ask a SuperAdmin to grant a host to the correct partner, verify free capacity, or complete a new-instance request and grant.
- Creation is blocked: confirm PartnerAdmin/SuperAdmin access and resolve host/grant loading errors. ClientAdmin does not have partner onboarding permissions.
- The host does not stop after this client's threshold: review other clients, Always on, pending/processing jobs, and scheduled work with the operator.
- First access is slow after inactivity: the host may be waking. Use Always on if that delay is unacceptable.