Software company — İstanbul, Türkiye
We design, build and operate applications — iOS and Android, web, and the services behind them — for companies that need working software rather than a prototype.
What we build
We take projects end to end: the data model, the screens, the release, and the months afterwards when real users arrive.
Native Swift and Kotlin, or a shared codebase where that is genuinely the right call. Store submission, subscriptions and in-app purchases, push, crash reporting and staged rollouts — the parts that decide whether an app survives its first week.
Customer-facing products and the internal tools nobody demos: dashboards, admin panels, operator screens. Server-rendered where speed and search matter, with the data model settled before the first screen is drawn.
Software shaped around an existing operation — ordering, stock, billing, reporting — instead of asking a team to work around the software. Integrations with the tools they already pay for.
APIs, relational schemas, background jobs and migrations that do not lose rows. Logs and metrics that answer a question at three in the morning instead of raising another one.
How we work
Every agency draws the same waterfall. These are the things we will actually be held to.
The people who design a feature build it. Work reaches you in weekly increments you can open and use, not as a demo at the end of a quarter.
Deployment, monitoring and the alert that wakes someone up are part of the job. Software that only works on the developer's machine is not finished software.
Each non-obvious choice — a database, a library, a trade-off accepted on purpose — is recorded with its reason. You keep the reasoning after the team changes.
Engineering
A tool list means little on its own. The reason next to each one is the part worth reading.
| Tools | Why |
|---|---|
| Swift · SwiftUI Kotlin · Jetpack Compose |
Native where an app has to feel native — gestures, animation and battery behave the way the platform promises. |
| TypeScript React · Next.js |
Types catch the errors a test suite never gets around to. Server rendering for anything a search engine or a slow connection must reach. |
| Node.js · NestJS Python · PostgreSQL · MySQL |
Relational data with migrations under version control, so the schema has a history you can read and undo. |
| AWS · Cloudflare Docker · GitHub Actions |
The same pipeline builds staging and production, so a release is a repeat of something that already worked. |
| Structured logs Metrics · alerts · on-call |
Alarms that reach a person. A dashboard nobody opens is not monitoring. |
Contact
A paragraph about the problem is more useful to us than a specification. We answer in English or Turkish.