PlayPalzPlatform Documentation

Everything you need to build, run, and ship the PlayPalz platform — from a fresh laptop to a production deploy.

Get Running in 15 Minutes

System Architecture

Platform Brief

Start Here

Prerequisites, local environment, the monorepo layout, and the day-to-day commands you will actually use.

Onboarding guide

Architecture

How the seven services fit together — auth, realtime, media processing, livestreaming, and the money flow.

System overview

Services

One page per service — what it owns, how to run it, its environment, and its failure modes.

Service index

API Reference

Every REST endpoint grouped by domain, plus webhooks and the realtime socket event contract.

API conventions

Mobile App

The Expo app — file-based routing, the TanStack Query data layer, the design system, and release builds.

Mobile overview

Infrastructure

Terraform on DigitalOcean, Kubernetes manifests, sealed secrets, DNS and TLS, and observability.

Infrastructure overview

What is PlayPalz?

PlayPalz is a social platform for gamers. Fans discover PlayPalz — e-girls, gamers, and coaches — and pay to spend time with them: subscribing to a creator's private channel, chatting by text or voice, gifting Play Coins during livestreams, and booking 1-on-1 sessions.

The platform is a pnpm + Turborepo monorepo containing an Expo mobile app, a Next.js marketing site, five backend services, and four shared packages, deployed to DigitalOcean Kubernetes.

Pick your path

You are…	Start at
A developer setting up for the first time	Local Setup
A developer picking up a backend ticket	Service Index → API Reference
A developer picking up a mobile ticket	Mobile Overview
On call, or shipping a release	Deploying → Runbooks
Handling infrastructure or cost	Infrastructure → Cost & Scaling
An executive or stakeholder	Product Overview

The 60-second version

Rendering diagram…

Read the full picture in System Overview.

Keeping these docs honest

These pages are generated from a reading of the code as it exists on master. When you change a route, an environment variable, a queue name, or a deployment, update the matching page in apps/docs/ in the same pull request. Stale docs are worse than no docs.