Skip to content
MTKSoftLabs
About

A publisher, not a workshop for hire

MTKSoft Labs builds its own applications, releases them on the platforms they belong on, and licenses them directly to the people who use them. We do not take on client projects — the catalogue is the work.

Founded
2026
Based in
India
Group
MTK
Model
Own products, licensed
Position

Plenty of software gets written. Far less of it gets finished, and less still is around in five years.

Builds go stale. Store listings rot. Installers stop being signed. The last release note is two years old and the issue tracker has quietly closed itself. None of that is a coding problem — it is what happens when work is organised around a launch instead of a lifespan.

Being the publisher is what makes the alternative possible. Nobody hands us a scope and a deadline and walks away. We decide what to build, we carry the cost of keeping it alive, and we are paid by the people who actually use it — which is the only arrangement where maintaining software for a decade makes commercial sense.

So the studio is built around the whole lifespan. One engineered core, the platform-specific behaviour a user would actually notice, and a release pipeline that turns a version bump into signed artefacts and store submissions without anyone having to remember the steps.

MTKSoft Labs is part of the wider MTK group, alongside MTK Publishing.

01Constraints

Easier to describe by what we refuse

Every software company claims to care about quality. These are the specific things we give up in order to mean it — several of them commercial.

  1. 01

    We do not sell what we cannot maintain

    Publishing on a platform means owning its releases, its store policy changes and its bug reports for years. If we cannot commit to that, the product page says planned rather than taking your money.

  2. 02

    We do not take away what you bought

    A one-time licence keeps working. We do not remove a feature from a version you already paid for in order to move it behind a subscription.

  3. 03

    We do not require an account to use a tool

    Sign-in exists where a product genuinely needs identity to function. It is not a growth mechanism and it is not a gate in front of the thing you paid for.

  4. 04

    We do not measure people who did not ask

    No third-party analytics inside our applications. When we need to know whether something is broken, crash reporting is enough.

  5. 05

    We do not describe unfinished work as finished

    Beta means beta. If a build is in testing, it is labelled as being in testing, on the same page as its download.

Next

The catalogue is the argument.