Canonical site URL
Canonical URL points at boetica.ai.
Status
Status separates the public site from the application plane.
Boetica publishes marketing-site readiness separately from application runtime status so buyers can see what is verified, what is blocked, and what proof is still pending.
Site readiness
Public-site gates need attention.
This is the same non-secret gate exposed at /api/readiness. It checks DNS, mail, lead durability, notification routing, and operator attestations.
blocked
2
Blockers
0
Warnings
12
Passing
Pass
Durable lead backup
Lead backup is configured through Vercel Blob.
Attio lead routing
Attio person/note/list routing is configured.
Lead email delivery
Lead notification email is configured through ses.
Branded sender domain
Lead notifications send from a boetica.ai domain.
Operator mailboxes verified
Set LAUNCH_MAILBOXES_VERIFIED=true only after security@, privacy@, legal@, and lead notification inboxes are monitored.
Brand/legal cleared
Set BRAND_LEGAL_CLEARED=true only after the final brand/legal review is complete.
Apex domain
boetica.ai resolves to Vercel.
www domain
www.boetica.ai resolves to Vercel.
Mailbox MX records
3 MX record(s) found.
SPF record
SPF record found.
Mail DKIM records
3 DKIM host(s) resolve.
DMARC record
DMARC record found.
CAA record
1 CAA record(s) found.
Marketing site
Static public site hosted separately from the Boetica application plane. Marketing-site incidents should be reported through security@boetica.ai when they affect security or privacy.
Application
Product runtime status, incident history, and platform-access readiness publish only from verified hosted workflow telemetry.
What will be tracked
The first product status feed should cover GitHub integration, sandbox execution, CI ingestion, lead intake, evidence export, and notification delivery.
Publication rule
A blocked readiness state is intentional until the outside-the-code gates are real. Boetica should not hide missing mail, backup, or legal proof behind marketing language.
Incident standard
Material incidents should include timeline, customer impact, mitigation, follow-up owner, and evidence of closure.