What Alevi Group builds
Three practices. Commissioned work first, and studio products when they are real enough to name.
People who look for Alevi software are looking for this practice: custom systems, SaaS platforms, and mobile apps from Alevi Group. The commissioned work is described below. Products of the studio are not listed until they can be opened.
Custom software
Custom software from Alevi Group is built around one organization's actual work. The records are specific. The permissions are specific. The language on the screen should sound like the people who use it, not like a template with the logo swapped. We start from the job: what has to be finished, what must not be lost, and what the current tools make harder than it should be.
A custom system can be internal. It does not need to be a startup, and it does not need a subscription. If one team is the whole audience, we will say so and build for that team. The point is the work, not the category. The sequence we use is the same one described in how a project runs: a boundary, a thin slice that really saves data, and care after release.
SaaS platforms
A SaaS platform is custom software that more than one organization will trust at the same time. Tenancy, permissions, and billing are the product, not a coat of paint on a single-company tool. Alevi Group designs those first, then cuts the first release until it does one job completely.
We write that approach down in how Alevi Group approaches a custom SaaS build, including the moment when a SaaS is the wrong shape and an internal tool is the honest one. We will not attach a pricing table to a product that does not exist yet.
Mobile apps
Alevi apps are not a separate company and not a default. They are the mobile form of the same studio: a website, a progressive web app, or a native client, chosen from the moment of use. If the work is occasional and linked, it should stay on the web. If people return all day and the device itself matters, native earns its cost. If an icon would help and the web is still the right codebase, a PWA is the middle path, with its limits said out loud.
The choice is written in web, PWA, or native. Store listings will appear when there is an app to list. A developer name is not a product.
In the studio
Alevi Group is also building products of its own. They are in development. They do not have public names on this site, because a name is a promise that someone can use the thing. When one is ready, it will have its own page, its own description, and a software record that matches the product a person can open.
Until then, the honest catalog is the three practices above. If one of them is the job you have, tell us.