Back

The Working Stack

Every layer, side by side.

The full stack in one card — the same four layers the home reel walks through, held open at once.

01 · What the user touches

Interface

Rendering, motion and type decisions that survive contact with real users — built once, themed twice, measured always.

  • ReactPrimary UI runtime
  • TypeScriptType system
  • Next.jsApp framework
  • Tailwind CSSStyling system
  • GSAPMotion engine
  • ReduxClient state

02 · What answers the request

Services

Business rules sit behind honest contracts: typed modules, predictable failures, no surprises in the response body.

  • Node.jsServer runtime
  • NestJSService framework
  • RESTAPI style
  • Express.jsHTTP layer
  • GraphQLQuery layer
  • Socket.ioRealtime transport

03 · What survives a restart

Persistence

Schemas are promises. Modelling comes before tuning, and every index has to earn its write cost.

  • PostgreSQLPrimary store
  • MongoDBDocument store
  • MySQLRelational standby
  • PrismaORM
  • MongooseODM
  • RedisCache & queues

04 · What keeps it online

Infrastructure

Boring infrastructure on purpose — small surfaces, clear logs, alarms that page a human only when it matters.

  • DockerPackaging
  • AWSPrimary cloud
  • CloudWatchObservability
  • NGINXEdge proxy
  • KubernetesOrchestration
  • Google CloudSecondary cloud

05 · What proves it works

Verification

Tests are documentation that executes. Coverage follows risk, not vanity metrics.

  • JestUnit suites
  • CypressE2E flows
  • StorybookComponent workshop
  • PlaywrightBrowser matrix

06 · How it ships

Delivery

From commit to URL without ceremony: automated pipelines, preview environments, rollbacks rehearsed before they are needed.

  • GitVersion control
  • VercelDeploy target
  • GitHub ActionsCI pipelines
  • FigmaDesign handoff
  • JenkinsLegacy CI