Glowscape
One dashboard for every home and office you run, controlled by talking to Claude.
The problem
Every smart-home platform assumes one home, one hub, one network.
The moment you run more than one place, a house and an office, a beach house, a studio, that model breaks. Each site has its own router, its own devices, and its own app, and none of them know the others exist. You end up with a drawer of vendor hubs and five apps that each see a fifth of your world. Managing lights, shades, thermostats, and networks across locations turns into a full-time chore.
What it does
one login, every siteA cheap Linux board runs each site.
Drop a $40 NanoPi or Firefly board on the network and it auto-discovers what's there: Lutron Caseta, RYSE shades, Flic buttons, TP-Link Deco routers, Ecobee thermostats. No proprietary hub, no cloud round-trip for local control.
Every site in a single place.
Brooklyn, the beach house, and the office all live in one view. Build a scene once and map it to a physical Flic button, so "movie night" is one press at the site and one sentence from anywhere.
103 MCP tools. Talk to Claude.
Control any device at any site through Claude: control_device, activate_scene, list_bases, and a hundred more. "Turn off all the lights at the beach house" resolves the site, fans the command out, and reports back.
It updates itself, over the air.
Bridges pull signed releases over their own WebSocket, verify a SHA256, swap the tree atomically, and roll back if startup fails. No SSH, no VPN. A cross-site Tailscale mesh and a .base DNS zone let every site reach every other.
One sentence in, six lights out
How it's built
Cheap ARM boards at the edge, one boring cloud in the middle.
Each site runs a small Python daemon on an ARM board, a NanoPi or a Firefly, the kind you buy for the price of a nice dinner. It owns the local Lutron, RYSE, Flic, Deco, and Ecobee hardware and holds one persistent WebSocket up to a FastAPI cloud on Fly.io. Releases push themselves out over that same socket: the bridge verifies a checksum, swaps the tree atomically, and if the new version fails to boot, systemd rolls it back on its own. No SSH, no field visit. It has run this way across three real sites for months, behind 1,469 tests.
This is what six weeks looks like
We built Glowscape for ourselves. We can build yours.
Every product in our labs was designed and shipped by the same two-person team that would build your MVP. If you have an idea worth building, that's the whole pitch.
Start a build →