Trigata
Process automation for people who do not write code.
Structured data tables, custom forms, and trigger-based automations — send an email, call a webhook, run a scheduled job — behind fine-grained role-based access control. Aimed squarely at small-business teams with a process and no engineer.
www.trigata.com (opens in a new tab)- Codebase
- ~42k lines
What it does
- Structured tables with typed columns and validation
- Custom forms that write into those tables
- Automations on triggers: email, webhook, scheduled job
- Role-based access control down to individual shared views
Under it
Next.js on MongoDB, with QStash for the queue, Zod for validation at every boundary, S3-compatible attachment storage, and Web Push for notifications. Unit tested with Vitest and driven end-to-end with Playwright in CI.
Stack
- Next.js
- MongoDB
- QStash
- Zod
- NextAuth
- Playwright
More labs
Keep looking
FlowRunner
LiveDesign pages. Run flows. Ship apps.
A no-code platform where a drag-and-drop page builder and a visual flow engine publish straight to live HTTP endpoints. The visible half is a builder; the interesting half is everything required to execute someone else’s logic on your infrastructure without regretting it.
- Next.js
- Turborepo
- QuickJS/WASM
- Ed25519
- +2
Band Tutor Buddy
LivePractice between lessons, for band kids.
Notation and tab that plays back, listens through the microphone, and tells a kid whether they actually hit the note. Built for the gap between weekly lessons — where nearly all the practice happens and nobody is there to correct anything.
- Next.js
- VexFlow
- Tone.js
- Pitch detection
- +1
Forge3D
LiveA WebGPU game engine and editor that never leaves the browser tab.
Open a tab, build a 3D game, export a single self-contained game.html you can double-click. Forge is a real editor — hierarchy, gizmos, inspector, TypeScript scripting — running on WebGPU with no install, no account, and nothing leaving your machine.
- WebGPU
- WGSL
- TypeScript
- ECS
- +1
Read morewww.forge3d.dev (opens in a new tab)
Want the long version?
Happy to go deeper on any of this — architecture, trade-offs, what I would do differently.