Approach
Immediate action. Long-term vision.
The method behind every Bonvo engagement — built from ten years of production ownership, incident command, and migrations that could not afford a minute of downtime.
The Operating Principle
“I specialise in the architectural heavy lifting that most engineering teams avoid. When legacy systems reach their breaking point or a platform requires a zero-downtime migration, I take ownership. I think in subsystems and rewrites, not patches.”
How an Engagement Runs
Four steps, every time.
No two systems are alike, but the discipline is constant — from the first mapping session to the handover that makes Bonvo optional.
Map
Understand the system, its history, and its real constraints.
Scope
A written plan — sequence, rollback path, and what “done” means.
Own
Hands-on delivery: multi-tenant-safe, observable, incident-ready.
Harden
Observability, runbooks, docs — a team that can run it without us.
Map before anything.
Every engagement starts the same way: sit down, map out exactly what is needed, and agree on the communication mechanisms and design patterns before diving in. Constraints, failure modes, tenancy boundaries, and the political reality of the system get written down first. (This is not a slogan — it is how a front-end architect described working with Gergely: “Our collaboration was always smooth sailing.”)
Scope in writing.
You get a written plan: what will be built or changed, in what sequence, with what rollback path, and what “done” means. Rewrites are sequenced so the system keeps running — dual-run, verify, cut over, never big-bang.
Execute with ownership.
Bonvo does the work hands-on — designing, writing, and shipping the code, not supervising a bench. The standard is the one set on a platform where missed deadlines carry eight-figure liquidated damages: multi-tenant-safe, observable, incident-ready.
Harden and hand over.
An engagement is finished when your team can run the system without Bonvo: structured logging and Sentry-grade observability in place, runbooks written, decision records committed, knowledge transferred. Two years of runtime ownership after a framework migration is the proof this step is taken seriously.
Engineering Principles
The rules the work is held to.
Boring in production.
Excitement belongs in the design phase. Systems should be observable, restartable, and dull to operate.
Zero-downtime is a discipline, not a feature.
Dual-running, backfills, verification, and rollback paths are planned before the first commit.
Multi-tenancy is a security boundary.
Context restoration and tenant isolation are treated with the same rigor as authentication.
Security is offensive-minded.
The person reviewing your auth architecture should think like the person filing the pre-disclosure report.
AI where it compounds.
LLM tooling is applied where it removes recurring toil — like automating a sixth of review feedback — not where it demos well.
Write it down.
Decision records, runbooks, and honest post-incident reviews outlast any individual engagement.
Engagement Models
The shape follows the problem.
Remote-first from Budapest (CET) — a working day that overlaps European mornings and US afternoons. On-site in Hungary and across Europe by arrangement.
The first conversation is a mapping session.
Bring the problem as it actually is — half-understood, politically complicated, on fire. That's the normal starting state.