About

A team that builds it, runs it, and stays.

ETCA Yazılım Danışmanlık Limited Şirketi provides technology consulting to companies — from cloud infrastructure and production operations to software development, game technology, and applied AI. Broad enough to carry a project from its infrastructure to its interface.

Why such a broad range?

Because this is how the work actually arrives. A client starts with "we need an admin panel" and two weeks in it turns out the real problem is that there is no infrastructure to run it on. Or a conversation that begins with "our server is slow" ends at database indexes nobody has looked at since launch.

When those pieces are split across separate vendors, the seams between them belong to no one. The infrastructure firm says the code is wrong, the software firm says the server is wrong, and you are left in the middle arbitrating. That is the real value of taking it from one team: responsibility does not fragment.

How we decide what to take on

We take work we can actually do. If we lack depth in an area, we say so on the first call rather than learning on your budget. Equally, if we think the right answer for you is not working with us, we say that too. A badly matched project is expensive for both sides.

How we work

Most engagements start in one of three shapes. We work out which one fits on the first call.

Project-based

Defined scope, defined delivery. We break the scope into pieces up front, each with its own timeline and delivery point — so you see progress throughout instead of one large reveal at the end.

Ongoing retainer

A set monthly capacity. This is the common shape for infrastructure and operations work, because that work does not finish — it continues. Capacity flexes up or down as your needs change.

Audit & takeover

Taking on an existing system, or simply reviewing it. We map the setup and report the risks with a prioritized fix list. There is no obligation to continue with us afterwards.

How an engagement begins

We do not like surprises, and neither do you. Here is the process end to end.

  1. 01

    You tell us what you are building

    Fill in the form or email us directly. The more technical detail you give about what is running and what is not, the more useful the first call will be.

  2. 02

    We have the first call

    It is technical, not a pitch. We listen, ask questions, and tell you whether it is workable. If we are not the right team, we say so on that call.

  3. 03

    We write the scope and the proposal

    What will be done, what will not, in what order, and over what timeline — in writing. If something is genuinely uncertain, we write that it is uncertain.

  4. 04

    We start, and progress stays visible

    You have repository and environment access from day one. We show working builds at regular intervals rather than a single delivery at the end.

The stack

This list is short because everything on it is something we actually use. If your team already has a stack, we work in it rather than around it.

Cloud & Infrastructure

  • AWS
  • Google Cloud
  • OpenStack
  • KVM / libvirt
  • Docker
  • OPNsense
  • WireGuard

Operations & Data

  • Prometheus
  • Grafana
  • PostgreSQL
  • MongoDB
  • Redis
  • Consul

Software

  • Java 17
  • Spring Boot
  • Next.js
  • React
  • TypeScript
  • React Native
  • gRPC

Game & AI

  • Unity
  • FishNet
  • Nakama
  • Gemma
  • Fine-tuning
  • RL / ML-Agents

Company details

Tell us what you're trying to build.

The first call is technical — no slide deck. We listen to what you're running and tell you whether it's workable. We reply within 2 business days.