About Micro Tech
We work on systems that can’t stop
We usually come in when part of a system can’t be touched, such as the schema or an old app that must keep running, and we change what sits underneath it.
{
"name": "Micro Tech",
"base": "Sarajevo, Bosnia and Herzegovina",
"shipping_since": 2020,
"clients_in": ["US", "Germany", "Sweden", "West Africa"],
"works": "remote · 9–18 CET · 4 h US/EU overlap",
"engagements": ["project", "long-term", "embedded lead"],
"downtime_policy": null
}We don’t touch what someone relies on.
Instead, we change what sits underneath it, and have done so for six different clients.
We put a safeguard where a mistake costs money.
Between an input and what it triggers sits a person or a mechanism: an operator, a type check, or a hold before anything runs.
We say when the answer would change.
We list the assumptions behind each option, so you can see when it stops being the right choice.
// Capability map
We have shipped systems in seven domains.
Each mark is a shipped system. Pick a domain to see the work behind it.
4 of 6 capabilities shipped
Regulated finance
- Client’s KYC product with liveness checks for the German market, sold at MVP stage
- Passport NFC chip read from React Native
- Six randomized verification steps, independently security-tested
4 of 6 capabilities shipped
Government ID
- Passport and ID issuance, offline in the field
- Monthly cloud bill cut from $24k to $2k
- Customs invoicing with immutable invoices
3 of 6 capabilities shipped
Healthcare under HIPAA
- Meetings platform with graph permissions in Neo4j
- Recording, transcription and signatures
- Client product sold to a US bank
4 of 6 capabilities shipped
Construction
- ERP alongside SAP: 150,000 items in 15 warehouses
- Crew planning by trade across countries
- Design system for 30+ brands, native Android modernization
5 of 6 capabilities shipped
Logistics and fleets
- Live marketplace rebuilt in four phases over four years, zero outages
- 2M+ analytics writes a day
- Five kinds of user in one codebase, 506 API routes
2 of 6 capabilities shipped
Retail data
- Data warehouse under a BI tool
- 15 min → 0.2 s without changing a query
- 200M+ products in the source system
4 of 6 capabilities shipped
Cross-border payments
- Remittances collected at 100+ POS terminals
- Payment partners in four markets
- Offline coupons valid only once confirmed
// How an engagement runs
Five steps, from the first call to the handover.
The steps advance on their own until you click one.
In one conversation, we find out whether we fit.
Tell us about the system, and we’ll ask which parts are off-limits, what an outage costs and who bears the consequences.
Where it happened
Since 2020, every engagement has come through someone who already knew our work.
We lay out three options, each with its price.
Once you decide, we write down the point at which the recommendation would change, so the decision can be revisited later.
Where it happened
A build-vs-buy review in 2026 recommended against building, which would have cost twice as much.
The system that earns money stops crashing.
Before anything is rewritten, we move the running system, add indexes, secure it and measure it. Only then do we decide whether it needs a rewrite.
Where it happened
Marketplace: stable on AWS within two months, with the slowest queries 90% faster.
The old system keeps running until nobody needs it.
The old and new systems run in parallel, synced in both directions, with a rollback that takes seconds. We switch off the old one only when the data says so.
Where it happened
Marketplace: old and new databases synced both ways for over a year, until the last user had left the old system.
Your team ships without us.
You keep a shared component library, coding standards written as rules that fail the build, and developers who have grown into full-stack engineers and ship features end to end.
Where it happened
Three developers, each with one specialty, grew into mid-level full-stack engineers.
What we don’t do
Things we say no to.
Projects that conflict with our values
We have turned down projects for this reason.
Rewrites for their own sake
We stabilize first and rewrite only when it is worth the cost.
Estimates presented as measurements
For example, the ~50% increase in team throughput once standards were checked in CI is marked as an estimate.
Client names
We describe engagements by sector and market and never name the client.
- years in production
- 6
- client systems
- 11
- case studies
- 18
- client products sold
- 2
- of clients via referral
- 100%
// Step 01 starts here
Thirty minutes is enough to know whether we fit.
Remote, or on site in Sarajevo.