Let's build
Martin Skořupa in a black coat, sitting on a low wall with illuminated buildings behind him

Martin Skořupa, builder. I build products, platforms, pipelines, a game, tools and a studio, and I keep them running.

co-founder, CEO and CTO of the IT studio Audaron

My own products, the studio I co-founded, and cloud platforms for the state and for the largest outpatient care provider in the Czech Republic.

Powerhouse in tech, menace in mindset. First commit to production. Solo or leading. Fully remote.

Stuff I built and stand behind

Build 1 of 6

co-founded June 2026

Audaron

Role: Co-founder, CEO and CTO

I co-founded Audaron. As CEO I make the company's decisions and as CTO I build what it runs on; sales and client relationships are my co-founder's. Our first app for a client reached their production server in under three weeks from its first commit.

  • I built all of the company's infrastructure as code in git, and every day it is checked against what actually runs
  • No vendor lock-in: our first client runs in its own accounts and can take over operation without a migration
  • I rehearse restores one component at a time, and an alarm fires if a scheduled check goes silent

Who reaches what, no exceptions. On our VPN access goes by role: with the infrastructure role I reach the servers and the internal apps; the apps role reaches only the apps and does not even see the servers. Changes to the VPN access policy run allow and deny tests, and a change that would open the servers fails. A client's platform runs in the client's own accounts, where the client controls our access through a lock it holds. The animation shows the client closing it: my next request is refused and their system keeps running.

Build 2 of 6

in pilot with approved offices

Asistent veřejné správy

Role: Software Development Lead at DIA, August to October 2026

In late August 2026 I took over development of the Digital and Information Agency's AI assistant for civil servants: its web portal module, the Teams agent and their SDK. It was already in use, so I turned pilot code into maintainable code while it ran.

  • Gates first: within two weeks, no change in my scope could merge without passing the CI gates I added
  • Then cleanup and bug hunting by risk: each finding was challenged before I triaged it, and fixes landed test-first
  • In the product: I reworked streaming so tables stay intact, and long Teams answers now split without cutting a citation

Illustration of the three gates I added to the CI of the assistant's Teams agent within two weeks of taking over development, while the assistant was already in use: commit rules, version and changelog together, and no new warning in the code. Change B passes the first two and is sent back for one new warning. Change A passes all three and is merged into the main branch. Every change has to pass them, mine too.

Build 3 of 6

built September 2026, in daily use

Burrreau

A local control room for the Claude Code, Codex and Grok Build agents I run at once. It shows which session is waiting on me, what each one is doing and in which project.

  • One checklist brings together the decisions and manual steps my parallel AI sessions need from me
  • It reads hooks and the agents' own session records, never types into a terminal, and if it is down, the agent carries on
  • Designed and reviewed by me, written mostly by the agents it now watches

Demo sketch of the Burrreau board with invented data: agent sessions in columns by area, each marked as waiting on me, working or done. The one waiting on me carries a short checklist of what it needs from me, and the header counts how many sessions are waiting on me, working and done.

Build 4 of 6

since April 2026, closed beta, self-hostedin development

Brrroadcast

Turns the work people already do, in any field, into posts in their own voice. Notes, photos whose contents it extracts, a pasted AI chat or a coding agent feed one timeline. Nothing is posted by itself: the last step is a manual paste.

  • My rule for every way in: it must not ask the user to build a new habit
  • The author comments on exact passages; the next version answers each one: what changed, what was left on purpose
  • Setup starts with a questionnaire across fifteen roles, and Grok drafts the voice from the answers
The Brrroadcast landing page

Build 5 of 6

2025 to 2026

Platforms for the state and healthcare

Role: Cloud and platform engineer, observability consultant

For 21 months I was the main engineer of the Azure platform at EUC, the largest outpatient care provider in the Czech Republic. At the Ministry of Labour (MPSV) I built the cloud side of central logging; for DIA I wrote logging and tracing standards.

  • EUC: landing zones from empty subscriptions to production, and my own probe for the platform SLA
  • MPSV: I set the rules every supplier had to meet: one log schema and a reader group; each project has its own database
  • DIA: my standards for the suppliers of eDoklady, NIA and ISZR: follow the request, never log the user, not even hashed

Three diagrams of my work. EUC: a client team's change leaves its repository and passes a gate that lets only the team's own fields through. One IP address is added to the allowed list, while a change to the network stops at the gate and is ignored. The platform code is out of the team's reach, and the network, Key Vault and storage stay with the platform. MPSV: logs from suppliers A and B pass my schema, whose required part is the same for everyone, and land in each project's own database. Supplier C joins once it meets the schema and names a reader group. DIA: the rule I wrote, not a trace that already runs. Once the suppliers implement it, a request carries one trace code from the user through systems A, B and C, and an incident can be found by that one code. A hashed user ID is not allowed in the logs, because it is still personal data.

Build 6 of 6

finished April 2026, open source, MIT

Icebreaker

A cyberpunk roguelike you play in the browser: fifteen hacking minigames, meta progression and an in-game economy, with no backend at all. Most of the code came from AI. I wrote the spec and threw out what the game did not need.

  • Playable online within three days of the first commit
  • The core balancing formulas live in one module, covered by regression tests
  • A pull request without a version change fails its checks, and every push to main triggers a deploy
A screen from the Icebreaker game

also built

Trainee to lead before thirty

  • Projects, Audaron Solutions s.r.o.: First Client App, Audaron Infrastructure, Audaron Brand, audaron.com
  • Projects, Digital and Information Agency (DIA): Asistent veřejné správy, Observability for Government Information Systems
  • Projects, Self-employed: Burrreau, Kaer Trolde, Brrroadcast, Dotfiles, Grrreenhouse, Code to God Mode, Icebreaker, RRM Website
  • Projects, EUC a.s.: Azure Cloud Platform, SLA Monitoring and Self-Service Config, Certificate Automation and Upload Scanning
  • Projects, SLÍVKA Architects: Minion, ELWave
  • Projects, Ministry of Labour and Social Affairs of the Czech Republic: Centralized Logging & Audit Platform
  • Projects, ABB Group: Co-Pulse, FCM, Paperless Office, SW License App, PAPI ECS-MES, SharedDesks
  • Projects, XEVOS Solutions: VŠB Cooper, Canteen, Agregator
  • Projects, While at high school: CELogis, DESIGN STAR 2020-21, DDM Praha 10, AVRAR, Stora Enso

certified along the way

  • MicrosoftAZ-400Azure DevOps Engineer ExpertDecember 2025
  • MicrosoftAZ-204Azure Developer AssociateJune 2025
  • Education FirstC2English, CEFR proficiencyMay 2023
  • Mensa CRMensaMembersince December 2017

Don't believe me believe them

Recommendations in two moving rows. Hover or focus a card to pause its row.

Let's build.

how I work

  • B2B, even part of the week
  • Fully remote, Czech or English
  • Leading, still building
  • Decisions in writing
  • My own account, no shared passwords
  • AI tools, agreed up front

what I don't do

  • Employment contracts
  • On-site or hybrid
  • People management
  • Budgets and funding: counting other people's money
  • 24/7 on-call without a contract
  • Standups that could have been a message

I will say what a system costs to run; the budget behind it stays with the client.

Tailor my CV

Pick the language, theme and length, then choose what goes into the PDF.

include