Evidence per release
Production deployment
The platform has a Vercel deployment path and commercial-route smoke checks. Current readiness requires a passing artifact bound to the exact deployment and commit under review.
Commercial status
Free company workspace first. Paid enterprise through sales.
Companies can publish products, Agent Skills, and perks for free with a work email. Private data, attribution, exports, and governed workflows are provisioned manually after a sales call and signed agreement; there is no pricing page or self-checkout. This page defines evidence expectations and does not certify a specific deployment.
- Release
- Per deploy
- verify the exact commit and deployment
- Data
- Controls
- runtime isolation evidence required per release
- Procurement
- Contract
- legal and support terms finalized with the buyer
Evidence state
Launch requirements by surface
These surfaces and controls are implemented, but this static page is not deployment evidence. Current availability and runtime behavior require an exact-release artifact; items marked contract also require account-specific agreement.
Control implemented
Production data boundary
Tenant-aware access controls and server-side key boundaries are implemented. A rollout still requires current migration, authorization, and cross-tenant denial evidence.
Result required
Security advisor
Advisor review is a release check. No current Supabase advisor result is published on this page; request the dated result used for the deployment under review.
Implemented
Buyer path
Free company signup, enterprise sales, ROI, trust, security, packet, and evidence routes are implemented and clearly separated. Availability is verified per deployment.
Gate defined
Verification
Build, lint, release checks, enterprise tests, migration receipts, and production verification are defined in the launch gate; a current claim requires the resulting release-bound artifacts.
Contract
Support path
Enterprise support and SLA terms are described for procurement and should be finalized in the signed order form.
Enterprise flow
From lead to annual contract
- 1
Lead capture
Buyer submits quote or sales form with a work email and commercial context.
- 2
Procurement packet
Sales shares trust, security, data processing, commercial packaging, ROI, and onboarding materials.
- 3
Paid enterprise setup
After the sales call and agreement, the team provisions paid access and confirms data sources, success metrics, readout cadence, and support owners.
- 4
Annual close
Signed agreement finalizes DPA, MSA, SLA, order form, security commitments, and rollout scope.
Commercial handoff
What gets finalized with sales
The public site shows control scope and evidence requirements, not current deployment certification. Customer-specific legal, security, support, and data commitments are finalized in the sales and procurement workflow.
- DPA, MSA, order form, SLA, and privacy terms are finalized per customer during procurement.
- Named support contacts, incident contacts, escalation owners, and customer success owners are assigned at kickoff.
- Buyer-specific security questionnaires are answered through sales and security review.
- Data residency, retention, deletion, export, and subprocessor terms are confirmed in the contract packet.
- Production verification, rollback notes, and launch owners are reviewed before each enterprise rollout.
- Environment variables and service-role keys must remain server-side; rotation evidence is reviewed for each enterprise rollout.
Security posture
Review access, RLS, secrets, incident response, and data controls.
Data processing
Review public and private data boundaries before a DPA review.
Commercial scope
Use the sales call to scope paid access, the contract, manual provisioning, and invoicing.
This is a readiness checklist, not a live status monitor or release certificate. Ask for evidence tied to the exact deployment under review. Contractual status notifications, uptime commitments, and incident notice terms belong in the signed SLA.
Use this page as the readiness checklist.
It shows implemented scope, required release evidence, contract-controlled items, and where buyer-specific commitments must be confirmed before manual paid enablement.