Production deployment
The root production app is deployed on Vercel and commercial buyer routes are verified through the production smoke script.

Preparing tokens&
Loading the next builder or enterprise surface.
Loading
Preparing page
Loading product graph, proof, and adoption context.
LoadingThis status page is the launch-readiness overview for enterprise buyers and the internal team. It separates what is live in production from contract-specific work that must be completed before a signed enterprise rollout.
Current state
The app can support sales conversations and paid pilots now. The items marked contract still need account-specific agreement before a large enterprise signature.
The root production app is deployed on Vercel and commercial buyer routes are verified through the production smoke script.
Enterprise data lives in the enterprise schema inside the single directory production Supabase project; the duplicate project was removed.
The Supabase security advisor reports no security lints after the latest RLS and schema hardening work.
Quote, pricing, ROI, trust, security, packet, and status routes now exist as real pages rather than dead routes.
Build, lint, release checks, enterprise tests, migration docs, and production verification are part of the launch gate.
Enterprise support and SLA terms are described for procurement and should be finalized in the signed order form.
Enterprise flow
Buyer submits quote or sales form with a work email and commercial context.
Sales shares trust, security, data processing, commercial packaging, ROI, and onboarding materials.
Team defines data sources, success metrics, weekly readout cadence, and support owners.
Signed agreement finalizes DPA, MSA, SLA, order form, security commitments, and rollout scope.
Commercial handoff
The public site shows platform readiness. Customer-specific legal, security, support, and data commitments are finalized in the sales and procurement workflow.
Review access, RLS, secrets, incident response, and data controls.
Review public and private data boundaries before a DPA review.
Use paid pilot, growth, and enterprise packages to scope the deal.
This is a readiness page, not a third-party status monitor. Contractual status notifications, uptime commitments, and incident notice terms belong in the signed SLA.
It lets the team say what is ready now, what is contract-controlled, and what should not be overclaimed.