We're building tissue Sense — a way to point any sensor at Tissue and get a live dashboard, stored history, and a full alerting pipeline — routed and escalated to wherever it needs to go — without standing up a single server.
Tissue already gives you compute (Cells), SQL (c3), object storage (g7), and scheduling (pulse). The piece missing for the physical world was a front door for devices and a way to run close to them. That's what we're adding, and it's two new pieces with names that fit the rest of the platform: synapse and ganglion.
synapse is the ingest layer. It speaks the protocols real hardware already
uses — MQTT, MQTT-over-WebSocket, CoAP over DTLS for battery devices, and plain HTTPS — and
turns every reading into an event your Cell handles in a new sensor(event, env)
handler, right alongside fetch and pulse. Each device gets its own
credential and can only write its own stream. The connections live outside your Cell, so your
code stays as simple as the rest of Tissue.
The practical upshot: a $5 microcontroller with a temperature sensor, a Tasmota plug you already own, or a battery LoRa node in a field can all report to the same place — and a browser can watch the numbers tick in real time.
ganglion is software you install on a Raspberry Pi (or any small Linux box) that runs the same Cell as the cloud — right there in your building. It bridges sensors that can't reach the internet on their own (LoRa, Zigbee, BLE, Modbus), and it keeps working when the internet doesn't: ingest, dashboard, and alerts all run on-site, and buffered readings sync up when the uplink returns.
Because the gateway runs the same Cell, your sensor data can be ingested, stored, charted, and alerted on entirely inside your own walls — the cloud becomes optional, for remote access, not a requirement to function.
A reading crossing a line is just the trigger. Because the alert logic is your Cell, what happens next is a pipeline you control: a rules engine watches for thresholds, sudden swings, and the case that matters most — a sensor that has gone silent — then routes the alert wherever it needs to go. Push it to a phone, text a teammate, email a list, fire a webhook into Slack or PagerDuty, or escalate up an on-call rotation until someone acknowledges. The notification on your phone is one delivery channel, not the whole system.
| You are | What you get |
|---|---|
| A tinkerer | Flash a board in your browser, scan a code, see your sensor on a shareable page in minutes — free. |
| A small farmer | Greenhouse and cooler alerts that reach your phone, your family, or your staff — including when a sensor goes silent, the case that matters most. |
| An operator | Private dashboards, embeddable charts, and alerts that escalate. Public or private with one tap. |
| Industrial | A gateway you own, Modbus and LoRa on-site, and data that never leaves the building. |
Most sensor platforms make you rent three black boxes — their ingest pipeline, their locked dashboard widgets, their rules UI — none of which you can move. On Tissue, the Cell that ingests the reading is the same Cell that renders the dashboard and runs the alert: one unit you own, that you can fork, and that runs in our cloud or on a Pi in your greenhouse. Dashboards are real web pages, so sharing and embedding them is native, not a paywalled tier.
synapse and ganglion are in active development. We're opening early access soon — if you want to be first to point a sensor at Tissue, sign up and keep an eye on this blog. We'll post again the day it's live.