For software already in production

Keep the system. Hand us the responsibility.

We stabilize live software and keep it shipping, without a rewrite.

Tell us about your system See what we run

With our partner E Galactic e.U., we have built and maintained MaxPlayer since 2020. 1M+ people use it.

What we run today

Systems we built and still answer for.

Most of what we run, we wrote from the first line and have maintained ever since.

  1. Austria With our partner E Galactic e.U.

    MaxPlayer

    A media player 1M+ people use on phones, computers and TVs. We still develop it and run the backend behind it.

    • Go
    • TypeScript
    • React Native
    Read the case study

  2. Bosnia and Herzegovina For Antena Net DOO BELGRAND

    BELGRAND ScoreMaster

    The mobile app and, later, the desktop software that drive live LED scoreboards at sports events. Desktop releases go through more than 1,700 automated tests and a beta channel, with the previous version kept for rollback.

    • TypeScript
    • Electron
    • React Native
    Read the case study

  3. Serbia Our own product

    Arhivix

    Our document platform, used by 500+ companies. We build it and run it ourselves, from the Go services to the desktop and mobile apps.

    • Go
    • Svelte
    • React Native
    Read the case study

Our home stack is Go and TypeScript. What we have not built

If you hand us yours

How it goes, in order.

Nothing gets rewritten in the first month. Each step builds on practices we already use on the systems we run.

  1. 01Before you commit

    A Technical Review

    • One to two weeks with read-only access.
    • A map of the system and a list of its risks, worst first.
    • A plan and a fixed price for what comes next. You can stop there.

  2. 02Week 1

    The keys move to you

    • Code, cloud, domains and payment accounts under accounts you control.
    • Secrets rotated and old access closed.
    • A clean build from an empty machine.

  3. 03Weeks 2 to 4

    Make it safe, then fix the worst

    • Backups checked, and alerts that reach a person.
    • The top risks fixed first, each change shipped with a way back.

  4. 04Every month after

    It keeps running, in writing

    • Releases through a test channel, with the previous version kept for rollback.
    • A written report every month: what we fixed, what we changed and the hours it took.

Before you forward this

Straight answers.

Who answers for it

  • Nemanja Marjanov Co-Founder & CEO. Leads engineering; the architect behind Arhivix.
  • Dragan Gavrić Co-Founder & CEO. Leads client delivery.

A Notix team does the work. Both of us answer for every system we run.

What we have not done yet

  • Most of what we run, we built from the first line.
  • We do not hold a SOC 2 or ISO 27001 certification yet.
  • We have not done technical due diligence for an investor yet.
  • If a rewrite is the better call, you will hear it in the review, not after the contract.
Everything we have not built

FAQ

Common questions.

Tell us about the system you need someone to answer for.

The first call is free, and on it you will hear whether we are the right team.

Tell us about your system Prefer email? [email protected]