Stack map

Short map of support systems early organizations 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. Which rows you actually stand up depends on org stage.

Forge identity first (optional fast path): Fast org bootstrap — About, .github profile, site, docs hub. This table stays the IT stack.

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

Team chat / ops bots

Hosted Slack/Discord until seat cost or residency bites; then Mattermost on a real VPS (not shared hosting) with optional R2/B2 offload

Chat · Mattermost self-host

Org DNS + platform IaC

Pulumi TypeScript org infra repo; member-only static hosts behind Cloudflare Access

Org infra · Org infra repo pattern · Access how-to

Fund OSS maintenance / infrastructure

GitHub Sponsors and/or Open Collective (fiscal host); grants when the work is public-good scoped — see landscape. On-site: show balance + floor/goal (Nonprofit Resources guide).

Funding · OSS funding landscape · Donation ask ideas

What this hub is not

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

  • Not a full developer toolchain — see Recommended tools.

  • Not AI-studio bootstrap (Cursor skills / MCP / agent rules) — that sibling path is Vibe coding bootstrap; stage defaults still remind you during solo / shipping.

  • Not a mandate to self-host everything.

Related