We design, build and run our own apps, and people use them every day. Bring us yours: we shape the idea, build it and keep it running, to the same standard.
In our own apps, rounded down.
Two apps we designed, built and still operate ourselves. What we bring to your project is what keeps these running.
Photograph a maths question, or type it. Get back a short video that works it out, step by step, out loud.
What it took
Tap a game and it starts. Nothing to download, nothing to install. Play alone, against AI, or against someone else.
What it took
Start with the first and stop there if it isn’t worth building. Most projects run through all three.
Tell us the idea as it stands. We tell you whether it’s worth building, what we’d build first, and what we’d leave out.
You get a straight answer, and what we’d build first.
Scope, architecture and the reasons behind each decision, settled in writing. Then working software as we go, so you can try it and steer it while changes are still small.
You get a written plan, then a first version people can use.
We keep building and stay on as the team that runs it: hosting, releases and monitoring. Or we hand it over to your team. We agree which before we start.
You get software that keeps running, or a clean handover.
Every service here is something we already do for our own apps.
Web and phone apps, websites and first versions, and the systems underneath them.
AI features you can trust, interfaces people can talk to, and content made from your data.
Hosting, safe releases, tested code and payments, kept running after launch.
Also on requestRapid clickable prototypesPhotos, PDFs and forms turned into structured dataInternal tools and automationsLegacy modernisationTechnical due diligence
Three rules we build into every project. Each is already true in the apps we run.
Where your software decides something that matters, a total, a price, a result, code checks the answer before anyone sees it. If it can’t be checked, the software says so instead of guessing.
Already true in Let’s MathEach part runs with only the access it needs, including add-ons someone else wrote. A fault in one stays in that one, and nothing reads data it has no business seeing.
Already true in Miniant GamesPayments, credits and balances live in one ledger. Any part can ask to spend; only the system can grant. Nothing creates value on its own.
Already true in Miniant GamesWe sign a non-disclosure agreement before you share anything sensitive.
Access to your systems is granted per project, kept to what the work needs, and removed when the work ends.
Keys and passwords live in a secrets manager, never in the codebase, in chat or in email.
Decision records and setup notes, so the system does not depend on any one person, including us.
Web and mobile applications, AI products, games and the platforms underneath them, and the infrastructure that keeps them running. The services above are the full list, grouped by where they sit in a build.
Yes. We are based in Dhaka (GMT+6), work in English, and take clients from outside Bangladesh.
Where it speeds the work up, the way we use any tool. Every change is reviewed, tested and type-checked before it ships, and the decisions about architecture, data and security are ours, not a tool’s.
We reply to every enquiry within two working days.