About · Engineering-focused software publisher

A publisher, not a product.

RedLine publishes software that makes the path from a question to its answer visible. Its first work is Utility Forge: a small ecosystem of Windows utilities that each answer one concrete question.

How the names fit together

  1. Publisher

    RedLine

    Engineering-focused software publisher. Develops focused software; no public application releases yet.

  2. Ecosystem

    Utility Forge

    Focused Windows utilities with one shared trust model and release pipeline.

  3. Products · shipping order
    1. PortWho In development
    2. FileScope In development
    3. Tidy In development
    4. NetDoctor In development

Who is behind it

The tools are designed and built by Mundoin, an independent developer based in Germany. The publisher is a neutral brand backed by a visible real person, because that is the model people can actually hold accountable: you know who wrote the software you are running.

RedLine is the display brand. Mundoin is the developer alias. The legal operator is Bujar Saciri; provider details are in the Impressum.

How the work is done

One repository holds the website, each application, shared libraries, tests and the continuous-integration configuration. It remains private. Source code, internal CI results and the issue tracker are not publicly accessible. Changes enter through pull requests, Windows applications are built and tested on Windows runners, and the website is deployed only from the main branch after a merged pull request.

The product strategy is written down in a canonical blueprint that fixes the active products, the website architecture, the release pipeline and the trust model. A product slot stays empty until there is evidence for a tool worth building. New ideas are measured against it and against real evidence: site searches, guide traffic, support requests and feedback.

What you will not find here

No PC optimizer, registry cleaner, RAM cleaner, driver updater, antivirus or generic AI wrapper. Those categories are either risky, commoditised or already solved well by others.

General notes

Product principles

Unless otherwise specified, these apply to every product.

  1. One job first

    A product solves one coherent family of problems. Features grow to support that job, never to turn a utility into a suite.

  2. Explain before acting

    Tools inspect, identify, compare and preview before they change anything. Many never change anything at all.

  3. Safe mutation

    When a tool does change state: preview, validation, explicit execution, an operation journal, and undo wherever technically possible.

  4. Least privilege

    Run as a normal user. Elevation happens for the operation that needs it, not as the default state.

  5. Local first

    Core functionality works without sending your data anywhere.

  6. No junk

    No bundled software, advertisements, fake download buttons, forced accounts, countdowns, optimizer claims or always-online DRM.

The catalog