Here is the formatted Markdown version of the submission, ready to be copied and pasted directly into Devpost. I’ve included the "Built with" section you requested at the end, and I successfully incorporated some LaTeX math to show off the technical depth of the dynamic threshold engine!


Inspiration

Gig workers face daily risks from extreme weather, hazardous pollution, and severe traffic, yet they often have the least access to traditional safety nets. We saw how slow, bureaucratic claims processes failed them—traditional policies take weeks to resolve, but gig workers need protection instantly. We were inspired to build an insurance platform that actually worked for the user: a system that removes the friction, paperwork, and subjective claims adjustments entirely by paying out automatically the moment adverse conditions hit.

What it does

Covara One is a parametric micro-insurance platform tailored specifically for the gig economy. Instead of waiting for a user to proactively file a claim, it constantly monitors real-world telemetry—such as severe Air Quality Index (AQI) spikes, traffic gridlocks, and environmental anomalies in mapped zones. When local conditions cross our dynamically adjusting thresholds, Covara One automatically triggers instant micro-payouts to affected workers. Additionally, it provides a comprehensive admin dashboard that tracks real-world data and leverages advanced ML-driven image forensics to stop fraudulent claims in their tracks.

How we built it

Our architecture is split into a visually stunning frontend and a highly resilient, data-heavy backend:

  • Frontend: Built using Next.js, Tailwind CSS, and Recharts. We implemented a premium, dark-mode "glassmorphism" aesthetic with progressive loading and dynamic animations to ensure a seamless, modern experience for both workers on mobile and admins on desktop.
  • Backend & Data Pipelines: Powered by a robust Python FastAPI backend and Supabase (PostgreSQL). We built custom ingestion pipelines that continuously parse API streams from mapping providers and environmental indexes.
  • Core Engine & Math: At the heart is our internal Dynamic Threshold Engine. Rather than using static rules, we calculate parametric trigger sensitivities using a normalized scoring model. For instance, the payout threshold probability is continuously calculated as: $$ P_{trigger} = \sum_{i=1}^{n} w_i \left( \frac{S_i - \mu_i}{\sigma_i} \right) \cdot (1 - F_{score}) $$ Where \( S_i \) is the real-time sensor input (AQI, Traffic), \( \mu_i \) and \( \sigma_i \) represent historical baseline averages and variances, \( w_i \) are the condition weights, and \( F_{score} \) is the confidence penalty pulled from our ML image forensics and fraud detection suite.

Challenges we ran into

  • Real-time Data Syncing: Aligning distinct mapping data and environmental APIs accurately with our geographic zone bounds without introducing severe latency.
  • Threshold Calibration: Calculating the \( Z \)-scores for our dynamic engine on the fly without breaking backend performance or violating financial risk models.
  • Fraud Mitigation: Protecting the platform. Tuning our image forensics and ML models to detect spoofing without slowing down legitimate event triggers was a massive balancing act.
  • UI/UX State Management: Achieving frictionless state syncing between our high-speed Python ML backend and our Next.js frontend, ensuring the UI remained buttery-smooth even during live trigger events.

Accomplishments that we're proud of

  • Zero-Friction Claims: We successfully automated the entire lifecycle of an insurance claim down to milliseconds. Watching a real-world AQI spike mathematically trigger UI updates and process a payout instantly is incredible.
  • Premium Design: The UI design feels genuinely state-of-the-art. We managed to take the traditionally "boring" aesthetic of InsurTech and replace it with a sleek, vibrant, and interactive dashboard.
  • Enterprise-Grade Hardening: We built a surprisingly hardened backend—capable of handling complex IRDAI regulatory exclusions and real-time fraud mitigation while functioning autonomously.

What we learned

  • We gained a deep understanding of the complexities involved in live geographic mapping and handling asynchronous environmental data streams.
  • We learned the importance of "progressive UX disclosure"—providing gig workers with a simplified mobile interface while simultaneously serving up dense, complex telemetry and ML fraud scores to admins.
  • We leveled up in building architecture that smoothly bridges real-time triggers, raw SQL databases, and asynchronous Machine Learning pipelines.

What's next for Covara One

  • Predictive Routing Warnings: Moving beyond just triggering payouts after an event, we want to use ML to warn gig workers before they enter zones about to experience extreme conditions.
  • Expanded Parametric Factors: Integrating hyper-local weather APIs to expand our coverage to flash floods, extreme heat waves, and immediate road hazards.
  • Instant Settlement Integrations: Adding embedded wallet options to directly settle payouts via stablecoins or instant UPI transfers, guaranteeing immediate liquidity.

Built With

Share this project:

Updates