Technology

From the sensor to the control room.

All our products follow the same engineering approach: integration over open protocols, systems that show what they're doing, modules that don't bring each other down, and infrastructure your team can take over.

.NET / APIReact PlatformsAI & Computer VisionMQTT / Modbus / IoTCloud & EdgeReal-Time SystemsObservabilitySecurity from Day One

Four-layer architecture

The chain from the device in the field to the user's screen is built in four layers. Each layer can be changed on its own; renewing one part doesn't stop the others.

Business ApplicationsDashboards, mobile experiences, reporting and workflows.
UI
User ExperienceFast, focused interfaces for daily operations.
AI & Decision LayerInference, automation, assistants and analytics services.
AI
Real-Time IntelligenceEvents, alarms, rules and context in motion.
Platform ServicesAPI, identity, workflow, integration and data services.
API
Secure IntegrationERP, CRM, industrial equipment and third-party platforms.
Edge & DevicesPLCs, sensors, cameras, gateways and field devices.
IoT
Cloud InfrastructureElastic workloads, storage, observability and deployment.

Technology stack

We don't chase trendy technology. What the tools we pick have in common: they last, our team knows them in depth, and the client's team can take them over.

Application and API

  • .NET / ASP.NET Core
  • Entity Framework Core
  • REST API
  • SignalR (real-time)
  • Hangfire (scheduled jobs)
  • JWT and role-based access

Front end

  • React + Vite
  • TypeScript
  • Astro (corporate sites)
  • Design tokens
  • Accessibility audits
  • Responsive layout

Mobile

  • React Native / Expo
  • iOS + Android single codebase
  • Background location
  • Push (FCM / APNs)
  • Offline queue
  • Camera and photo evidence

Data

  • PostgreSQL
  • Redis (cache)
  • Time-series storage
  • Reporting engine
  • Excel export
  • Data migrations

Industrial connectivity

  • OPC UA
  • Modbus TCP / RTU
  • MQTT
  • PLC drivers
  • Edge gateway
  • Meter and sensor reading

Infrastructure and operations

  • Docker
  • Windows Server / IIS
  • Linux
  • Backup and recovery
  • Log and metric collection
  • Release and deployment pipeline

Systems we connect to

None of the systems we build live on their own. The invisible part of integration is error handling: where data waits when a transfer fails, and who gets notified, is designed up front.

Enterprise systems
ERP (Netsis and similar)Accounting softwareCRMHR systemse-Invoice / e-Waybill
Field and devices
PLC and HMISensors and metersCameras and imagingBarcode / QR readersLicense plate recognition
Communication channels
SMTP / e-mailWhatsApp BusinessTelegramPush notificationsWebhook
Identity and access
LDAP / Active DirectorySign in with GoogleSign in with AppleOIDC / SSORole-based access

Security and data management

Security isn't a feature added later; it is part of the architecture from day one. In systems running in critical environments, the answer to "who changed what, and when" must always be at hand.

Role and permission separationUsers only access the data they need for their job; permissions are managed in one place.
Audit trailCritical actions are recorded with who did them and when.
EncryptionData is protected with TLS in transit and at the storage layer at rest.
Session managementShort-lived access tokens, a refresh flow and termination of suspicious sessions.
Backup and recoveryRegular backups, recovery drills and a version rollback plan.
Separate environmentsDevelopment, test and production are isolated; no testing with live data.

Deployment options

Most industrial clients want a clear answer about where their data lives. We support all three deployment models; the choice is made together based on the product and regulations.

Cloud

We run the system; you simply use it.

  • No installation effort
  • Automatic updates
  • Access from anywhere
  • Monitoring handled by us
Who it's forOrganizations without their own server team that want to start quickly.

On-premise

The software runs on your servers; data never leaves the building.

  • Data stays with you
  • Runs on a closed network
  • Easier regulatory compliance
  • Your own backup policy
Who it's forSites whose data cannot leave the premises, and public-sector work.

Hybrid

The field runs at the edge; management and reporting in the cloud.

  • Field keeps running if the internet drops
  • Central reporting
  • Edge data processing
  • Multi-site
Who it's forOrganizations that want to monitor distributed sites from one center.

Our engineering principles

Each of our products does a different job; what they share is how they are built.

ObservabilityWhatever the system does must be visible: logs, metrics and traces are designed in from the start.
No silent failuresA failed operation waits in a queue and triggers a notification; it never disappears quietly.
Modular servicesChanging one part doesn't stop the others; boundaries are drawn clearly.
Security from day onePermissions, encryption and audit trails are foundations, not add-ons.
Edge to cloudData is processed at the source and consolidated centrally; when the connection drops, it waits at the edge.
Hand-over readyThe client's team must be able to take over what we build; we document it and transfer the knowledge.

Frequently asked technical questions

Do your products run on our own servers?

Yes. We support cloud, on-premise and hybrid deployment. On-premise, the software runs on your servers and data never leaves the building; it can also be commissioned on a closed network.

Can you connect to our existing ERP and accounting system?

If the system has an API, we connect directly. If not, we integrate through file-based transfer, a database view or robotic process automation (RPA) on the user interface. Every transfer is logged and faulty records wait in a queue.

Is field data lost when the internet goes down?

Not for outages within the buffer capacity. Field apps and edge gateways keep an offline queue; when the connection returns, data is sent to the center in order. In a hybrid setup, field operations keep running regardless of connectivity.

Where is the data stored?

It depends on the deployment model: on your own server for on-premise, and in the region set out in the contract for cloud. If the geographic location of data matters for regulatory reasons, we settle it at the start of the project.

Can our own team take over the system?

That's what we aim for. Architecture decisions, the data model, installation steps and maintenance notes are documented, and a hand-over session is held with your team at delivery. A system that can't be handed over isn't finished in our eyes.

How do source code and licensing work?

In custom development the source code is handed over to you with the installation documentation, and it is yours. For products, the license grants a right of use. Which model applies is set out in writing at the start of the project.

Let's talk about your architecture.

We'll hear about your current system and decide together where to start.

Request a Call →See Services