Eightlife — Smart Operations Platform for Food Shelves

A student buses to the food shelf. Eggs & chicken are gone. No SNAP backup. Eightlife: browse livestock before leaving, request food with no login. Staff get AI forecasting & expiration alerts.

Comment

What Inspired Me

I am an international student. I know what it means to depend on a food shelf and arrive to find the items you need are gone.

At St. Thomas, Tommie Shelf serves hundreds of students every week. But the students who need it most — international students on F-1 visas, ineligible for SNAP, with no financial backup — are the ones most hurt when the system fails. A wasted trip is not a minor inconvenience. It means going without food that day.

I built Eightlife because that broken moment — where a student takes the bus, makes the trip, and finds empty shelves — is a software problem. And software problems can be fixed.

The name comes from the infinity symbol — the figure eight turned on its side. Because the goal isn't to serve a hundred students once. It's an endless cycle of more food reaching more people, less waste, continuously improving.

Infinite impact. That's Eightlife.

What I Built

Eightlife is a full-stack nonprofit operations platform with two completely separate user experiences:

Client Portal (/request — no login required)

  • Browse live inventory by category before leaving home
  • Select exactly what your household needs — no preset boxes
  • Schedule a pickup by date and time slot
  • Receive confirmation number instantly (TS-XXXXXX format)
  • Mobile-friendly, zero friction, dignity-centered design

Staff Portal (login-protected dashboard)

  • Real-time inventory with batch-level expiration tracking
  • Color-coded alerts: critical (red), warning (yellow), info (blue)
  • Statistical demand forecasting — 3 months ahead
  • One-click SMS volunteer coordination from alert cards
  • Distribution logistics planning table by location
  • Donor impact report card: grant-ready metrics in one click

How I Built It

I built the entire platform in a single hackathon session using an AI-assisted development workflow with Emergent.

Tech stack:

  • Frontend: React + TailwindCSS + Shadcn UI + Recharts
  • Backend: Python FastAPI (18 endpoints, 100% tested)
  • Database: MongoDB with async Motor driver
  • Auth: JWT with bcrypt password hashing
  • Forecasting: Statistical seasonal average model — no external AI APIs, runs entirely in-house

The architecture has two key design principles:

1. Batch fetching everywhere — every API endpoint fetches all related data in one query. No N+1 problems. 7 performance issues were identified and fixed before deployment.

2. Two completely separate UX systems — the client portal has no sidebar, no admin elements, no jargon. It was designed to feel like ordering from a modern app, not filling out a charity form.

Challenges I Faced

The dignity problem was harder than the technical problem.

Building the inventory system and forecasting engine was straightforward. The harder challenge was designing the client portal in a way that genuinely respects the person using it.

Every decision had to answer one question: what stops the person who needs help most from actually getting it?

  • No login → because account creation is a barrier
  • No name collection → because international students fear sharing personal data
  • Choice-based selection → because preset boxes remove agency and ignore cultural food needs
  • Live inventory visible before the trip → because a wasted trip is not acceptable

The second challenge was scope. It is easy to over-build. I had to make deliberate decisions about what NOT to build during the hackathon — no native mobile app, no real SMS integration, no barcode scanning. Those are roadmap items. What matters today is that the core loop works: staff knows what they have → students see what's available → students request what they need → staff prepares → student picks up.

That loop is live and working right now.

What I Learned

Food insecurity on college campuses is not a resource problem. Minnesota food shelves are approaching 9 million annual visits. The food exists.

It is an operations problem and an access problem.

Staff need better tools to stop waste before it happens. Students need a way to verify what's available before making the trip. Both of those are solvable with software.

I also learned that peer-reviewed research on Minnesota food pantry users confirms what felt intuitive: clients value choice, cultural inclusion, and respectful treatment above almost everything else. Every feature in Eightlife was designed around that finding.

What's Next

  • Real SMS/Email integration via Twilio and SendGrid
  • Barcode scanning for faster inventory intake
  • Native mobile app for volunteers
  • Partner portal for Second Harvest Heartland
  • Multilingual support for East African, Southeast Asian, and Latin American student communities

Minnesota has nearly 500 food shelves. The platform is multi-tenant — adding a new food shelf requires no new code, only a new database record.

I built the pilot for Tommie Shelf. The platform is ready for all 500.

Built With

Share this project:

Updates