AI plans the change; the platform owns the contract.

GoLivePilot lets an owner ask for changes in natural language, but the LLM cannot mutate arbitrary code or state. Plans are normalized into typed commands, validated server-side, audited, previewed, and only then applied to the selected variant for owner review.

Open live booking Contact

The core boundary is deliberate

Git stores site definition: pages, reviews, news, navigation, SEO, theme tokens, media manifest metadata, booking configuration, commerce catalog, locale packs, variants, releases, and restore history. SQLite stores runtime truth: appointments, blocked time, contact submissions, carts, orders, payment events, entitlements, auth, sessions, owner preferences, and audit traces.

Release safety

Preview, compare, go live, and restore without exposing raw Git.

Internally, variants are branches and releases are snapshots. Publicly, owners see product language: selected variant, preview links, changed sections, warnings, booking blockers, go-live checks, restore version controls, and a clear path from request to managed publication.

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.

Architecture facts

What is the product in one sentence?

A self-hosted AI website operating system for owner-led sites that need preview-first publishing, booking, commerce, localization, customer assistance, media, and restore-safe operations.

What prevents AI from becoming unsafe code generation?

The LLM can only request predefined typed commands. The server validates payloads, applies risk rules, records audit evidence, and refuses unsupported mutations.

Why use Git and SQLite together?

Git gives inspectable content history, variants, diff, release and restore. SQLite keeps live operational facts stable when content changes or a version is restored.

What is intentionally not in V1?

Multi-tenant SaaS hosting, arbitrary app-code generation, retail inventory, accounting, subscriptions, marketplace payouts, patient accounts, SMS, and third-party calendar sync are outside the current product boundary.