Shared commerce workflow, catalog sync, and Stripe-centered operator design.
This view trades the diagram for a direct read: rows are projects, columns are technologies, and the lower matrix shows where systems are intentionally related beyond shared stack.
Stack overlap matrix
Colored cells mark technologies a project actually uses. Grouped columns make the stack shape readable without relying on a graph layout.
| Project | Foundations | Frontend | Payments | Operations | Infrastructure | Data | Backend | ||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| Role | TypeScript | Python | Node.js | Astro | Next.js | React | Tailwind CSS | Leaflet | Stripe | CLI tooling | Bash | Testing | Nginx | SSH | rsync | JSON manifests | SQLite | Express | FastAPI |
| My Store | ● | · | · | ● | · | ● | ● | · | ● | · | · | · | · | · | · | · | · | ● | · |
| Natural Stripe | · | · | ● | · | · | · | · | · | ● | ● | · | ● | · | · | · | ● | · | · | · |
| WebJuggle | ● | ● | · | · | ● | ● | ● | · | · | · | · | · | · | · | · | · | · | · | ● |
| Juggle | · | ● | · | · | · | · | · | · | · | · | · | ● | · | · | · | · | · | · | · |
| Internal Ops Monitor | · | ● | · | · | · | · | · | ● | · | · | · | · | · | · | · | · | ● | · | ● |
| QR Studio | ● | · | · | · | ● | ● | · | · | ● | · | · | · | · | · | · | · | · | · | · |
| Alien API | · | ● | · | · | · | · | · | · | · | · | · | · | · | · | · | · | ● | · | ● |
| ngdeploy | · | · | · | · | · | · | · | · | · | · | ● | · | ● | ● | ● | · | · | · | · |
| Newsscribe | · | ● | · | · | · | · | · | · | · | · | · | · | · | · | · | · | · | · | · |
| ComfyUI Lab | · | ● | · | · | · | · | · | · | · | · | · | · | · | · | · | · | · | · | · |
Affinity matrix
This lower matrix only marks the curated relationships that matter at a product and workflow level, not every shared dependency.
| Project | My Store | Natural Stripe | WebJuggle | Juggle | Internal Ops Monitor | QR Studio | Alien API | ngdeploy | Newsscribe | ComfyUI Lab |
|---|---|---|---|---|---|---|---|---|---|---|
| My Store | — | 100% | · | · | · | 58% | · | 52% | · | · |
| Natural Stripe | 100% | — | · | · | · | · | · | · | · | · |
| WebJuggle | · | · | — | 95% | · | · | · | · | · | · |
| Juggle | · | · | 95% | — | · | · | · | · | · | · |
| Internal Ops Monitor | · | · | · | · | — | · | 68% | 72% | · | · |
| QR Studio | 58% | · | · | · | · | — | · | · | · | · |
| Alien API | · | · | · | · | 68% | · | — | · | · | · |
| ngdeploy | 52% | · | · | · | 72% | · | · | — | · | · |
| Newsscribe | · | · | · | · | · | · | · | · | — | · |
| ComfyUI Lab | · | · | · | · | · | · | · | · | · | — |
Why the strong connections exist
The curated affinity cells above map to these human-readable reasons, so the matrix stays compact while the rationale stays visible.
Both revolve around parametric making workflows and Python-driven geometry logic.
Local-first operational tooling with simple deploy surfaces and direct ownership of infrastructure.
Pragmatic Python systems shaped around controlled internal workflows instead of broad platform abstractions.
Interface-heavy browser tools where product polish matters alongside implementation speed.
Shipping discipline and self-managed deployment practices connect the storefront to the infrastructure layer.