If you are deciding
Every record, draft and change has a named person behind it, so nothing reaches your board or funder that someone on your staff has not stood behind.
If you use it daily
Your programs, your stages, your correspondence and your deadlines in one place, with the routine work generated for you.
If you are doing diligence
Separate database per agency, a single transactional write path, and an AI gateway that refuses output nobody owns. Limits stated per chapter.
Three things that are built in, not bolted on
- Governed AI
- Every AI output shows what it was given and what it guessed, and cannot be filed, sent or published until a named person owns each guess. The block is enforced by the server, not by the screen.
- Your records, your database
- Each agency has its own Postgres database, rather than a shared table with an agency column. An agency can run that database in its own cloud account, in its own region.
- One write path
- Every change is authorized, written and recorded in a single database transaction. A change that failed to record itself did not happen either.
Where to start
If you are deciding whether to buy
Read this page, then Governed AI and Security & residency. Together they answer the question a board will ask: who is accountable for what this system produces?
If you will use it every day
Start with Getting started, then Streams & engagements and Workflows & tasks. That is your first week.
If you are doing diligence
Go straight to Security & residency and Governed AI. Both state their limits plainly. The rest of the guide describes features, not controls.
What this does not do
- StreamBuild is not a general-purpose project or task manager. Tasks exist because workflows generate them.
- It does not produce board update packs or forward financial forecasts.
- It is not SOC 2 certified. SOC 2 is on the roadmap and we will say so here when it is held.