# Gábor Gyurák — the developer behind RootCR

URL: https://rootcr.com/about/
Updated: 2026-08-24

# Gábor Gyurák — I write every line myself

> **In short:** There is one person behind RootCR: Gábor Gyurák. I build web systems for small and mid-sized businesses: websites and online stores from my own code, ordering and quote request flows, automation that replaces manual work, and the security layer that belongs to them. No page builders, no plugin chains — your processes should not have to bend to the limits of a framework. The quote comes from the same person who writes the code and fixes the bugs — here there is no responsibility hidden between a salesperson, a project manager and a subcontractor.

## How do I work?

Four steps, with fixed points. **Conversation:** you tell me what your company does and where it hurts; if I cannot genuinely help, I say so here, not three months later. **Quote:** written scope, fixed price, fixed deadline — plus an itemized list of what is not included. **Build:** you see it working every two weeks, not in a screenshot. **Handover:** the code is yours, the server is yours, the access is yours, along with a measurement report and a description of how everything works.

## Technologies — and why these

Rust, TypeScript, Node.js. These are not exotic choices: established, widely known tools you can always find another developer for. That is deliberate. With a one-person workshop the most important question is what happens if I am not available — and the answer to that is not a promise, but the fact that the system needs no special knowledge to carry on.

What I deliberately avoid: page-builder frameworks, plugin chains, and services that keep your data inside their own system for a monthly fee.

## The risk of a one-person workshop — openly

This is a real risk, and I am not going to talk you out of it. What I can do about it, I do, and every item is verifiable:

- the **full source code** and every access credential are yours at the moment of handover;
- the system is **documented**, it does not just live in my head;
- **established technologies**, so any developer can take it over;
- **six months** of free bug fixing after handover;
- no mandatory operations contract — the delivered system can run anywhere.

The advantage you get in return: there is nobody to pass responsibility to. Whoever you have the first conversation with writes the code, and answers when something breaks.

## What I do not take on

I do not take on template sites, I do not compete for "cheapest quote", and I do not take on work where I honestly believe an off-the-shelf system would be better. That last one is not modesty: a badly chosen custom build is a bad deal for both of us.

## What you can check instead of my word

The [case studies](/case-studies/) hold the most recent work, on public
addresses, with measured data: a [bakery site](/case-studies/bucipek/) with an
ordering and careers module, a [craft webshop](/case-studies/honeyzsu/) with its
own catalogue manager, a [wholesale quote request form](/case-studies/pekarunagyker/)
with five layers of protection, and a [full custom site](/case-studies/lunavera/)
in place of a template WordPress. Each one states what the task was, what the
solution became, and what we measured afterwards — with the method and the date
of the measurement.

This section deliberately stands where a professional CV would. For a developer,
"I have been doing this for x years" is not a verifiable claim; which system is
running right now, and how fast it answers, is.

## Contact

- Email: info@rootcr.com — reply within one business day

If you have a task and want to know whether it needs custom development at all: [write to me](/#contact), and I will tell you.