We learned by building.
Then by living with it.

We started with practical questions. What are we working on? Who owns the next step? Where did that result go? How do we pick things up again when a conversation ends?

A board, a status light, a shared page—each addition answered something we had run into. Some ideas worked immediately. Others needed several attempts. A few became clutter and had to go.

Working with agents taught us that sending a task is not the same as someone receiving it, and receiving it is not the same as finishing it. Useful collaboration needs visible ownership, context and a place to review what comes back.

Nightporch grew around those lessons. We built something, used it for real work, noticed where it got in the way, and changed it. The workspace is the result of that continuing loop—not a claim that we got everything right the first time.

The most convincing way to explain Nightporch turned out to be letting people use it. This site reuses the working board, dashboard and visual components, with a fictional team and dataset.

The demo is also a useful mirror. If a feature is confusing here, it may be confusing at home. If a widget no longer earns its place, we can retire it. Improvements should make the working installation better too.

That exploration also led beyond the browser. Porchlight is Nightporch firmware for ESP32-based devices: a small physical companion that makes selected status and updates visible without keeping the dashboard open.

It follows the same pattern as the software. Start with a useful, bounded job; try it on real hardware; make recovery possible; improve what the person using it actually sees.

Nightporch is a working private installation and an evolving product idea. It is not yet a packaged service or a one-command installation.

We want a shared workspace where people and agents can do useful work together, understand what happened, and make the next decision with enough context. We’re building towards that by using it.