References
Selected References — Overview
Appropriate service and technology paths
Key deep dives on this topic
For us, references should not only provide names, logos or individual screenshots. What matters is whether a project reveals how data, roles, process logic, operations and the expansion path actually interrelate. Precisely for that reason we do not present window dressing here, but solutions from which product line, client-server architecture, hardware relationships and ongoing responsibility can be traced.
We present references with technical relevance
We are not interested in decorative demo projects, but in systems that must carry the everyday load. Good references show whether a solution can reliably 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 relations, integrations and the path to future expansion stages.
Concrete references reduce technical decision risk
Reading real references makes it easier to tell whether a partner can only present or can also deliver. That is why these pages are deliberately comprehensive, technically precise and aligned with real project logic.
Selected references in detail
The following examples deliberately point in two very different directions. netScope represents scalable product development with viewer, team tiers, server and cloud. netNotdienst represents an operationally close enterprise solution with client, server, hardware system, status logic and genuine 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 operations interact. Only then does a project become a reliable reference for new initiatives.
Operations 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 work in everyday operation
Whether data intensity, multi-user operation or real hardware: the decisive question is always whether the solution operates reliably under real conditions and not only looks good in a showcase.
You want more than an agency—you want 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 related answers in the FAQ center.
Anyone who wants not only to view references but to assess them technically will find in the FAQ center the appropriate answers on project size, architecture, portals, services and long-term operational responsibility.
Next step
If you have a concrete modernization, API or platform question, we should establish the technical scope clearly and early.
Net-Base evaluates existing systems, data paths, interfaces and target platforms not in isolation, but in the context of domain logic, operations and future expansion.
- Current state, target state and technical risks are assessed jointly.
- REST, data access, portals and rollout are not deferred to a later stage as secondary consequences.
- You can see early on which path is economically and operationally viable.