The work isn't us. The work is the system that keeps running after we ship.
A deliberately small studio. Few projects, deeply followed. We open a file, not a brochure.
Six things, every time
Every system we ship has these six. Not marketing promises — a checklist.
A documented system, not just code
Each ship: BookStack runbook + architecture diagram + ENV reference.
Monitoring on day one
Alerting, dashboard, page rotation in place before ship.
Backups that are tested, not assumed
Manual quarterly restore drill. Dated records.
Failure recovery you can demo
We can simulate the actual failure and recover the live system.
Your jurisdiction, your control
Self-hosted. EU or TR, your preference.
A handover plan from day zero
Handover package ships with the system. Operator transition documented.
Four phases
Discovery → Design → Build → Operate/handoff. Each phase has clear outputs.
Discovery
2–4 weeks. We extract the shape of the problem. Existing infrastructure, stakeholders, constraints.
Design
2–6 weeks. Architecture sketch + ship plan + cost estimate. We commit at this stage.
Build
8–20 weeks. In shippable chunks. Each chunk goes live, doesn't wait.
Operate/handoff
Continuous or handover. Monitoring, alerting, runbook training.
Engagement models
Three models. The middle one is most common.
Project
One-off ship. Discovery + Design + Build. We ship and hand off.
Build + operate
Ship plus post-ship operations. 3–18 months.
Advisory
Architecture advisory. Hourly or retainer. We don't write code, we point direction.
Projects we turn down
- 01 · Marketing sites and brochureware
- 02 · Rescue jobs without honest access
- 03 · "Build it in two weeks" with no design
- 04 · Anything that requires us to bend our values
Where we are
Samsun, Turkey. Northern Black Sea coast. The studio's physical office is small; the core operation runs here.
Servers in Europe and Turkey. Customers mostly in Turkey; accepting first projects from the EU and the Gulf.
The studio is deliberately small. If you ask "who'll work on it," we'll tell you, by name, in the first call.
$ start --shape=problem
What's the shape of your problem?
Two channels: structured brief or direct email. We respond within 24h.