CAPABILITY / 04

Cloud

In production

Production cloud: AWS Lightsail, Azure App Service on StrikeHike v1, Google Cloud with OAuth and the Meet/Calendar APIs, Supabase Postgres.

Updated

01 / PROOF

The measured part

  • AWS

    Lightsail runs StrikeHike and this site

    Source
  • Azure

    App Service ran StrikeHike v1

    Source
  • GCP

    Google Cloud project, OAuth and the Meet REST API (v2); Calendar API

    Source

02 / WHAT I DO

In practice

  • Run a small production estate on AWS Lightsail with Docker Compose.
  • Use Supabase Postgres on the Job Portal and the Scheduler.
  • Run StrikeHike and this site behind Caddy with TLS on the same host.
  • Ran StrikeHike v1 on Azure App Service.
  • Run a Google Cloud project with OAuth and the Meet and Calendar APIs; Meet stores recordings in Google Drive.

03 / WHERE I'VE DONE IT

The systems behind it

04 / STACK

What it runs on

  • AWS

    Lightsail host for StrikeHike and this site

    See the system
  • Azure

    StrikeHike v1 ran on Azure App Service

    See the system
  • Google Cloud

    Google Cloud project, OAuth, Meet REST API (v2), Calendar API; recordings in Google Drive

    See the system
  • Supabase

    Postgres for the public product

    See the system
  • Docker

    Compose stack built and cut over on deploy

    See the system
  • Caddy

    TLS, routing and reverse proxy

    See the system
  • AWS ▸AWS Glue (in my roles)In my roles

    AWS Glue in my roles (self-reported)

  • Azure ▸Azure Data Factory (in my roles)In my roles

    Azure Data Factory in my roles (self-reported)

  • Azure ▸Azure AI Foundry (in my roles)In my roles

    Azure AI Foundry in my roles (self-reported)

05 / LIMITS

What this does not claim

No wider GCP services (BigQuery, GKE) are claimed. No multi-cloud IaC is claimed.

06 / RELATED CASE STUDIES

All work
ProductionStrikeHike

Live at strikehike.com; this engine replaced the first version on 25 Oct 2026. No accuracy or usage figures are claimed.

StrikeHike: a macro and planetary research terminal, built and run solo

A live research site that sets the US macro record beside the planetary sky, with tested claims, a weekly roundup, a public ledger, upcoming dates, and recession and decline histories. Next.js and FastAPI. Research, not advice.

131 of 131 commits on its main branch are mine

Built and testedRVM CAD Job Portal

Merged with 616 of 616 tests passing at 48c3cab1 (23 Jun 2026). RVM approved describing the behaviour on 15 Nov 2026; production rollout state was not independently verified.

Interviews that schedule, record and file themselves

One interview, end to end in the Job Portal: a Google Meet space and invites, a consent gate before recording, a recording state machine, and Drive filing with metadata. Built in one commit, with 616 of 616 tests passing at that commit.

70 files in the feature commit

07 / QUESTIONS

Short answers

Which clouds has KP actually run?

AWS Lightsail runs StrikeHike and this site. Azure App Service ran StrikeHike v1. Supabase Postgres sits under the Job Portal and the Scheduler. The Job Portal interviews use a Google Cloud project with OAuth and the Meet and Calendar APIs; Meet stores recordings in Google Drive.

Is there infrastructure as code?

No. The estate is configured and deployed with Docker Compose, Caddy and CI workflows; multi-cloud Terraform is not claimed.

Need this on a real system?

Hiring for a role, or scoping a short engagement? The Hire page has the role families and contact; Consulting has the scoped offers.

ESC

↑ ↓ to move · Enter to open · Esc to close