Executive Overview

Before we touch CloudStack, VLANs, or a single Terraform module, we zoom out.

This is the executive layer of HostKid (Volume 0 in the handbook). Not slide-deck fluff. Not “business buzzword bingo.” It's the honest answer to: what kind of company are we building, who pays us, what do we owe them, and what does “good” look like from the top?

Engineers, don't skip this

Beautiful platforms nobody can sell are expensive hobbies. This volume keeps us honest: HostKid is a hosting company, not just a homelab with a logo.

Executive ownership: not just sales and orders

As the executor and owner of this project, I don't only think about sales-driven orders and generic company goals. “Get customers, ship VPS, hit revenue.” That's necessary. It's also incomplete.

Running a hosting company means holding two dashboards in your head at once:

Business line	Executive question
Revenue & products	What do we sell, who buys it, and does the journey from signup to provision actually work?
Technical north stars	Is the platform secure, observable, automatable, and defensible, not just “up right now”?

The biggest technical lines I care about at this level, before diving into configs, include:

Security & trust: what customers hand us, shared responsibility, ISO-aligned intent, not bolt-on hardening later (Security & trust posture, Governance)
ERP & billing sync: the company's ERP (ERPNext, Volume 11 Corporate) must stay aligned with products, entitlements, and provisioning. Paid but not provisioned, or provisioned but not billed, is a company-killer, not a bug ticket (Business model, Volume 11 Corporate)
Identity & access: who can touch portal, API, CloudStack admin, and support tools; one identity story, not five silos (Volume 9)
Provisioning integrity: customer order → queue → CloudStack → notify must be traceable and repeatable (Volume 19)
Observability & SLOs: we measure health before customers feel pain (Executive metrics & SLOs)
Automation & drift: no tribal hypervisor clicks; GitOps-shaped change (Volume 21)

Why this lives in Executive Overview

These aren't "Volume 22 problems" or "Volume 11 Corporate problems" alone. As owner, I set intent and boundaries here, then later volumes implement. If ERP and portal disagree on what a customer owns, that's an executive failure first and a debugging session second.

Bottom line: Executive Overview is where business goals and technical non-negotiables meet. Sales tells you what to build demand for. Security, sync, and architecture tell you whether the company survives owning it.

People first: values, respect, and a non-toxic culture

Let's talk about the part that doesn't show up in a network diagram but decides whether the company lasts.

HostKid enforces, at executive level, a simple non-negotiable: no toxic work environment. Not “we'll fix culture later when we're bigger.” Not “that's an HR thing.” From day one in this handbook, the expectation is clear:

Robust values apply to every department and every individual
People should feel valued, respected, and safe to speak up when something is wrong
Remote or on-site doesn't change the standard. Location is logistics. Behavior is culture.

This isn't soft fluff. Toxic teams break on-call, ship blind, hide incidents, and burn out the exact people you need when a customer DNS zone goes sideways at midnight.

Value (executive intent)	What it looks like in practice
Respect	Disagree on architecture without disrespecting the human. No hero worship, no blame theater.
Transparency	Decisions and tradeoffs written down. Nobody has to guess why we chose CloudStack or ERPNext.
Ownership	Clear accountability per department, without throwing people under the bus when prod hiccups.
Learning in public	Bad calls stay in the docs when they teach something. That's this entire project.
Sustainable pace	Uptime matters. So do humans. On-call and incidents are not an excuse for permanent crunch.

What I mean as owner

If someone joins HostKid (even as a future teammate in this lab story), they should never feel like a replaceable ticket-closer. Engineering, support, corporate ERP, security: same bar. Valued. Respectful. Clear expectations.

Handbook-first: inspired by GitLab

One of the companies that impressed me most, remote and on-site, is how GitLab runs in public. Not a polished annual report. A living GitLab Handbook where you can read how they actually operate: values, mission, communication, engineering, finance, security, people policies, product principles, the whole stack of “how does this company work?”

As the owner making decisions, I treat that handbook as a serious source of inspiration:

What GitLab models	What HostKid takes from it
Handbook-first culture	If it's not written, it's harder to scale and impossible to audit fairly
Cross-functional clarity	Engineering, finance, legal, people: same transparency standard
Remote-ready operations	Async-friendly docs, explicit ownership, no “you had to be in the room” knowledge
Technical + business in one place	Not “tech docs over here, accounting vibes over there”

We're not cloning GitLab. We're a mini hosting company with our own stack (CloudStack, ERPNext, Frappe Insights). But the idea? Document how the company runs. Make it readable. Make it honest. Let future teammates and future you open one place and understand vision, values, org, and technical direction.

HostKid is our handbook. Volume 0 is the executive chapter. The rest of the volumes are how we build and operate without losing the human and the decision record along the way.

Browse GitLab's approach when you want a north star for what “public, serious company documentation” looks like: handbook.gitlab.com.

What you'll walk away with

A clear picture of what hosting is and who we serve
Company values and a non-toxic culture standard for every department
How money flows and what we sell
Who owns what inside the company
Core values, LMS, and fair evaluation so growth and compensation speak the same language
The customer journey from signup to churn
A product catalog mindset (SKUs, not random VMs)
A high-level architecture you can draw on a whiteboard
Executive metrics: north stars, not Grafana panels
Governance & ISO thinking: scope and intent, not control checklists yet
A security trust model: what customers trust us with

Docs in this volume

Read in order the first time. After that, jump to whatever decision you're making.

Doc	One question it answers
What is a hosting company?	What business are we actually in?
Business model & revenue	How does money flow?
Organization & departments	Who owns what?
Core values & human engine	How do people grow, get evaluated fairly, and train for incidents?
Customer lifecycle & journey	What happens from first click to churn?
Product portfolio & catalog	What do we sell, in product terms?
Technical decisions & stack rationale	Why CloudStack, ERPNext, and the other stack picks?
High-level architecture	What are the major boxes and how do they talk?
Executive metrics & SLOs	How do we know the company is healthy?
Governance, risk & compliance	What rules and frameworks govern us? (ISO intent)
Security & trust posture	What do customers trust us with?

What this volume deliberately does NOT cover

Topic	Where it lives
CloudStack install & operations	Volume 4
Platform selection (Proxmox vs CloudStack)	Volume 3
ERPNext / corporate ERP	Volume 11
Provisioning engine implementation	Volume 19
Security tooling (Vault, CrowdSec, etc.)	Volume 22
Day-to-day ops & incident process	Volume 27