Resurgence

Resurgence: every relief dollar, traced. A transparent disaster-aid tracking that follows each donation from the need to the purchase to the delivery. Not just sanctioned but sanctuary

Comment

Inspiration

After a major flood in Nepal, a huge amount of money went into one central account, and ordinary people couldn't see where it went or whether affected families were actually helped. Funds were approved for families in need, yet they remained locked in accounts while people waited for weeks, sometimes months. The struggle to claim what was already allocated to them meant delayed shelter, food, medicine, and recovery. Donors want proof, and coordinators on the ground want to be believed. Resurgence is my attempt to close that gap: Not just sanctioned. Sanctuary

What it does

  • Coordinators post a need in plain words. AI extracts the items, quantities, location and urgency into a draft, and a human reviews it before anything is published.
  • Donors give through PayPal and can see exactly which need their money supports. An assistant answers questions in the donor's own language with multi language support.
  • Admins record purchases and deliveries, so each need climbs a visible proof ladder from posted to funded to delivered.
  • Live admin analytics (AG Studio and AG Grid) show KPIs, charts and a live donations ledger, with a USD to NPR toggle and CSV export.
  • A delivery scheduler (Bryntum) lets admin plan who delivers what, and when.
  • A story page from Rasuwa shows why this matters.

How I built it

Next.js and TypeScript on the front and back end, Prisma with Postgres for storage, and Zod to validate everything that comes in. Groq powers AI extraction and the multilingual assistant. Channel3 looks up real products for each need. Payments use PayPal Orders v2 with a verified webhook. AG Grid and AG Studio drive the admin ledgers and analytics. Bryntum powers the delivery scheduler for admins. The app is deployed on Render.

I built this solo working with AI coding assistant.

Challenges

  • Trusting money flows. I added validation before capture, automatic refunds when something fails, verified PayPal webhooks, and request caps on the assistant, after a security review of my own code.
  • Making the AI useful, not flashy. The assistant had to answer from real app data (like the latest donation), reply in the user's language, and stay warm and helpful.
  • Dashboards that are readable at a glance rather than cluttered.
  • Time. Switching from one AI provider to another after overload errors cost me hours. -Demo Video.It was hard to condense all of Resurgence’s features, and the whole site, into a single 3-minute video

Accomplishments

  • A complete loop: post a need, donate, record delivery, see it in analytics.
  • Payment safety features I'm proud of for a first project.
  • An interface built for Nepal (rupee toggle, local languages) that isn't hardcoded to one country.

What I learned

Trust is a feature. Every screen should answer "where did the money go?" I also learned how payment webhooks, refunds and validation actually work.

What's next for Resurgence

  • Cloud-scale reliability: managed database with backups, autoscaling for donation surges after a disaster, and a CDN for fast access worldwide.
  • Live PayPal mode.

Built With

Share this project:

Updates

Submission history