Community platforms, client builds, studio products and earlier experiments. Each has its own stage; a running demo alone does not establish adoption or production readiness.
Shipped & maintained
Community work
Live platforms built for community organizations — deployed, maintained, and separate from client MVPs and lab experiments below.
Live · maintained
Association of Zambians in California
Built and deployed for the ZANC community — events, membership, and payments on a site the association owns and runs day to day.
Vite + React + Supabase: content, dues, and community workflows.
Live and maintained — not a client MVP or experiment.
Built and owned at LevrAge Innovation Studios — at different stages, and labeled that way: live products, working MVPs, and early concepts. The same patterns we bring to client work.
Live
Verifiable AI + data infrastructure — the studio's long arc.
The studio's long-horizon venture: trust and verification infrastructure for AI and data workloads, currently in deep R&D.
What we shipped
Core data and infra patterns that support AI-augmented workflows.
The engineering discipline behind it (receipts, audit trails) shows up in client builds today.
The studio's own product. Make your card, share it with a scan, and let Levi help you remember the people you meet. Live, with open beta in preparation.
What we shipped
One card drives its face, its QR code and its contact file. The QR carries only the fields you choose, and sharing by scan needs no account.
Tell Levi who you met, by voice or text, and it saves the person with the context.
Released 30 October 2026 after 862 automated tests and 19 read-only production checks.
Early concept for a trust layer on Africa's Atlantic export corridor — an exploratory build sharing patterns with CopperCloud, not an operating platform.
What we shipped
Next.js + Firebase with Pinecone-backed intelligence for corridor workflows.
Parked until the corridor work has a real audience.
The deepest systems we build and run in-house: signed receipts, audit trails, and governed data pipelines. These are working R&D platforms that show our engineering discipline — shown honestly as research builds, not commercial products.
In-house R&D platform
Proof-carrying compute (R&D)
Working R&D platform for verifiable computation — receipts, attestation, and workload coordination, run on our own nodes as an engineering proof.
A public monitor of power stress in Zambia's Kariba hydrology channel, built from public data. Readings are labelled observed or estimated, with the model's confidence shown: a present-state reading, not a forecast.
• Collects public hydrology, rainfall, exchange-rate and copper-price data on a daily schedule.
• Publication is gated by data freshness, and the page states the model's limits, including the range of scores it can reach.
• Days without a reading are left blank, not filled in.
Project ideas and early builds — some shipped as demos, most started for clients or partners who didn't move forward. Not maintained like community work above.
Afriai
Demo / paused
Early concept at the intersection of African markets and AI infrastructure — pattern tests, not a maintained product.