We make our own software, and help you ship yours.
Bayanura is a team of three. We build our own apps, and we use what that taught us to get other people's AI-built apps ready for customers.
Why both
We had the problems before our clients did
Every check and tool the Studio uses was built for our own apps first. These are the dates they were built, in our own history.
- 14 August 2026Jidoka. Built to walk our own apps and record what broke.
- 3 September 2026Isnad. Built to catch our own documentation drifting from our own code.
- November 2026The Studio. The same checks, on somebody else's app.
First commits in our own repository.
What we have built
Our own software, measured
On web, iPhone and Android, and all of it in one repository.
- Web and shared
- 1,711,811
- iPhone, in Swift
- 399,949
- Android, in Kotlin
- 387,633
2,499,393 lines of our own software
Counted over our own repository on 7 October 2026: every tracked source file, less archived projects, documentation and lock files.
The mark
Where the name comes from
One bowl, two readings.
The point below is bā's, for Bayanura.
The point above is nūn's, for nūr, light.
No letter takes a point above and below at once, so the doubling reads as deliberate rather than as a mistake. The light is never drawn, only the vessel that holds it.
From our own brand specification.
Who we are
- Faiz SaleemLeads client work. The person Studio clients deal with.
- MartynaEngineer. Builds and tests the apps.
- HaiderProduct and design.
Get in touch
For Studio work, send a link to your app and a line about what it does.
We reply by email.