Symbious™ · operational memory for the built environment

Run a pilot

A few nodes. One zone. Ninety days. The record is yours.

A pilot is the smallest honest test of whether a building can remember itself. We place a handful of passive nodes at the thresholds that matter, the people who pass them tap them in the course of the work, and at the end you hold a witnessed, tamper-evident record you own — and can walk away with. No wiring, no cameras, no lock-in.

01

What a pilot is

Not a deployment, not a purchase — a scoped test. One zone of one building, a small set of nodes, ninety days of accumulating memory. Enough to see the memory accumulate and the dashboard begin to fill; small enough to start next week and stop whenever you like. It runs on the phones people already carry and the surfaces already in place.

02

How it works

1
Choose a zone

One area, a short list of thresholds that matter — cleaning, plant, a safety check.

2
We ship the kit

Peel-and-stick nodes and a one-page setup. No installer, no wiring.

3
The threshold is tapped

Whoever is at the threshold confirms its state in the moment. No app, no login — a web page opens.

4
You read the memory

A witnessed, tamper-evident record and a dashboard that starts to explain itself.

03

Who it's for

Any building with thresholds a person still judges, where enough people pass that the record is of the place rather than of one person — from the drawing board to twenty years in service.

Buildings
  • Hotels & hospitality
  • Malls & multi-tenant
  • Events & venues
  • Offices & towers
  • Hospitals — estates & facilities
Networks & makers
  • Franchises & QSR
  • Restaurants & bars
  • Craft & provenance (DPP)
  • Facilities & estates
  • Owners & operators

Not sure your case fits? Read the illustrative studies first — then bring the one closest to yours.

04

The commitment

Small & fixed
  • One zone, ninety days
  • A handful of nodes
  • No wiring, cameras or IT project
  • Stop any time — no lock-in
Yours to keep
  • Owner-sovereign record
  • Portable if you change operator
  • Exports to the systems you run
  • Deleted on request
05

The assurance

Events, not people

A pilot records that a threshold was confirmed — by a role, at a time — never who did it, and never their movement through the day. No camera, no presence-tracking, no profile. The record holds no name, no account and no device, because the schema has no field for them. It is held by you and the building, and this is not a setting we can change later — it is fixed in the Concordat, published to the public domain.

Where that protection is strong, and where it is not

Anonymity is a property of the threshold, not only of the schema. Where many people pass, the absence of an identifier is decisive. Where one person covers one threshold alone, the record is indexed on the object or the place — a lift's own history, a product's own provenance — rather than on a person's shift. Where even that is not possible, the protection is a commitment rather than a physical impossibility, and we will say so plainly. We would rather scope a pilot honestly than record more than a threshold can safely hold.

06

Request a pilot

A few details and we'll be in touch. Nothing binding — a conversation.

Stage
Type
Prove first
Symbious™ · operational memory for the built environment
DWNTWN Global Pte Ltd · UEN 202608530M · symbious.io · ping@symbious.io