Why SARB
In Arabic, سرب (sarb) is a flock of birds flying in one formation: no bird flies alone — each holds its place, the effort is shared, and the flock arrives together. SARB is work automation built on that picture: agents moving in formation, for your team — simple, secure, and auditable.
Built on three decisions
Every design choice in SARB follows from three decisions we made early and hold everywhere:
- Expressions are a closed language, not JavaScript. Every dynamic value in an agent is written in a small, fully specified expression language. There is no eval and no JS engine — a spec can be read and audited line by line, and text arriving from the outside can never become code.
- Code runs in a permissionless sandbox. When you need real code, a code step runs out-of-process in a Deno sandbox with no network, no filesystem, and no environment access. It computes over its inputs and returns a value — nothing else.
- Nothing is ever guessed. The n8n migrator converts what it can convert deterministically; anything it cannot convert safely is carried verbatim and flagged for your review — never silently approximated.
Durable by construction
Every run is a finite state machine persisted in Postgres. The set of states is closed, exactly one code path may change a state, and every transition appends one row to an append-only event log — so a run's history is complete and replayable.
If a worker crashes mid-step, its lease expires and the step is reclaimed and retried. Publishing a new version never changes a run already in flight — runs pin the version they started with.
Secure by default
- Credentials are encrypted at rest (AES-256-GCM) and never returned by the API — not in responses, not in logs, not in run events.
- Outbound HTTP from agents is SSRF-guarded: loopback, private, and link-local addresses are blocked on the resolved IP.
- Role-based access with per-resource visibility (private / shared with groups / whole tenant), and a publish-time check that an agent may only use credentials its publisher can use.
- Every security-relevant action lands in an append-only audit log — actor, action, IP — with secrets excluded by construction.
Built for teams
Agents and credentials are shared deliberately, not by default. Human-in-the-loop steps pause a run until someone approves. Studio speaks Arabic and English, right-to-left included, and teammates join by invitation — no shared passwords.