Website deployment readiness for a safe prelaunch public launch.
This page summarizes the public website launch posture for annuvera.com and www.annuvera.com. It is website-only and does not enable production financial services, persistence, analytics, cookies, tracking, provider execution, or credentials.
Planned domains
- annuvera.com
- www.annuvera.com
Future subdomains
- app.annuvera.com
- api.annuvera.com
- docs.annuvera.com
- support.annuvera.com
- status.annuvera.com
Safe public launch checks for the prelaunch website.
Static website build
Next.js public website renders as static-first pages without backend persistence, authentication, cookies, analytics, or tracking.
Legal publication pages
Privacy, Terms, Account Deletion, Support, and Contact pages are present as prelaunch drafts pending qualified counsel review.
SEO discovery files
Sitemap, robots, metadata helpers, canonical paths, and structured data are present for public discovery.
Beta waitlist safe mode
Consumer, merchant, and partner/API waitlist intake remains frontend-only and does not create accounts or persist records.
Developer waitlist safe mode
Developer interest intake remains frontend-only and does not issue API keys, create accounts, publish SDKs, or call external services.
Production financial processing
The website does not perform payment processing, KYC processing, provider execution, ledger writes, balance writes, or production financial activity.
Domain and DNS launch
annuvera.com and www.annuvera.com deployment wiring remains a future hosting and DNS configuration task.
Launch checks before connecting public domains.
Static website readiness
The website is built as a static-first Next.js public surface with product marketing pages, app readiness pages, developer pages, SEO files, structured data, and publication-ready content.
Legal pages present
Privacy, Terms, Account Deletion, Support, and Contact pages are present as prelaunch drafts. They should be reviewed by qualified legal counsel before production launch or regulated activity.
Beta and developer waitlist safe mode
Waitlist experiences are frontend-only placeholders. They do not persist records, send email, create financial accounts, create developer accounts, issue API keys, or call external services.
No sensitive data collection
Public forms warn users not to submit sensitive financial, banking, card, identity, KYC, provider credential, API key, production secret, or government ID information.
No production financial processing
The public website does not execute payments, KYC, provider calls, ledger writes, balance writes, settlement, treasury, FX, reconciliation, or live financial workflows.
No analytics or cookies yet
No analytics, cookies, tracking pixels, external services, or third-party data collection scripts are added in this phase.
Future launch checklist
- Select deployment target and confirm static Next.js support.
- Connect annuvera.com and www.annuvera.com through DNS after hosting target selection.
- Verify /, /beta, /app, /developers, /privacy, /terms, /sitemap.xml, and /robots.txt after deployment.
- Complete legal counsel review for publication pages before production financial activity.
- Confirm no production credentials, provider credentials, API keys, tracking scripts, or analytics are added before launch.
- Keep beta and developer intake frontend-only until approved intake infrastructure exists.
Review the key public launch surfaces.
Beta Waitlist
Frontend-only beta interest intake with prelaunch safety warnings.
Developer Platform
Developer ecosystem pages for future API, sandbox, docs, and SDK readiness.
Support Center
Prelaunch support paths for beta, merchant, partner/API, privacy, security, and app readiness questions.