I didn't want the workflow by Muhammad UnainI didn't want the workflow by Muhammad Unain

I didn't want the workflow

Muhammad Unain

Muhammad Unain

I didn't want the workflow canvas to feel like a single-user tool.
So I made it collaborative.
SeerForge is a multi-tenant AI workflow builder, so multiple people can work inside the same workspace.
And that's where things started getting interesting.
How do you keep everyone's canvas in sync?
How do you show another user's cursor in real time?
What happens when two people change the workflow at the same time?
And how do you keep everything responsive without making a database request for every little thing?
The canvas itself wasn't the hardest part.
Most of the interesting work was happening behind it:
→ real-time state → events → persistence → database calls → keeping everything in sync
It's one of those features that looks pretty simple when you're using it.
But once you start building it, you realize there's a lot happening underneath.
Still working on SeerForge, but the collaboration layer has been one of the more interesting parts to build so far.
Like this project

Posted Oct 20, 2026

I didn't want the workflow canvas to feel like a single-user tool. So I made it collaborative. SeerForge is a multi-tenant AI workflow builder, so multiple p...