SPS Architecture Knowledgebase

Where things live, how they connect, what's coming next

What this is

This is the canonical "where things live and how they connect" reference for the Sand Point Studios product portfolio. Each product has its own page covering hosting, data flow, dependencies, and current status. The Shared infrastructure page covers the cross-portfolio surfaces (Mailcow, vigil-server, Cloudflare account, Bitwarden, the multi-tenant tunnel, etc.) that show up under every product.

Living document. When infrastructure decisions land in ~/dev-context/decisions-log.md, the relevant page here gets updated. If a diagram looks out-of-date, file an issue or fix it directly — this is meant to track reality, not aspirations.

Products at a glance

Vigil Steward / Iris live

Locally-hosted personal AI OS. 297 routes, runs on vigil-server. Iris is the conversational persona.

No Wake Zone live

Cross-product helpdesk, docs hub, and admin UI. Customer portal with magic-link auth.

Agoge trio live

Educational products: Agoge Academic Advisor, UniversalGrader, LedgerLearner.

OneCut suite live

OneCut Studios LLC (50/50 Teagan/Bert). OneCut Shop + Segmented Turning.

FinishOps live

Service ops platform for the home-finishes trade. FinishOps LLC (50/50 Teagan/Dusty).

TimeKeep live

Multi-tenant SPS timekeeping with project/WBS budgets. Drives payroll via Gusto.

Wyrdlyre pre-alpha

Voice-driven AI Dungeon Master for tabletop RPGs. Lew profit-share.

HaulHard build

Driver-first trucking app. Lew + new contributors. Renamed from KingpinNav.

RightBower live

Local-multiplayer euchre, Flutter. Host Pass IAP unlock model.

EventInk build

Photo-to-calendar via AI (Android, Outlook + Google Cal). Renamed from SnapCal.

AguaAzul planned

AI-native STR platform for Mexican market. Phase 1 = single property; Phase 2 = SaaS.

How to read these pages

Each per-product page follows the same shape:

  1. What it is — one paragraph on the product's purpose and current stage.
  2. Hosting — where the code runs, what platform, what region.
  3. Data — what stores the product owns, what data it processes, who has access.
  4. Dependencies — what other SPS surfaces or third-party services it consumes.
  5. Flow diagram — Mermaid diagram of the request and data paths.
  6. Roadmap — what's owed next, with rough dates if known.

For the cross-portfolio surfaces that every product touches — Mailcow, vigil-server, the cloudflared tunnel, Cloudflare Access, Bitwarden — see Shared infrastructure.