vedia. Nigeria Ltd WAT

Software engineering · est. in Nigeria

We build the systems clinics, schools and businesses run on.

Haematology registries, hospital information systems, multi-tenant school platforms, inventory and fintech backends, and the statistics behind published research. Everything below is real, shipped code — with a pointer to where it lives.

vedia logo: a V made of two strokes carrying letters and numerals, with owl eyes at the top and the words learn, grow, excel

01Index of work

Open a row for detail. Press / to filter.

Stack ledger — projects using each technology, computed from the index above

    02What we build

    Each line links back into the index.

    Clinical & health systems
    Registries with disease-specific scoring, EMR and departmental workflows, PACS-backed imaging, maternal care records that survive bad connectivity.
    School & institutional platforms
    Multi-tenant school management with results, fees and payroll; registration and result processing for polytechnics; desktop and Android delivery.
    Commerce & fintech backends
    Multi-branch inventory with offline tills and generated reports; account, marketplace and lending services with property-based tests.
    Research & statistics
    Structural equation models, regression on field assessment data, survey analysis — and repositories that keep institutional research findable.
    Web & content
    Organisation sites with their own CMS, payments and enquiry flows, accessibility tested in CI, and an AI drafting pipeline with a human approve gate.

    03How we work

    Habits you can check in the repositories.

    1. Offline is a requirement, not an edge case.

      Branch tills keep selling when the link drops. Maternal records are designed to sync later. The school system ships as an installer that runs with no server at all.

    2. Roles before screens.

      Access control is designed first — facility isolation in the haematology registry, row-level tenancy across schools, row-level security in Postgres.

    3. Models advise; people decide.

      Every AI output in a clinical flow waits for clinician review. Content drafts wait for an explicit approve. Heuristics are labelled as heuristics.

    4. Tests touch real infrastructure.

      Testcontainers against Postgres, in-process Postgres for unit tests, Playwright with axe for accessibility, property-based tests for money paths.

    5. Handover is part of the build.

      Deployment guides written for first-time operators, environment references, OpenAPI specs with Postman collections, and a written list of known limitations.

    04Start a project

    Tell us what the system has to do on its worst day — no network, wrong input, an auditor asking questions. We'll start there.

    • emailcontact@vediang.org
    • tel0802 541 6885, 0803 335 8906
    • lagos
      Head officeRoyal Estate, Unit 3, Block C, Aggrey Road,
      Tech Staff Qtrs, Sabo, Yaba,
      Lagos State, Nigeria
    • uyo
      Branch office10 Brooks Street, off Barracks Road,
      Uyo, Akwa Ibom State
    • githubgithub.com/BrianBassey37
    • sourceMost client repositories are private. Read access is granted on request for due diligence.