A tour of the Foxcore panel
Where Services, the instance header, Ports, Console, Files, Backups, and Billing live, and which panels stay unavailable until a node is ready.
Services is the list
Services lists the instances on your account that are not destroyed. Each row leads with the name, the observed power, and the join host when an allocation exists. Create is on the same page and stays closed when no ready node has free capacity.
Opening a row gives you one instance workspace. The instance id stays the same across power changes, console sessions, file edits, backups, and a title switch.
The instance header
Start, stop, and destroy sit in the instance header. The panel records desired power first and queues a job. Observed power changes when the node reports, so a short difference between the two is normal. While a power job is open, the header hides a second click and refreshes until the job settles.
The overview under the header shows the pack, the size, the region, and the join address. It does not grow a second power strip or a second set of billing controls.
The tabs
Ports lists every allocation with its protocol and pack bind. Console attaches a live session through the NodeSession Durable Object when the node is ready and the guest is running. Files browses the instance volume over the files RPC. Backups creates, lists, restores, and deletes archives on the node.
Each of those tabs can show UnavailablePanel. That is the honest state when there is no node, the session is stale, or observed power is not running. It is not a loading animation and it is not a promise that a hidden feature exists.
Account and support
Account → Settings → Billing holds the plan, the processor status, and the customer portal. Account security holds sign-in methods. Support is a Foxcore form stored in the panel, not a third-party desk, and signed-in tickets stay under Your messages.
If a panel action is missing, read the page before assuming a browser fault. Foxcore renders the unavailable state rather than a mocked success.