By invitation · Limited early access
Run every business you own from one login. Each is sealed from the others, and each team sees only its stream.
Try it here. Switch person in the panel and watch the book change.
| Business / stream | Records | Access |
|---|---|---|
| Real estate agency | ||
| Leasing | 1,482 | Visible |
| Sales | Sealed | |
| Events company | ||
| Sponsorship | Sealed | |
StreamsSalesLeasingSponsorshipIllustrative workspace
A sponsorship rep never sees a tenancy renewal. A leasing agent never browses the sales book. Neither knows the other business exists.
Home opens on what is incomplete, counted, and linked to the exact records it counted. Not a wall of charts reading zero.
Work queue · Tasks · Automations · Pipelines & stages · Meeting notes · Calendar feeds
Thousands of records, and the depth to actually work them: what a unit sold for, what similar ones went for, and where it is on a map.
Custom objects · Filters & facets · Map · Record panel · Transaction history · Comparables · Spreadsheet import · Search
The part most CRMs leave to convention. Here it is enforced per row by the database, and an agent's claim on a record lapses if they stop working it.
Ownership claims · Concealed fields · Documents · Field history
Product surfaces shown with illustrative records
“They can't see it” is easy to say and easy to get wrong. Here the boundary is enforced by the database on every single read, so it holds even for someone talking to the API directly.
Row-level security on every table. Not a filter the application adds, and not something a bad query can step around.
Concealed fields are gated separately, so opening the record and seeing the phone number are two different permissions.
An invite is bound to one stream from the moment it is accepted, and there is no public sign-up to work around.
A business can require a second factor. When it does, a session holding only a password sees nothing, even through the API.
-- runs on every read, for everyone, including the API
create policy rc_select on records
for select using (
internal.is_member(workspace_id)
and internal.can_see_stream(stream_id)
);
-- a leasing agent asks for the sales book:
select count(*) from records where stream = 'sales';
-- 0 rows. Refused by the database, not the app.Every claim above is set out in full, gaps included, on the trust page. It is written to be checked rather than believed.
Most CRMs bill per workspace, so a second company means a second subscription. Streams bills per seat, and a person in three of your businesses is still one seat.
3
10
$1,470
A separate subscription for each of your 3 companies, every month.
$490
$980 a month less, and one login instead of 3.
The comparison figure is illustrative, modelled on Pipedrive Professional's published per-seat list price. Streams is billed per seat, per month, annually.
The full model: every business you run, sealed, in one account.
For owners working the book themselves.
$29 · AED 107per seat / month
For teams that want the machine to do the remembering.
Automations, concealed fields, enforced two-factor, audit.
$49 · AED 180per seat / month
Custom terms, invoicing, and a direct line rather than a ticket queue.
For groups running many businesses and teams.
Every place starts with a 14-day trial. AED shown at the dirham peg; fair-use limits per tier apply. Prices per seat, per month, billed annually.
Streams is new, and we open it a few businesses at a time so early workspaces get real attention while the product hardens. Every request gets a reply from a person.
No. Every read is checked by the database against who is asking. A leasing agent cannot open the sales book, and nobody in your events company can tell the agency exists.
Nothing. Pricing is per seat, not per company. Your second and third businesses living in the same account is the entire point.
It is yours. We hand you a full export and delete what we hold on request. You can also delete an entire business yourself, from its own settings.
Yes. Import from a spreadsheet, map your columns onto your own objects and fields, and re-uploading the same file never duplicates a record.
A single company with one team and one pipeline. You would be paying for separation you do not need.
Streams is new, and we're letting businesses in deliberately so early workspaces get real attention while the product hardens. Request access, tell us what you run, and we reply personally as places open.
A few minutes, no payment details.
© 2026 Streams