Stack map

Short map of support systems early tech orgs usually need besides product code. Each row opens a capability area with room for explanation, how-to, and interconnect articles. Per-org wiring stays in that org’s infra and product docs.

Stack

Job Default lean path Area

Human vs product email

ZeptoMail / Resend / Customer.io lane split

Email

Scheduling / booking pages

Cal.com hosted for SLA + orgs; Cal.diy when you self-host MIT community edition

Scheduling · Cal.com and Cal.diy

Product / brand design (Figma-class)

Penpot (open file format, self-host or cloud); Figma when partners require it

Design · Penpot

Human + machine secrets vault

Bitwarden cloud (or official self-host for compliance); Vaultwarden for tiny self-host

Vault · Bitwarden and Vaultwarden

Org DNS + platform IaC

Pulumi TypeScript org infra repo

Org infra · Org infra repo pattern

What this hub is not

  • Not a product partner marketplace (POS, delivery marketplaces, etc.).

  • Not a full developer toolchain — see Recommended tools.

  • Not a mandate to self-host everything.

Related