Real desktop pet preview
The first screen uses existing loops and contact sheets so visitors see what Pawktopia already produces.
AI desktop pet companion
Turn a real pet's look, motion loops, and small moments of company into a companion that lives on your desktop.
Windows desktop comes first. The website handles discovery, entry, and downloads.
Real video-loop bundle preview: Zorro idle
V1 website focus
The first screen uses existing loops and contact sheets so visitors see what Pawktopia already produces.
Chinese, English, and Japanese share one page structure, with every visible string coming from locale dictionaries.
Download, waitlist, and FAQ flows stay usable on phones without relying on a wide desktop canvas.
Pages hosts the site, Functions handle lightweight site APIs, and R2/KV/D1 stay in focused roles.
User path
Visitors first see real previews, product boundaries, and the desktop-first positioning.
The waitlist writes to D1 and can later connect to account and download flows.
Login, pets, uploads, generation, review, and bundle downloads remain owned by the .NET API and SQL Server.
R2 and signed URLs can distribute installers, public demos, and user bundles.
Product media
The Zorro walk loop and Ningao fixed scene come from existing desktop bundles.
Deployment call
Hosts the multilingual site, previews, and static frontend output.
Handles /api/site/*, such as health checks, waitlist capture, and future safe proxy routes.
R2 stores large media and installers, KV stores non-critical config, and D1 stores only lightweight site data.
Remains the source of truth for auth, pets, generation jobs, review, and bundle delivery.
Product entry
Leave an email and a note. The site writes the request to Cloudflare D1 while product accounts stay with the backend.
FAQ
Not for this version. Cloudflare is a strong fit for the site, site APIs, and media delivery; the current generation state machine, SQL Server model, and IIS/.NET API should stay in place.
No. In V1, D1 stores only waitlist, feedback, and lightweight site data, so strong product workflows remain together.
No. Mobile first means the website is readable and useful on phones. The desktop companion experience still targets Windows first.