Reference Overview
Selected References at a Glance
References should not deliver only names, logos or individual screenshots for us. What matters is whether a project reveals how data, roles, process logic, operation and expansion path truly interrelate. Precisely for that reason we do not present window dressing here, but solutions from which product line, client-server architecture, hardware relation and ongoing responsibility can be traced.
We present references with technical relevance
We are not inteRESTed in decorative demo projects, but systems that must perform in daily operation. Good references show whether a solution can genuinely handle roles, data, operational logic and further development.
A good reference also explains the operation behind it
A reliable reference shows not only the visible surface, but also permissions, hosting, edge cases, hardware relation, integrations and the path to later expansion stages.
Concrete references reduce technical decision risk
Those who read real references can more quickly determine whether a partner can merely present or actually deliver. Precisely for that reason these pages are intentionally detailed, technically clean and oriented to real project logic.
Selected references in detail
The following examples intentionally point in two very different directions. netScope represents scalable product development with viewer, team tiers, server and cloud. netNotdienst represents an operations-oriented enterprise solution with client, server, installation, status logic and real everyday suitability in pharmacy operations.
How we assess 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 calmly, extended and maintained across multiple expansion stages.
Domain processes must work in everyday operation
Whether data volume, multi-user operation or real hardware: the decisive question is always whether the solution operates reliably under real conditions and not just looks good in a shop window.
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 on this topic
Anyone who wants not only to view references but to assess them technically will find in the FAQ hub the appropriate answers on project size, architecture, portals, services and long-term operational responsibility.