tissue Sense — coming soon

Your sensors,
on Tissue.

From a $5 microcontroller to an industrial gateway — connect any device, store every reading, build a dashboard you can share, and route alerts through a pipeline you control — to a phone, a team, or any system you run — when something goes wrong. Built on the same Cells you already deploy, with two new pieces: synapse and ganglion.


synapse sensor ingest
The doorway for your devices.

synapse terminates MQTT, CoAP, and HTTPS at the edge, authenticates every device, and turns each reading into an event your Cell handles — write it to c3, check a threshold, raise an alert that routes and escalates. The millions of cheap, sleepy device connections are held outside your Cell, so your code stays simple and stateless. You write one new handler: sensor(event, env) — a sibling to fetch and pulse.

  • Speaks MQTT, MQTT-over-WebSocket, CoAP/DTLS, and plain HTTPS — bring hardware you already own (Tasmota, ESPHome, LoRa, cellular).
  • Battery-friendly. CoAP over DTLS and session resumption for nodes that wake, report, and sleep for months on a coin cell.
  • Secure by default. Per-device credentials; a device can only write its own stream — never another's.
  • Live dashboards. Browsers subscribe over wss and watch readings tick in real time.
ganglion edge gateway
Tissue, inside your building.

Install ganglion on a Raspberry Pi and it runs the same Cell as the cloud — ingest, dashboard, and alerts, all on-site. The internet can drop and your greenhouse still shows live temperature and still sounds a local alarm; when the uplink returns, buffered readings sync up. Your data never has to leave the building. It's software you install on hardware you own — not another box to buy.

  • Bridges non-IP sensors. LoRa, Zigbee, BLE, Modbus — devices that can't reach the cloud talk to ganglion on your LAN.
  • Offline-complete, not offline-degraded. Buffers locally during an outage, forwards when connectivity returns. No data lost.
  • Deploy to the field. ribo deploy pushes new logic to the gateway; roll back in seconds. Your gateway is a Cell, not firmware.
  • Sovereign by default. Ingest, store, and alert entirely on hardware you control — nothing crosses to a vendor cloud.
// synapse joins the platform primitives
Cells
compute
JS, Rust, or Python in a V8 isolate. Your sensor() handler lives here.
c3
sql
SQLite-backed SQL. Every reading, queryable, with rollups and retention.
g7
storage
S3-compatible objects — images, snapshots, exported series.
pulse
scheduler
Cron rollups and the offline dead-man's-switch alert.
synapsesoon
ingest
MQTT / CoAP / HTTPS in, a sensor event out. Devices on, code simple.

When something's wrong,
the right people know.

An alert is more than a buzz in your pocket. A rules engine watches every stream — high and low thresholds, sudden swings, and the case that matters most: a sensor that's gone silent. When a rule trips, it moves through a pipeline you control — notify one phone or a whole team, send SMS or email, fire a webhook into Slack, PagerDuty, or your own systems, and escalate up an on-call list until someone acknowledges. The alert logic is your Cell, so it can reach anything that speaks HTTP — the buzz on your phone is just the last hop. The 3am cooler failure, the greenhouse frost, the freezer whose sensor quietly died: caught, routed, and escalated — not just shown on a screen.

  • Greenhouse — frost & heat alerts for small farms
  • Cold-chain — cooler & freezer monitoring, dead-sensor detection
  • Workshop / home — temperature, humidity, door state
  • Industrial — Modbus & LoRa on a gateway you own