05 / 05Orphan sponsorship platform2026
Lamma
Sponsor a named child within their own family, and see where your money went.
- Laravel 12
- PHP 8.2
- MySQL
- Blade
- Bootstrap 5
- Vue 3
- Sanctum
- Pest
- Playwright
- Pinia
- Tailwind 4
- Chart.js
- Vitest
- Larastan
- Spatie Permission
- REST API

At a glance
01Who is it for?
- The sponsor: chooses a named child, pays regularly, and follows the reports and where the money went.
- The visitor: browses children and programmes and reads the transparency page before deciding.
- The association’s staff: an administrator who sees everything, an accountant who runs transfers, and a field supervisor who sees only their own country’s families.
Before the project
Most donation sites ask you to trust them: you give to an anonymous cause and never see what arrived, what was kept and what was spent. Lamma is built so you do not need that trust: you sponsor a child who lives with their family, through a verified local association, and you see your money item by item.
- Marketing figuresA percentage typed into the page that nobody can check.
- Giving without a faceThe donor never learns where the money went.
- Double chargesA double tap on Pay, or a webhook sent twice, can charge twice.
The product
The product, as its users use it
Scroll to walk with the user one step at a time, each step on the screen where it actually happens.
Meet the children
Children whom supervisors have visited at home, filtered by programme, age, country and urgent cases.
/orphans

The child’s file
A name, a story and a verified file, not a donation to an anonymous cause.
/orphan

Sponsor at your amount
The sponsor covers the whole amount or part of it, pays monthly, quarterly or yearly, and sees before paying that the platform takes no fee.
/checkout

The sponsor portal
Their children and payments, and the latest field report with spending split across education, health and food.
/dashboard

Transparency for everyone
The spending figures are computed from real payments and disbursements in the database, not typed into the page.
/transparency

Two people on every payout
Whoever records a disbursement in the admin panel cannot approve it.
/admin/disbursements

How it was solved
Built to hold
The decisions that make the promises above true, rather than a look on the screen.
Every figure derived from the database
The spending ring is aggregated from approved disbursements, the reach percentage is a division, the number of field visits is a real count. Nothing is typed into the interface.
A partial constraint on an engine without them
A generated column equals 1 for active sponsorships and NULL otherwise, with a unique key over sponsor, child and that column. MySQL leaves NULL out of unique constraints, so cancelled sponsorships never block a return.
Four eyes on every disbursement
Whoever recorded a disbursement cannot approve it, and the policy checks that in code, not the interface. An approved entry is reversed with a counter-entry, never edited, and a unique idempotency key makes a double charge impossible in the engine.
Worth explaining
One origin for everything
The public site, the admin panel and the API share one domain, so no CORS, no cross-site cookies, and the tightest possible content-security policy. The session is an HttpOnly cookie, not a token in localStorage.
A public site that works without a server
The data file is both seed and hydration layer: its written values work with no API at all, and a hydrate step swaps them for database values when the server is up. If the server falls over, the site shows correct content instead of a blank screen, and that is tested.
Tests on MySQL, not SQLite
The schema relies on a generated column and a full-text index that SQLite does not have, so a test suite on SQLite would pass while production broke. 53 Playwright browser tests walk the site against the real API.
The outcome
What was delivered
- 32
- screens in the product
- 40
- real screenshots
- 384
- automated tests
- 2
- full languages
- A live site with demo accounts for four roles, on a demo payment gateway where no money moves.
- Arabic first and full English, with over a thousand translated strings guarded by a test.
- 331 Pest tests and 53 Playwright browser tests.
- A 23-screen admin console, each role seeing only its own part.
- PASSWhoever recorded a disbursement cannot approve itlamma/tests/DisbursementRecordTest.php
- PASSThe orphan grid sorts on the index, never with a filesortlamma/tests/OrphanGridSortTest.php
and 382 more in the repository
Every screen
Every screen, as it is
Real screenshots of the project running — not stock imagery.
Every page in the project
Real screenshots of the project running — not stock imagery. · 40 screens





