About

What this is

Vectorbea Engineering is a public engineering blog written by the team building Vectorbea, a durable, long-running visual agentic workflow builder. Vectorbea itself is a private product. This blog is where we write about the engineering decisions, tradeoffs, and mistakes behind it, in the kind of detail we'd want to read ourselves.

We write about durable execution, checkpointing, retries and resume, event history, human approval gates, BYOK key management, worker orchestration over Redis Streams, cost budgets, rate limits, and the occasional retrospective on what we got wrong.

About the author

Susmit Banerjee

Backend Engineer, Vectorbea

Susmit Banerjee is a backend engineer with 9+ years building distributed systems in Java and Kotlin. At Vectorbea, Susmit works on the execution engine, worker orchestration, and event history: the durability layer that the rest of the product sits on top of.

Why we write this

Most of what we learn building Vectorbea comes from reading other teams' write-ups about systems they've shipped: the honest ones, with the parts that didn't work included. This is our attempt to return the favor. We try to be specific about what we built, why, and what we'd do differently, without overselling the scale we're operating at. We're a small team; these are notes from the trenches, not claims of having solved distributed systems.

Get in touch

Find us on GitHub and LinkedIn, or subscribe via RSS. For the product itself, visit vectorbea.com.