Döbling

Signal origin · 49.0°N 8.4°E · Earth

Martin Döbling

Independent software engineer — three live worlds, one operator.

I take a thing from the first sketch to the running system: the schema, the interface, the billing, the deploy at two in the morning. No committee, no handover document, no waiting for the platform team. What follows is what is currently in orbit.

Descend into the system Open a channel
Scroll to descend

Catalogue · three bodies · all inhabited

Everything here
is live.

Not case studies. Not concepts in a slide deck. Three products with real users, real invoices and real 3 a.m. incidents, each one built end to end.

World I — Velox

flitzerr.com

On-site help, fixed price, today

“Help on-site — today, not next week.”

Locked out, broken down, moving on Saturday. Flitzerr collects offers from local providers with a fixed price and an arrival time attached before you commit to anything — then tracks the van and settles the payment. Providers pay for the job they got, not the lead they might have gotten.

  • 10 categories, from roadside rescue to removals
  • Fixed price and arrival time before booking
  • Live tracking and in-app payment
  • Südpfalz & Karlsruhe — 9 cities and widening
  • 15% per job. No base fee, no lead costs

World II — Terra Communis

campusverleih.de

Inventory & lending platform for universities

“No Excel. No paper forms. No chaos.”

Every student council on the planet runs its equipment on one spreadsheet that exactly one person understands — and that person graduates. CampusVerleih turns the whole ritual into software: catalogue with photos, loan requests with real availability, approvals, overdue reminders, and a full audit trail nobody has to keep by hand.

  • QR handout & return from any phone
  • Role-based access, per council or campus-wide
  • CSV import for the inventory that already exists
  • EU-hosted, GDPR-native, free for small councils
  • 10% of revenue → Wikimedia Deutschland

World III — Circuitum

briskpcb.com

AI hardware design, description to fabrication

“Describe your board. The AI builds it.”

A sentence goes in. A manufacturable board comes out. BriskPCB places real parts, wires the circuit, remembers the decoupling caps and the pull-ups you forgot, runs ERC, and derives schematic and layout from one single model so the two can never drift apart.

  • Gerbers, BOM and pick-and-place in one export
  • Community catalogue across 16+ part categories
  • Fork a component, improve it, publish it back
  • Straight to the fabricator, no round trip
  • One model — schematic and PCB never disagree

Operating principles · not a mission statement

Six rules
I actually ship by.

  1. 01 Nothing ships that cannot be rolled back with one command.
  2. 02 A health check decides whether a deploy stands, not my confidence in it.
  3. 03 If it cannot be exported, it is not owned. Gerbers, BOM, CSV — the way out stays open.
  4. 04 Every config says why it looks the way it does, especially when an outage is what shaped it.
  5. 05 The data sits on hardware I can physically reach.
  6. 06 No tracking. One cookie, and only if someone switches language.

None of this was read somewhere. Most of it is the residue of something that broke — a deploy with no way back, a container that could not boot because the old one still held the port. Writing the rule down is cheaper than having the same outage twice.

Open channel · response within one rotation

Say something
into the dark.

[email protected]

Building something that does not exist yet, need a fourth world in the system, or just want to tell me the shader is too much — the channel is open.

© 2026 Martin Döbling · Independent

SvelteKit · one fragment shader · no tracking, no analytics, one cookie only if you switch language