Skip to content
A right-aligned wall of technology names on a dark grid, with React, TypeScript, PostgreSQL, Node.js, Redshift, Docker, AWS and React Native standing out in teal.
Sarajevo · six years · available for new projects

We build and run systems that can’t stop

We come in where failure isn’t an option: customs invoicing, identity verification in banking, state document issuance, a HIPAA meetings platform, a construction ERP, and a US marketplace where we have held technical leadership for four years. Two of them were acquired as products.

See the case studiesStart a conversation
Zero
downtime across four migrations
2M / day
analytics writes, annual report under one second
$24k → $2k
monthly cloud spend
For context
$2.41T

the minimum cost of poor software quality in the US economy.CISQ, 2022

Selected case studies

Problem, constraint, measured outcome. Every page starts with what could not change.

Four re-platformings in four years. No user ever saw a page that didn’t work.

“MySQL was the only thing that could not move.”

Zero
outages across 4 phases
60 → 90+
Lighthouse; SEO 30 → 90+
90%
faster: the 20 slowest queries
Technical leadership · 2022–2026 · PHP, MySQL, React, Next.js, NestJS, AWS

A 15-minute report now opens in 0.2 seconds

“Neither the queries nor the schema could change.”

15 min → 0.2 s
the measured report, across 200M+ items
Architecture · US supplier to retail chains · 2025 · ongoing
How we work

Don’t break what someone already relies on. Change what sits underneath it.

The difference between ugly and expensive: every change to a surface someone relies on is paid for by someone else. We stabilize first and rewrite only when it is earned.

  • A failing PHP system was stabilized before the rewrite began — revenue did not wait two years for it.
  • MySQL kept as the only fixed point through four re-platformings.
  • A warehouse schema left untouched, so the customer’s saved reports worked the same day.
  • An ERP built next to SAP, not instead of it.

Four pieces of evidence for the same judgement, across three client systems.

Writes, live reads, and a year of history — pick three

“No single database does all three jobs.”

2M+ / day
writes; annual report under one second
Technical leadership · US marketplace for truck services · 2022–2026 · team of 12

Standards that fail the build

“A convention with no owner is a suggestion.”

~50%
team throughput, by ticket cycle
Technical leadership · same marketplace · 2026 · team of 12, fourth year

All 18 case studies

The full index — each one starts with what could not change.
All 18 case studies

Our products

Separate from client work

Alongside client work we build operational software for small companies in the physical world — the ones with vehicles, people in the field and paperwork that has to be right. Three layers of the same idea.

  • Financial platform

    Profitability tracking for small companies, entered through VAT preparation for their accountant. The data the accountant enters anyway fills the reports, so the company never starts from an empty screen.

    Stands on an ERP with inventory, suppliers and invoicing (2025).

    Application ready · first users in the first quarter
  • Identity OS

    Identity verification as infrastructure — orchestration and user consent on top of existing vendor services.

    A continuation of a KYC system for a financial institution (2020) and a state document issuance system (2024) — both ends of the identity chain.

    In development
  • Fleet platform

    Fleet management and telematics for rental companies, with vehicle data available for the duration of a rental. Identity OS is its first internal consumer.

    Developed with our own fleet as the test environment; five fleet and driver dashboards built 2022–26.

    Hardware acquired · integration next

None of them has a user other than us yet. That changes in the first quarter.

About

Six years building systems that can’t stop, from Sarajevo for clients in the US, Germany and Sweden. Eighteen case studies, two products sold, four years of technical leadership.

We don’t write components to a specification. We come in where the constraint is already set — the schema can’t be touched, the queries aren’t ours, the old app can’t be switched off — and look for what can change underneath it.

Full background →
Don’t touch what someone relies on
Four pieces of evidence across three client systems.
Software for the physical world
POS terminals at filling stations, warehouses with 150,000 items, sites in several countries, telematics.
Identity and documents in regulated systems
Customs, German finance, HIPAA, state identity — both ends of the chain.

Have a system that can’t stop — or are you still building it?

A single 30-minute conversation, no obligation, is enough to know whether we fit. We reply within one business day.

Start a conversation

Systems that can’t stop — from architecture to production.

© 2026 Micro Tech, Sarajevo