mbranch

Software built by the two people who will keep it running

mbranch is a two person development studio in Riga. We build web and mobile products and stay on after launch.

Book a call

The four kinds of work we take on

New products, built from nothing

For a company whose process has stopped scaling. We agree the smallest version that is genuinely useful, build it, and put it in front of real users.

Codebases another developer left behind

We read what is there, write down what it actually does, and give you a plan with real numbers before we change a line.

Applications people use on a phone

One React Native codebase for both stores, with offline behaviour designed in from the start. We handle store submission and review.

Keeping software running after launch

A monthly arrangement for software we built or audited: updates, monitoring, backups that are restored on a schedule, and small changes.

Projects we can show

Most of what we build sits behind a login and an agreement that does not allow us to show it, so this list is short.

  • Image of Placeholder project one

    Placeholder project one

    Replace this entry with a real project. One or two sentences on what it is and who it is for.

    Open the project, opens in a new tab
  • Image of Placeholder project two

    Placeholder project two

    An entry without a link. Cards without one are plain and not clickable.

  • Image of Placeholder project three

    Placeholder project three

    Delete the three placeholder files before the site goes live. The section hides itself when the folder is empty.

Two developers in Riga, trading as SIA FqvB

mbranch is the name on the work. SIA FqvB is the name on the invoice. There is no bench and no delivery manager: when you hire mbranch you get both of us, and the person who wrote a piece of code is the person who answers when it breaks.

The name comes from how we work. Every piece of work is a branch off main, read by the other of us, and merged only when we would both be willing to explain it a year later.

How a project runs

  1. A call, then the scope in writing: what we would build first, what we would leave out, and what it costs.
  2. Something running within two weeks, deployed where you can open it on your own phone.
  3. A build you can click every second Friday, with a short note on what changed.
  4. A handover written as though we are leaving: repository, infrastructure, accounts, and a document.

What we build with

  • TypeScript, and Go where a service needs to be small.
  • PostgreSQL, and SQLite on devices that go offline.
  • React on the web, React Native on iOS and Android.
  • Docker and Terraform, hosted in the EU unless you ask otherwise.

Book a thirty minute call

Tell us roughly what the problem is. We will say what we would do first, what it costs, and whether we are the right studio for it.

Or write to us directly.

A few sentences is plenty. What exists today and what should be true in six months.

What happens to your details is in the privacy notice.