Reference Overview
Selected References at a Glance
Appropriate service and technology paths
Key deep dives on this topic
References should not, for us, merely provide names, logos or individual screenshots. What matters is whether a project reveals how data, roles, process logic, operation and the expansion path actually relate to one another. Precisely for that reason we do not show window dressing here, but solutions through which product line, Client-Server architecture, hardware relationships and ongoing responsibility can be traced.
We present references with technical substance
We are not inteRESTed in decorative demo projects, but systems that must carry everyday use. Good references show whether a solution can truly handle roles, data, operational logic and further development.
A solid reference explains the operation behind it
A robust reference shows not only the visible surface, but also rights, hosting, edge cases, hardware relationships, integrations and the path to later expansion stages.
Concrete references reduce technical decision risk
Those who study real references can more quickly determine whether a partner can merely present or actually deliver. Precisely for that reason these pages are deliberately detailed, technically precise and oriented to real project logic.
Selected references in detail
The following examples deliberately point in two very different directions. netScope stands for scalable product development with viewer, team tiers, server and cloud. netNotdienst stands for an operational enterprise solution with client, server, installation, status logic and real everyday 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, rights and operation interact. Only then does a project become a reliable reference for new initiatives.
Operation must be factored in
A project only becomes truly valuable when it can not only be built, but operated reliably, extended and sustained across multiple expansion stages.
Domain processes must work in everyday operation
Whether data intensity, multi-user operation or a real installation: the decisive question is always whether the solution operates reliably under real conditions and not only 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 durable technical responsibility in concrete projects.
Read answers from the FAQ hub
Those who want not just 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.
Next step
If you have a concrete modernization, API, or platform question, we should define the technical scope clearly and early.
Net-Base evaluates existing systems, data flows, interfaces and target platforms not in isolation but in the context of domain logic, operations and future extensibility.
- Current state, target state and technical risks are assessed jointly.
- REST, data access, portals and rollout are not deferred as afterthoughts.
- You can determine early which path is economically and operationally viable.