TSYSGroupBOD/TSYSGovernance
2
0
Fork 0
Code Pull Requests Actions Packages Releases Activity
Files
main
TSYSGovernance/pages/122.Handbook.SourceMaterial.people.team-structure.infrastructure/default.md
Charles N Wyble a1662cff1a feat: convert mdbook to Grav format (199 pages) 
Converted from mdbook src/ in input/ to Grav pages/ format:
- Added YAML frontmatter to all pages
- Created numbered folder structure (01.home, 02.Bylaws.*, etc.)
- Preserved all content from Bylaws, Handbook, OperatingAgreements,
  Policies, and JointVenture sections

super ultra big merge completed. scope of work clearly defined. let's go build!

Assisted-by: GLM-5 via Crush <crush@charm.land>
2026-03-02 16:35:00 -05:00

2.1 KiB
Raw Permalink Blame History

title, menu
title menu
People People

title: Team Infrastructure & Deployments sidebar: Handbook showTitle: true hideAnchor: true

Image of Cloud Infrastructure

People

Mission

Make using and developing for PostHog as reliable as running water. Wherever you want it.

Goals

  • We don't lose events
  • Data is as up to date as possible
  • Engineers always be able to ship and build
  • Fail fast. Fix faster.
  • Ship anywhere
  • Stack scales with demand
  • Support Small Teams (and contributors) in building and debugging Posthog
  • Be frugal.

Responsibilities

Concrete things we take responsibility over:

  • app.posthog.com and its infrastructure
  • On Prem & Single Tenant deployments
  • CI/CD - How we deploy
  • Data infrastructure (Clickhouse, Kafka)
  • Monitoring and Alerting stack

Customer

  • Other Small Teams in making sure they have the tools (databases, queues, etc) and the ability to deploy effortlessly that they need to build
  • End users (Both cloud and on-prem teams)

Output metrics

VPC

Retention
  • Metric: Retention
  • Objective: Better than cloud

Cloud

Data Loss
  • Metric: Data loss %
  • Objective: < 0.1%
Uptime
  • Metric: Uptime
  • Objective: > 99.99%
Speed
  • Metric: Speed
  • Objectives
    • Event ingestion: TBD
    • Query response: TBD
  • Overall: We should anticipate increasing demand (either manually or automatically)
Cost
  • Metric: Infra Costs
  • Objective: Our costs should grow at a rate that is sublinear relative to scale

Dev Experience

Dev Experience NPS (Infra)
  • Metric: Developer experience (relating to infra) (maybe NPS?)
  • Objective: TBD (maybe NPS?)

Slack channel

#team-deployments-and-infrastructure

View Git Blame Copy Permalink