# Manage instances

Instances are created from the cluster page and managed from an instance's detail panel. Every action is a discrete permission, refused at the method level, so a role can be granted exactly the verbs it should have.

## Create

Create an instance from the cluster page: choose the node it lands on, pick an image from the live catalog, and set CPU and memory limits, security nesting, and a description. Creation is asynchronous; the instance can be started immediately or left stopped. A system container requires nesting, and a launch requires an explicit target node.

## Lifecycle

Start, stop, and restart run asynchronously with live progress in the panel.

## Rename and reconfigure

- **Rename instance** renames it in place (`instance.rename`).
- **Edit config** changes the CPU limit, memory limit, security nesting, and boot autostart. Some of these apply only on restart; kixctl marks the affected running instance and explains what changed, but never restarts on its own — a **restart now** option applies it when you choose.

## Profiles

Attach or detach a profile from the instance (`profile.attach`, `profile.detach`). Profile management itself is covered under [Networks and profiles](../advanced/networks-and-profiles.md).

## Delete

**Delete instance** requires typing the instance name to confirm. It removes the root filesystem only; persistent volumes are left untouched. Deletion is an admin-tier verb (`instance.delete`).