Captain Landseed
Operational mission-control for Landseed's field deployments.
Origin
Landseed deploys continuous sensors on conserved land — remote, often off-grid, often across multiple jurisdictions. Each site has a status, a maintenance window, an upstream agreement, a deed, an owner, a contact, a power source, a connectivity story. Without a control plane you spend the first hour of every site visit reconstructing what is there.
Problem
A field operator on bad cellular needs to know, in five seconds: which sensor is offline, when it last reported, whether anyone has been dispatched, what the agreement says about access. The vendor consoles are not built for that.
Approach
A single internal console: sites, sensors, deployments, agreements, alerts. Built so a non-engineer in the field can read it on a phone with bad signal — no JS framework boot, no client-side hydration, server-rendered HTML, sub-second TTFB.
Methodology
Edge-rendered. The console runs on Cloudflare Workers; data lives in Postgres at the edge replica. Auth is a passkey. The mobile experience is built first; the desktop view is the same HTML wider.
Selected milestones
- In active use across Landseed's deployment surface
Ask me about
- What a 'site' actually contains in a Landseed deployment
- Why edge-rendered HTML over a client-side dashboard
- How the agreement layer connects to the sensor layer