For us, references should not be limited to names, logos or single screenshots. Crucial is whether a project makes it possible to see how data, roles, process logic, operation and the extension path actually interrelate. That is why we do not present window-dressing here, but solutions from which product line, client-server architecture, hardware relations and ongoing responsibility can be traced.
We present references with technical significance
We are not inteRESTed in decorative demo projects, but in systems that must perform in everyday operation. Good references demonstrate whether a solution can actually handle roles, data, operational logic and ongoing development.
A solid reference also explains the operation behind it
A reliable reference shows not only the visible surface, but also permissions, hosting, edge cases, hardware dependencies, integrations and the path to later expansion stages.
Concrete references reduce technical decision risk
Those who read real references can more quickly tell whether a partner can only present or can also deliver. That is why these pages are deliberately detailed, technically precise and oriented toward real project logic.
Selected references in detail
The following examples deliberately head in two very different directions. netScope stands for scalable product development with viewer, team tiers, server and cloud. netNotdienst stands for an operations-near enterprise solution with client, server, installation, status logic and real everyday suitability in pharmacy operations.
How we judge strong references
Architecture must be readable
We want to be able to show how client, business logic, data storage, permissions and operation interact. Only then does a project become a reliable reference for new initiatives.
Operation must be considered
A project only becomes truly valuable when it is not only built, but can be operated reliably, extended and sustained across multiple expansion stages.
Domain processes must function in everyday operation
Whether data intensity, multi-user operation or real equipment: the decisive question is always whether the solution works reliably under real conditions and not merely looks good in a showcase.
You want not just an agency, but demonstrable technical substance
Then these references are the right starting point. They show how we implement product development, client-server systems, real process logic and lasting technical responsibility in concrete projects.
Read answers from the FAQ hub about this
Anyone who wants not only to view references but also to classify them technically will find the appropriate answers in the FAQ hub on project size, architecture, portals, services and long-term operational responsibility.