Few engagements done well. Growing the work, not the volume.
Akaya Labs aims to grow in the nature of its work — not in scale.
View details →Akaya Labs is a one-person software studio founded by Ahmet Karaca in Rize, Türkiye, in 2026. It builds and publishes its own apps and takes on a few client projects a year. This page explains how it works and what it turns down.
Design decisions are made by the person who will write the code. The client always knows whom to ask. Illness or a full calendar are real risks in this structure, which is why schedules are written down and source code and access are documented and handed over to the client.
The real life of a software product begins on the day it ships, not during delivery. Akaya Labs treats post-launch performance, maintenance, security updates and scaling as first-class concerns rather than optional add-ons. Post-launch maintenance is available through a project-based agreement or a retainer.
Performance, accessibility and security are discussed at the start of a project. Automated tests are standard on the backend; the client side is tested by hand on real devices. Code is written for the next developer reading it two years on, and architecture decisions are documented.
Akaya Labs aims to grow in the nature of its work — not in scale.
View details →Akaya Labs' promise to clients can be summarised in a single sentence: delivered on the date agreed, at the quality promised, without surprises.
View details →Akaya Labs is a one-person software studio. Interface design, frontend, server, mobile, infrastructure and post-launch support are all in the same hands. Nothing is lost between layers, and there is one person to ask. The cost is just as clear: only a few projects run at once.
We keep our distance from both extremes the software industry tends toward: the half-finished MVP rushed out in two weeks, and the ambitious engagement that stretches over two years and never actually ships. For Akaya Labs, the right pace is the pace at which a word can be kept. We honour the agreed timeline; when something needs to change, the reason and the revised schedule arrive together, and any additional cost is presented for client approval before an invoice is issued.
Akaya Labs takes a few projects a year, so that each one gets the time, attention and post-launch care it needs. This limits revenue. Time will show what it returns.
Akaya Labs does not design dark patterns or interfaces that manipulate the user, and does not build software for gambling, betting or fraud-driven business models. These limits are raised openly in the first conversation and, where required, the project is declined.
Our name carries both a sense of care and inherited memory. The gold ring on the logo — an enso from the sumi-e tradition — represents the beauty of the impermanent and a steady resolve drawn in a single stroke.
The mountain silhouettes inside the ring are a nod to the Black Sea geography of Türkiye; quiet but rooted, making room for everything that grows on it. The sakura petal stands for softness; the crimson stamp for the accountability sitting beneath every product.
Working with this palette is not coincidental. Like every Akaya Labs product, the brand identity is a slow, careful, and owned decision.
Akaya Labs does not work like a vendor that finishes the design, sends an invoice and leaves; it also accounts for the long-term health of the product. Architecture choices, third-party dependencies and maintenance costs are discussed together, and the outcome is put in writing. Risks are raised before they materialise, not after.
Every project begins with an agreed, written scope document. It defines the technical requirements, the delivery schedule, the payment plan, the number of revisions included and what falls outside the project. Changes that emerge along the way are agreed in writing before they join the scope; any extra cost or time is presented for client approval before an invoice is issued.
Client communication runs through a single official channel agreed at the start of the project. That channel, whether email, business messaging or a project management tool, stays the same throughout. Official matters receive a response within one or two business days; a separate fast channel can be defined for technical emergencies. The client always speaks with the same person through the same channel.
Once paid for, source code, design files and access keys belong to the client. User data belongs to the client from the start. If the client wants to continue with another developer, the handover runs cleanly, because architecture decisions, third-party dependencies and hidden configuration are documented from the outset. The Akaya Labs business model relies on clients choosing to continue, not on lock-in.
Founder · Software Developer
Founder and only developer of Akaya Labs, based in Rize, Türkiye. Designs, builds and ships every product the studio makes.
Akaya Labs takes on a few client projects a year. If you are planning a SaaS, a mobile product or a focused internal tool, write a few lines; you will hear back within 1–2 business days.