Federated_Computer/enterprise.federated.computer
0
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

first candidate for launch

Browse Source
This commit is contained in:
david
2026-05-28 07:21:42 -06:00
parent 9e4d26de44
commit 9e24a217ed
70 changed files with 1117 additions and 484 deletions
Download Patch File Download Diff File Expand all files Collapse all files

10
content/docs/enterprise/cores/_index.md Normal file
View File

@@ -0,0 +1,10 @@
---
weight: 166
title: "Cores"
description: "Provision and manage dedicated compute units for your organization."
icon: "article"
date: "2025-05-27T00:00:00-00:00"
lastmod: "2025-05-27T00:00:00-00:00"
draft: false
toc: true
---

29
content/docs/enterprise/cores/deleting-a-core.md Normal file
View File

@@ -0,0 +1,29 @@
---
weight: 169
title: "Deleting a Core"
description: "How to permanently remove a Core from your account."
icon: "article"
date: "2025-05-27T00:00:00-00:00"
lastmod: "2025-05-27T00:00:00-00:00"
draft: false
toc: true
---
Deleting a Core permanently removes it from your account. Only **Owners** and **Admins** can delete Cores.
## How to Delete a Core
1. Go to **Cores** in the dashboard.
2. Locate the Core you want to remove.
3. Click the delete action for that Core.
4. Confirm the deletion. The Core is immediately decommissioned.
> **Warning:** Deleting a Core is **permanent and irreversible**. Any data or configuration on the Core will be lost. Make sure to back up anything important before proceeding.
## Billing After Deletion
Deleted Cores are removed from your billing at the end of the current billing cycle. You will not be charged for a deleted Core in the following month. There is no prorated refund for the portion of the current month that remains after deletion — the Core runs until the end of the period.
## Add-ons on Deleted Cores
Any add-ons attached to a deleted Core are automatically canceled when the Core is deleted. You will not be billed for those add-ons in subsequent billing cycles.

32
content/docs/enterprise/cores/provisioning-a-core.md Normal file
View File

@@ -0,0 +1,32 @@
---
weight: 168
title: "Provisioning a Core"
description: "How to provision a new Core from the dashboard."
icon: "article"
date: "2025-05-27T00:00:00-00:00"
lastmod: "2025-05-27T00:00:00-00:00"
draft: false
toc: true
---
Provisioning a Core starts a new compute instance under your account. Owners and Admins can provision Cores from the Cores section of the dashboard.
## How to Provision a Core
1. Navigate to **Cores** in the main navigation.
2. Click **Provision a Core**.
3. Optionally, select any add-ons you'd like enabled on this Core (Monitoring, Backup, etc.).
4. Confirm. The Core is created immediately and moves into **Provisioning** status while the Provisioner sets it up.
5. Once provisioning completes, the Core will show as **Active** with its assigned IP address visible in the dashboard.
## Billing for New Cores
Cores are charged on a monthly basis as part of your regular billing cycle. When you provision a Core mid-cycle, the cost for the remaining days in the current period is **prorated** — you're only charged for the time the Core was active, not the full month.
Any Core add-ons selected at provisioning are also prorated in the same way.
> **Note:** Your account balance is used first when any charge is incurred. Only the amount exceeding your balance is charged to your card. See [Account Balance](../billing/account-balance.md) for details.
## SSH Access
Your account SSH key pair (generated at checkout) is the credential used by the Provisioner when setting up your Core. You can find your SSH public key in **Account Settings**. Enterprise and Consultant tier accounts can also use the Provisioner API directly to automate Core management.

32
content/docs/enterprise/cores/what-are-cores.md Normal file
View File

@@ -0,0 +1,32 @@
---
weight: 167
title: "What Are Cores"
description: "An introduction to Cores — dedicated compute units tied to your account."
icon: "article"
date: "2025-05-27T00:00:00-00:00"
lastmod: "2025-05-27T00:00:00-00:00"
draft: false
toc: true
---
A **Core** is a dedicated compute unit provisioned to your account. Think of it as a private server that Federated manages on your behalf — you don't deal with hardware or hosting directly, but the Core is exclusively yours.
Each Core has its own IP address and is provisioned into your account's environment. Cores are billed on a per-unit, per-month basis on top of your membership fee. The exact per-Core price depends on your plan tier.
## Core States
A Core moves through several states during its lifecycle:
- **Available** — The Core has been allocated to your account but provisioning hasn't started yet.
- **Provisioning** — The Provisioner is actively setting up the Core. This typically takes a few minutes.
- **Active** — The Core is live and operational, accessible at its assigned IP address.
- **Failed** — Provisioning encountered an error. Contact support if a Core is stuck in this state.
- **Decommissioned** — The Core has been deleted and is no longer running.
## Core Add-ons
Each Core can have optional add-ons attached to it, such as Monitoring, Backup, Customer Service, and Technical Support. Add-ons are billed per Core, per month. See [Add-ons](../billing/add-ons.md) for pricing and details.
## Core Limits
Your plan tier may define a maximum number of Cores. The Enterprise and Consultant tiers have no hard Core limit by default. Check your plan details or contact support if you need to confirm your Core limit.