Canonical site URL
Canonical URL points at olydi.com.
Status
Status starts when the hosted product is live.
OLYDI does not publish uptime history before the hosted app is available to design partners. This page separates the public marketing site from the future product runtime so launch materials do not imply operational proof that does not exist yet.
Launch readiness
Launch gates are still blocked.
This is the same non-secret gate exposed at /api/launch-readiness. It checks DNS, mail, lead durability, notification routing, and manual launch attestations.
blocked
1
Blockers
0
Warnings
20
Passing
Pass
Durable lead backup
Lead backup is configured through Vercel Blob.
Attio lead routing
Attio person/note/list routing is configured.
Keystatic GitHub storage env
Keystatic GitHub storage credentials are configured.
Lead email delivery
Lead notification email is configured through resend.
Branded sender domain
Lead notifications send from a olydi.com domain.
GitHub App install path
GitHub App install path is live and reachable.
CLI install path
CLI install path is live and reachable.
GitHub Action install path
GitHub Action install path is live and reachable.
Launch mailboxes verified
security@, privacy@, legal@, and lead notification inboxes are operator-verified.
Brand/legal cleared
Set BRAND_LEGAL_CLEARED=true only after the final brand/legal launch review is complete.
Apex domain
olydi.com resolves to Vercel.
www domain
www.olydi.com resolves to Vercel.
olydi.ai 301 redirect
olydi.ai resolves to Vercel for a 301 to olydi.com.
olydi.dev 301 redirect
olydi.dev resolves to Vercel for a 301 to olydi.com.
olydi.io 301 redirect
olydi.io resolves to Vercel for a 301 to olydi.com.
Mailbox MX records
1 MX record(s) found.
SPF record
SPF record found.
Mail DKIM records
1 DKIM host(s) resolve.
DMARC record
DMARC record found.
CAA record
2 CAA record(s) found.
Marketing site
Static public site hosted separately from the OLYDI application plane. Marketing-site incidents should be reported through security@olydi.com when they affect security or privacy.
Application
Product runtime status, incident history, and design-partner readiness will publish only after the hosted workflow is available.
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. OLYDI should not hide missing mail, backup, or legal proof behind launch language.
Incident standard
Material incidents should include timeline, customer impact, mitigation, follow-up owner, and evidence of closure.