SysML Repo Modeler
Supabase Platform
Five repositories, four languages, one system
This model was read out of five separate repositories at once. The connections between the parts are the point: they came from the source, not from a diagram someone drew. Follow an edge from the storage API to Postgres, or from the edge layer into auth, and drill in to see which component owns each interface.
What was analyzed
| Repository | Branch | Commit |
|---|---|---|
| auth | master | fc654b05 |
| postgrest | main | 6a7ad335 |
| realtime | main | 3dfce67c |
| storage | master | 4ae10084 |
| supabase | master | 81523d5d |
Why this repository
This is the case the analyzer was built for. Supabase is not one codebase — it is a Go auth service, a TypeScript storage API, an Elixir realtime server and a Haskell REST layer, developed in separate repositories and run as one platform. No single repository contains that picture.