At a glance
References at a glance
For us, references should not just provide names, logos, or individual screenshots. What matters is whether a project makes it clear how data, roles, process logic, operations, and the expansion path really fit together. That is exactly why we do not show window-dressing here, but solutions where product line, client-server architecture, hardware linkage, and ongoing responsibility can be traced and understood.
We show references with technical substance
We are not inteRESTed in decorative demo projects, but in systems that have to carry day-to-day operations. Good references show whether a solution can really handle roles, data, operational logic, and ongoing development.
A good reference also explains the operations behind it
A robust reference does not only show the visible interface, but also permissions, hosting, special cases, hardware linkage, integrations, and the path to later expansion stages.
Concrete references reduce technical decision risk
Anyone who reads real references can more quickly see whether a partner can only present or can also deliver. That is exactly why these pages are deliberately detailed, technically clean, and aligned with real project logic.
Selected references in detail
The following examples intentionally go in two very different directions. netScope stands for scalable product development with viewer, team tiers, server, and cloud. netNotdienst stands for an operations-close enterprise solution with client, server, system hardware, status logic, and real day-to-day suitability in pharmacy operations.
How we define strong references
Architecture must be readable
We want to be able to show how client, business logic, data storage, permissions, and operations work together. Only then does a project become a robust reference for new initiatives.
Operations must be considered
A project only becomes truly valuable when it is not only built, but operated calmly, extended, and sustained across multiple expansion stages.
Domain processes must work day to day
Whether data intensity, multi-user operation, or real hardware: the decisive question is always whether the solution works reliably under real conditions and not just looks good in a shop window.
You do not just want 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 long-term technical responsibility in concrete projects.
Read answers from the FAQ hub
Anyone who wants not only to look at references but to classify them technically will find the right answers in the FAQ hub on project size, architecture, portals, services, and long-term operational responsibility.