LevelFive-Studio/helix-tribune
AWS-native fork of willchen96/mike: Supabase and Cloudflare replaced with Fargate, Aurora, Clerk, and SST v3.
LevelFive-Studio/helix-tribune is a fork of willchen96/mike that replaces the upstream Cloudflare Workers and Supabase stack with an AWS-native runtime. The backend runs on ECS Fargate behind an ALB; the frontend deploys via @opennextjs/aws to CloudFront and Lambda. Postgres moves to Aurora Serverless v2 fronted by RDS Proxy, with Drizzle ORM replacing @supabase/supabase-js at every callsite and row-level security dropped. Authentication switches to Clerk on both frontend and backend. SST v3 describes the full infrastructure - VPC, RDS, S3, Fargate, Next.js site, and secrets - in a single sst.config.ts. A separate commit renames user-facing product strings from "Mike" to "Helix Tribune" while leaving code identifiers alone, keeping future upstream merges clean.
What's in it
- Helix Tribune branding A clean user-facing rename of Mike to Helix Tribune, applied wherever a reader would notice.
- AWS-native replatform Hosting, database, auth, storage, and email all moved off the upstream Cloudflare and Supabase setup onto AWS services.
- UK audience focus The replatformed build is explicitly pointed at UK users.
- Coordinated stack transplant The infrastructure swap is handled as a single coordinated effort rather than a piecemeal migration.
Direction
infrastructurebranding
Activity
saratpediredla-level5 ↗ analysis ↗ GitHub saratpediredla-level5 ↗ analysis ↗ GitHub Threads of work (detailed view)
LevelFive-Studio rebrands Mike as Helix Tribune
A fork puts its own name on the product and the AI assistant - and deliberately stops there.
User-facing strings renamed Mike -> Helix Tribune; identifiers left alone
saratpediredla-level5 renamed the product across 15 files, but only where end users see it. Code identifiers - `mikeApi`, `MikeChat`, `MikeIcon`, `MikeMessage`, package names - are unchanged by design, keeping the diff small and future upstream merges cleaner.
LevelFive-Studio rips out the cloud foundation and rebuilds helix-tribune on AWS
A wholesale migration off Cloudflare and Supabase onto Amazon's stack, with the default home base moved to London.
helix-tribune migrates from Supabase/Cloudflare to AWS (SST + Fargate + Aurora + Clerk)
saratpediredla-level5 replaced the entire runtime foundation of this fork across three commits: Supabase out, Aurora Serverless v2 and Clerk in; Cloudflare Workers out, Fargate behind an ALB and CloudFront plus Lambda in. The SST v3 config covering VPC, RDS, S3, Fargate, and the Next.js site is the single infrastructure source of truth.
Proposed AWS replatform closed without merging; work visible on the fork as a reference
saratpediredla-level5 opened a PR proposing a full platform swap for willchen96/mike - Supabase/Cloudflare out, AWS-native in - and it was closed eight seconds after it was opened. None of it landed on the upstream repo, but the design is preserved on the helix-tribune fork.
helix-tribune lands Cloudflare/Supabase-to-AWS migration in nine staged commits
saratpediredla-level5 migrated the helix-tribune fork off Cloudflare Workers and Supabase onto a fully AWS-native stack. Nine logically staged commits cover every layer: infra (SST v3), database (Aurora + Drizzle), auth (Clerk), storage (S3), email (SES), and frontend (OpenNext AWS adapter).
Pull requests (detailed view)
✅ Merged (1)
saratpediredla-level5 · opened 2mo ago · merged 2mo ago by saratpediredla-level5 ⛔ Closed without merge (1)
saratpediredla-level5 · opened 2mo ago · closed 2mo ago