Tech
How the G-Starlink stack is built and run.
Sections
- System architecture — what runs where
- Credentials policy — how we handle secrets
- Deployment — release process and environments
- Incident response — when production breaks
Current stack
| Component | Tech | Hosted |
|---|---|---|
| Storefront | Shopify | Shopify |
| Order management (OMS) | Next.js + Supabase | Vercel / Cloudflare Pages |
| eSIM Hub (partner portal) | Next.js (WIP) | TBD |
| Chatbot | Cloudflare Workers | Cloudflare |
| Competitor monitoring | Cloudflare Workers + D1 | Cloudflare |
| Handbook (this site) | Next.js + Nextra | Cloudflare Pages |
| Knowledge base DB | Supabase tzcmqeucnabgcorqbpnl | Supabase |
| OMS DB | Supabase (separate project) | Supabase |
Repositories
All code lives on GitHub under the SlowBoat2015 account:
shopify-esim-system— OMSesim-hub— Partner portal (WIP)gstarlink-chatbot— Cloudflare Workers chatbotgstarlink-handbook— This handbook
Principles
- Simple over clever. We’re a small team. Every “advanced” piece of infrastructure is a tax on future us.
- Hosted over self-managed. Prefer Supabase, Cloudflare Pages, Vercel over running our own servers.
- One source of truth per concern. Product catalog in Supabase. Orders in OMS. Don’t replicate.
- Secrets never in code. Supabase Vault, environment variables, or secrets manager — never commits.