Ahmed Al-HawajriLaravel & PHP Developer All work · Lamma

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
$93
Lamma

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.

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.

  1. Meet the children

    Children whom supervisors have visited at home, filtered by programme, age, country and urgent cases.

    /orphans

    Lamma — Orphans
  2. The child’s file

    A name, a story and a verified file, not a donation to an anonymous cause.

    /orphan

    Lamma — Orphan profile
  3. 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

    Lamma — Start a sponsorship
  4. The sponsor portal

    Their children and payments, and the latest field report with spending split across education, health and food.

    /dashboard

    Lamma — Sponsor portal
  5. Transparency for everyone

    The spending figures are computed from real payments and disbursements in the database, not typed into the page.

    /transparency

    Lamma — Transparency
  6. Two people on every payout

    Whoever records a disbursement in the admin panel cannot approve it.

    /admin/disbursements

    Lamma — Disbursements
Lamma — Orphans
Open the full page

How it was solved

Built to hold

The decisions that make the promises above true, rather than a look on the screen.

  1. 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.

  2. 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.

  3. 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

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.