Cyra

Most productivity and wellness systems were built around linear routines that ignore how women live. Traditional applications expect the same level of energy outputs everyday, and never acknowledge hormonal phases that influence focus, mood, creativity, social energy, and rest. This creates overwhelm, burnout, and guilt when women are made to feel like they don't fit the mold.

Cyra is a privacy first, productivity, and self care app built for women by women, powered by AI, that automatically synchronizes your personal and professional life with the phases of your hormonal cycle. Cyra considers your priorities, energy, creativity, focus, and rest needs throughout the month, turning your biological rhythm into a superpower that shapes how you plan, work, and care for yourself.

Our purpose is simple, to give women their freedom, clarity, and authenticity to live an optimal life.

TLDR; Frontend core React 18 + TypeScript 5.8 Vite 5 (con SWC) React Router DOM 6 UI/UX Tailwind CSS 3.4 Radix UI (componentes accesibles) Lucide React (iconos) Blockchain y Web3 Wagmi 3.0 + Viem 2.39 Soporte para Oasis Sapphire (Testnet y Mainnet) Privy 3.7 (autenticación Web3) Almacenamiento Supabase (PostgreSQL) Pinata/IPFS (almacenamiento descentralizado) localStorage (temporal) Seguridad Web Crypto API (AES-256-GCM) Encriptación end-to-end Desarrollo ESLint + TypeScript ESLint React Query (gestión de estado) React Hook Form + Zod (validación)

Cyra is built as a modern React + TypeScript web app with a privacy-first architecture designed around women’s cyclical data.

The frontend runs on React, Vite, Tailwind, Radix UI, and React Query for server-state caching. Forms are handled with React Hook,

Login is powered by Privy, which gives us simple Google, email, and Telegram authentication without exposing users to blockchain complexity. Once authenticated, sensitive cycle data is encrypted client-side using the Web Crypto API, We never store unencrypted data.

After encryption, metadata is stored in Supabase while encrypted blobs are pinned to IPFS through Pinata. This makes user information portable, censorship resistant, and fully revocable. The architecture diagram: Privy login > onboarding form > Oasis AI agent > Pinata storage / IPFS > personalized calendar

One hacky but powerful detail: we implemented hybrid storage where Supabase stores only encrypted metadata while the cycle logs themselves live on IPFS. This ensures long-term privacy and avoids vendor lock-in. Everything is fully mobile responsive and PWA-ready.