Starlight platform

The operating stack behind the services.

Starlight Lab is not only installation work. The repeatable product direction is a stack: public API edge, Starlight Bridge middleware, local Home Assistant runtime, device integrations, audit logs, and customer-specific documentation.

System shape

Cloud services stay in the cloud. Local controls stay local. The bridge is controlled.

Booking platforms, vendor APIs, and cloud services can send authorized events to a public endpoint. Starlight Bridge validates and normalizes those events. The local runtime receives only the sanitized event or command it needs.

  • Public website and marketing stay separate from API runtime.
  • API secrets belong in runtime environment variables or secret stores.
  • Home Assistant remains the owner-controlled local control surface.
  • Live automations progress from dry-run to pilot to approved rollout.
Public edgeapi.starlightlabllc.com
↓
Starlight BridgeValidate, normalize, map, log
↓
Local runtimeHome Assistant, devices, dashboards

Device fabric

A visual stack for APIs, dashboards, networks, controllers, lighting, locks, and cameras.

The platform is designed as a productized wiring diagram: cloud events at the edge, sanitized Starlight Bridge rules, local Home Assistant dashboards, and field devices that can still be manually controlled when needed.

Cloud APIsBookings • vendors • reports
Starlight BridgeValidate • map • log
Home AssistantDashboards • scenes • alerts
Locks
Cameras
WLED
Pi 5
HVAC
Network

Modules

Project work is becoming a productized operating system.

Bridge

Starlight Bridge

Webhook intake, OAuth callbacks, event normalization, room/device mapping, retries, audit logs, and safe local delivery.

HA

Home Assistant Hospitality

Dashboards for owners and staff, room status, maintenance, energy, lock visibility, camera tiles, signs, and operational alerts.

Locks

Schlage middleware

Encode-style lock planning, guest code lifecycle, staff access separation, battery/connectivity warnings, and API-gated rollout.

Light

WLED Hospitality

Exterior scenes, status lighting, event lighting, holiday schedules, occupancy cues, and Home Assistant lighting integration.

Field

TRACKTOR

Contractor time, expense, job notes, receipts, project profitability, and field-service recordkeeping as a future app lane.

Pi

Specialty controllers

Raspberry Pi hardware controls, phonebooth-style GPIO/audio workflows, kiosk-like devices, and one-off local automations.

Safety model

Production automation needs boring discipline.

A

Authorize

Use scoped API access and service accounts. Avoid broad owner passwords when API authorization is available.

B

Sanitize

Keep guest data, lock PINs, OAuth codes, tokens, and vendor secrets out of public responses, logs, dashboards, and GitHub.

C

Observe

Log what happened, which rule fired, whether the action was preview-only or live, and what operator can override.

D

Recover

Keep manual controls, vendor-app fallback, backups, documented network maps, and clean handoff notes.

What this enables

A repeatable Starlight Lab service instead of one-off scripts.

The platform direction lets Starlight Lab sell a coherent service: assessment, installation, dashboards, middleware, automation rules, logs, support boundaries, and future expansion. It can fit homes, small businesses, and hospitality properties without mixing customer secrets into the public website.

Product promise

Connect the systems that should work together, separate the systems that should not, and leave the owner with visibility instead of mystery.

See work lanes