Naming & Components¶
The star metaphor — use these names exactly. Each component has a public/internal name, the metaphor behind it, its audience, and the repo it ships from.
| Component | Name | Metaphor | Audience | Repo |
|---|---|---|---|---|
| Product | Starform | Star formation | Public | — |
| Control Plane | Starbase | Central space station | Internal / blogs | starform/starbase |
| Cluster Agent | Shuttle | Deployed to remote locations | Internal / blogs | starform/shuttle |
| Build System | Starforge | Forges source into images | Internal / blogs | Package in Starbase |
| Frontend | Stardeck | Ship's command deck | Public | starform/stardeck |
| Architecture overview feature | Mission Control | Bird's-eye view of systems | Customer-facing | Part of frontend |
| Pod instance tiers | Mininova → Ultranova | Stellar scale | Customer-facing | — |
Pod Tier Names:
| Tier | Nova Name | CPU | RAM | Price |
|---|---|---|---|---|
| Hobby (shared) | Mininova | Shared | 512 MB | $5/mo |
| Dedicated entry | Micronova | 0.5 vCPU | 512 MB | $18/mo |
| Dedicated mid | Nova | 1 vCPU | 2 GB | $36/mo |
| Dedicated growth | Supernova | 2 vCPU | 4 GB | $85/mo |
| Dedicated scale | Hypernova | 4 vCPU | 8 GB | $175/mo |
| Dedicated premium | Ultranova | 4 vCPU | 16 GB | $250/mo |
Cross-references
The two Starbase binaries + repos → Binaries & Repos ·
system topology → System Topology · the tier name as a pod
label (starform.io/tier) → §24.2 · Mission Control →
Stardeck. Canonical map:
Canonical Sources.