migo.dev:~$_

migo.dev:~$ studio --senior

From first screen
to working system.

One person, one inbox, twenty-plus years of senior engineering. Pick what you need on the diagram — the rest of the page follows.

Start a project Production proof
Years
20+
Production contexts
7
Reply within
24 h

A website a public-facing site or landing page where people first meet your offer. see in scope →

WEBSITE or landing APP or tool BACKEND or API AI in a product MODERNIZE old code

migo.dev:~$ verify signa

Proven
in production.

0 years in production software

Continuous since 2005. Senior ownership across product, platform, infrastructure, and AI delivery contexts.

0 known production contexts

Each shipped end‑to‑end. Listed below.

scale high‑volume, low‑latency

Class wording for older roles. Exact figures stay in private context.

AI / LLM chat

Multi-provider LLM chat infrastructure on Kubernetes; agentic workflows under senior review.

nexos.ai 2025 — present

Cybersecurity / VPN

API gateway on Go & Kubernetes. 100–300k RPS‑class workloads, client devices in the millions.

NordVPN 2023 — 2025

Ad‑tech / RTB

Monolith → microservices on Kafka + ClickHouse. Sub‑60 ms RTB at 500k events/sec.

MediaMath 2020 — 2023

Email infrastructure

Perl → Go migration for outbound email; hundreds of millions/day‑class with reliability intact.

GetResponse 2018 — 2020

OTT / DRM

License servers and license‑generator machines. PlayReady, multi‑level AES, secure streaming.

NeuLion 2016 — 2018

Mobile DRM

Backend services and native mobile libraries (iOS/Android) for DRM-protected video. Acquired by NeuLion.

Saffron Digital 2011 — 2016

IT infrastructure

Network management, CRM, infrastructure automation. Designed architecture from scratch over 6.5 years.

ABP Computer 2005 — 2011

Full chronology & recommendations on LinkedIn · exact figures stay in private context, per disclosure policy.

migo.dev:~$ inspect scope

Scope without
the guesswork.

Each entry point has a delivery shape and a technical view. The highlighted row mirrors what's selected in the system map above.

01 A website You're launching an offer, campaign, product or personal brand, or the current site no longer explains the value clearly. Information architecture, UI, responsive frontend, contact path, SEO basics, analytics hooks and deployment. Static/content-first: Astro, Next.js or Vite, edge deploy, forms/API where useful, performance and WCAG from the start.
02 An app or tool A team needs a dashboard, operational panel, SaaS MVP or internal tool that organizes real work. Process turned into a product: UI, auth, data model, API, integrations, roles and a path to evolve. TypeScript app stack, PostgreSQL, API/serverless or Go where useful, CI/CD and observability; mobile only when justified.
03 A backend A product, app or automation needs business logic, data flow, webhooks, third-party systems or background jobs. API design, integrations, data model, auth, retries, jobs, documentation and operational visibility. Often Go + PostgreSQL, containers/serverless/Kubernetes by scale, queues/events, OWASP API security and OpenTelemetry.
04 AI in a product A repeated workflow with text, documents, support, sales, operations or internal knowledge can be assisted safely. LLM workflow, eval cases, guardrails, human review where needed, cost/latency tracing and fallback paths. Provider-flexible LLM layer, RAG only when needed, vector search where justified, queues/workers, GenAI observability.
05 Modernize or rescue An older Perl/PHP monolith or critical system still runs the business, but every change is slow or risky. Audit, test harness around critical paths, observability, strangler-fig plan, rollout gates and rollback path. Legacy to clearer boundaries; Go where it pays off; API/queues, CI/CD, dependency posture and observability gates.

These are example technical bases, not fixed packages. The actual stack follows the product stage, team, budget, risk and maintenance path. If your case does not fit a row, choose Something else in the contact form.

migo.dev:~$ cat pov

A small point
of view.

  1. 01

    Start with the job, not the stack.

    The right architecture follows the right outcome. A correct tech choice for a wrong problem still ships a wrong product.

  2. 02

    Small projects deserve solid engineering.

    Fragility cost is independent of project size. A landing page that breaks on Safari is a broken product, regardless of budget.

  3. 03

    AI helps, but doesn't own the outcome.

    Models are a force multiplier under senior judgment, not a substitute for it. Eval, review, rollback — or it doesn't ship.

  4. 04

    Frontend is product work.

    If the interface is confusing, the system is confusing — regardless of what's behind it. The first screen sets the trust contract.

migo.dev:~$ start handoff

Tell me what you
want to build.

A short message describing what you want to build, what exists today, what has to work, and any deadline or constraint is enough to start a useful conversation. I reply within a working day.

EN / PL · remote, Poland · senior & principal engineering

What's closest to your need?
Privacy and data use

Controller: Tomasz Kolaj, KolajFX JDG, Gdansk, Poland. Contact: tomasz@migo.dev.

Purpose and legal basis: I use the data from this form to reply to your message, understand project context and, if the conversation leads there, prepare or perform cooperation. The legal bases are GDPR Art. 6(1)(f) for handling inquiries and Art. 6(1)(b) for steps before a contract.

Data: name, email, selected project type, message content and technical data needed for delivery and security. Providing the data is voluntary, but necessary for a reply.

Cookies and local storage: the site does not use analytics or advertising cookies. If you switch language manually, that preference may be stored locally in your browser so the site can remember it.

Recipients: hosting, security and transactional-email providers, especially Cloudflare and Resend, only as needed to run the site and deliver messages. Data may be processed outside the EEA under appropriate safeguards such as data processing agreements and standard contractual clauses.

Retention and rights: I keep correspondence only as long as needed to handle the inquiry, cooperation or legal claims. There is no automated decision-making or profiling. You can request access, rectification, deletion, restriction, object to processing and complain to the Polish data protection authority.