Operating model

What an operator or investor can inspect after the public demo.

This page replaces generic office copy with the operating facts that matter: local deployment topology, provider keys, release checks, backup boundaries, observability, and current V1 operating boundaries.

Deployment and ownership

The stack is designed for a single service business or agency-managed client: FastAPI control plane, Next.js public/admin apps, Caddy, Git site repository, SQLite runtime database, media store, and provider-backed LLM/STT/vision/image/video services.

Operational safety

The demo should survive scrutiny beyond the first page.

Investor review should include public routes, localized routes, booking creation, catalog product pages, owner chat typed plans, media readback, order/payment visibility, release history, restore behavior, and split backup evidence.

From owner workspace to public proof

A public product site that stays truthful across variants, locales, and runtime operations.

This surface is rendered from the same Git-backed pages, booking config, reviews, and SEO state that the owner can preview and release.

Localized navigation and slugs stay truthful across routes.
Runtime-backed bookings and submissions stay intact behind publish and restore.

Ready to inspect the cockpit?

Use the admin workspace after reviewing this public site. The strongest proof is the handoff from public content to typed owner operations and runtime evidence.

Visitors see a polished public surface while variants, locales, booking rules, and runtime data remain truthful underneath.