Case Studies

Systems we built and run

Codnov was incorporated in July 2026 and has not yet completed an external client engagement, so we are not going to show you one. What follows is what we have actually built and run — with figures a technical reviewer can reproduce from the repositories.

EducationOur own product
Ongoing — in production

A study-abroad marketplace in 22 languages

Empire Overseas Education

A programme catalogue, application pipeline and partner network serving students across South Asia, the Gulf and Europe — localised into 22 languages including right-to-left Arabic and Urdu.

Locales
22
Including RTL Arabic and Urdu
Schema migrations
177
Versioned, reversible, in production
Partner intake
Audited
Review step and key provisioning are logged
Next.jsTypeScriptFastAPIPostgreSQLAlembicnext-intl
View case study
RecruitmentOur own product
Ongoing — in production

A recruitment app that fills its own forms

EmpireO

A cross-platform candidate application where a voice assistant completes the profile, matches are scored against the live role catalogue, and document checklists change by country.

Platforms
3
iOS, Android and web from one codebase
Profile capture
Voice
Conversational intake writes structured fields
Doc rules
Per country
Modelled, not hard-coded per screen
ExpoReact NativeTypeScriptFastAPIPostgreSQL
View case study
Platform engineeringOur own product
Ongoing — in production

One identity layer under seven products

Empire Core

A shared business core that gives seven separate brand applications one customer identity, one permission model and one audit trail — without any of them sharing a database schema by accident.

Services
7
Brand APIs on the shared core
Isolation
ORM-level
Scoping in the data-access path, not per endpoint
Roles
Single model
One permission model across brands
FastAPISQLAlchemyPostgreSQLRedisAlembic
View case study
B2B marketplaceOur own product
Ongoing — in production

Referral attribution that survives an audit

Empire Global Partner Network

A partner portal where every registration is attributable to the person who referred it, using single-use invites rather than shareable codes.

Invites
Single-use
Bound to the issuer, not shareable
Attribution
End-to-end
Carried through registration, not captured late
Reporting
Per partner
Activity reports against the stored referrer
Next.jsFastAPIPostgreSQL
View case study
Professional servicesOur own product
Ongoing — in production

A client portal you can only enter by invitation

Codnov.AI

The portal behind this website — enquiry, review, approval, then an account. Built after we found our own registration endpoint would mint a client account for anyone who posted to it.

Registration
Invite-only
Approved enquiry is the only path in
Roles
4
CEO, admin, staff, client — one shared dependency
Audit log
Diffed
Actor, entity and change recorded on writes
Next.jsTypeScriptFastAPIPostgreSQL
View case study