Tigris Systems · demo lab
Patterns held here until they materialise.
The Tigris demo lab. Each pattern is a demo, an experiment or a piece of new technology, held in the buffer with the same identity, access and data path as a production Tigris service, until it graduates into a service of its own or is handed to another company.
2 patterns in the buffer · sign in to open one
Open the showcasePresenter mode: the ring, the materialise beat, the stage. Not the day-to-day console.
Demofire-watch
Fire hazard detection across the network
Fire Watch
A satellite hotspot lands in the shared graph; the Connection Index decides which organisations it reaches; each is scored in its own private graph. One pass, several companies alerted, none of them learning the others subscribe.
- Heading to
- Insert into a Tigris service · FireWatchConsoleManager
- Streams
- fire.detections, fire.incidents, fire.exposure, fire.risk, fire.world, fire.merged, fire.merged.published
- Roles
- admin, operator, viewer, compliance, partner
- Since
- 2026-09-19
Demolive-stream-tile
Live stream tile
One tile, one org-scoped stream, delivered over Server-Sent Events with replay on reconnect. The smallest thing that proves identity, entitlement and the data path end to end — every new pattern starts by copying this one.
- Heading to
- Insert into a Tigris service · SporeDrive
- Streams
- lab.pulse, lab.build, lab.attention
- Roles
- admin, operator, viewer, compliance, partner
- Since
- 2026-09-19
Identity
Keycloak, authorisation code + PKCE, server-side. Roles from the realm; the lab only reads them.
Data
Org-scoped streams org:{org}:stream:* over the Bus, filtered on delivery, Server-Sent Events to the browser.
Service
PatternBufferManager · port 8220 · profile infra · /info
