Projects · Mini Hostpapa
Product Portfolio & Service Catalog
What HostKid sells: SKUs, offerings, v1 scope, and how products map to the platform.
Product Portfolio & Service Catalog
Engineers love building platforms. Customers love buying products.
This doc is the catalog at executive level: what we sell, what each thing includes, and what's in scope for HostKid v1 vs later. Every SKU should eventually map to a CloudStack offering, a billing product, and a portal tile.
Product philosophy
- Name what you sell: “VPS Starter” beats “KVM instance type 7”
- Bundle clearly: disk, RAM, bandwidth, mailboxes, support tier
- Automate delivery: if it can't be provisioned without a human, it's not a product yet
- Document limits: oversell is an incident waiting for a calendar invite
A SKU is a promise. Engineering, billing, and support must agree on what that promise means.
Core product lines
| Product line | Customer gets | Platform anchor | Volume |
|---|---|---|---|
| VPS Hosting | Linux VM, root access, IP, optional backups | CloudStack compute offering + template | 15, 19 |
| Shared Hosting | Web space, PHP, DB, panel access | Shared stack / panel automation | 14 |
| Domains & DNS | Domain registration or DNS hosting, records API | PowerDNS + registrar integration | 12 |
| Business Email | Mailboxes, SMTP/IMAP, SPF/DKIM/DMARC | Mailcow / mail platform | 13 |
| Object Storage | S3-compatible buckets (later) | MinIO | 16 |
Example VPS catalog (v1 sketch)
| SKU | vCPU | RAM | Disk | Target customer |
|---|---|---|---|---|
| VPS Starter | 1 | 2 GB | 40 GB | Blog, small app |
| VPS Standard | 2 | 4 GB | 80 GB | Agency site, API |
| VPS Pro | 4 | 8 GB | 160 GB | E-commerce, multi-app |
Numbers are placeholders. The structure matters. CloudStack service offerings mirror these rows in Volume 4 and 15.
Add-ons (attach to any base product)
- Extra IPv4 address
- Automated daily backups
- Additional mailboxes
- Priority support queue
- Managed migration (Solutions-led, Volume 25)
Add-ons need ERPNext line items (Volume 11, Corporate) and provision hooks (Volume 19).
v1 scope vs roadmap
HostKid v1 (documented first):- VPS + DNS + portal + corporate ERP skeleton + provisioning engine path
- Identity (SSO for portal admin minimum)
- Shared hosting at scale
- Full email product
- Object storage
- Reseller / white-label
Volume 28 holds future evolution. This doc prevents building everything at once.
Catalog → systems mapping
If any arrow is manual, mark it technical debt in the handbook.
What this doc does not cover
- ERPNext product configuration → Volume 11, Corporate
- CloudStack offering API calls → Volume 4, 15
- HestiaCP / WordPress stack → Volume 14
Next: Technical decisions & stack rationale. Why CloudStack, ERPNext, and the rest before the architecture diagram.