Why did you use convex as backend?

Great question! We chose Convex for multiple reasons:

– We spin up isolated projects for each user. Convex handles this seamlessly with zero manual setup, while Supabase/Firebase have limitations and manual configuration needed – We abstract backend logic as visual nodes, so Convex's modularity makes it logical to find the right granularity for workflow representation. – Everything is reactive, so UIs and workflows stay in sync without bolting on listeners – Everything is end-to-end TypeScript with transactions by default, so generated code is predictable and maintainable