Technologies
Technology is a tool, not a goal
In our projects we mainly use Java and Spring Boot on the server side and Angular and TypeScript in web applications. We choose the architecture to fit the process, scale, security requirements and maintainability, not the other way round.
What for, not just what
Every technology has a specific job with us
A list of logos says little about how a system is built. Below we show what each part of the stack is responsible for in our projects.
| Area | Technologies | Why we use them |
|---|---|---|
| Backend | Java, Spring, Spring Boot | Durable server-side processes, business logic, REST services and integrations. |
| Frontend | Angular, TypeScript, JavaScript | Responsive, rich form-based and operational interfaces: panels, data tables, dashboards. |
| Data | Microsoft SQL Server, PostgreSQL | A consistent data model, transactions and controlled migrations. |
| API | REST, JSON, XML | Data exchange between applications and enterprise systems. |
| Identity | Keycloak, SAML 2.0, Active Directory, Microsoft Entra ID, LDAP | Fitting an application into the existing identity and single sign-on ecosystem. Scope depends on the deployment. |
| Environment | Microsoft Azure or client infrastructure | Matching the deployment to requirements for availability, data location and the way it is maintained. |
| Source data | Excel, CSV, batch imports | Unifying information from systems of differing maturity: validation, mapping, transformation. |
| Maps | OpenStreetMap | Spatial data in applications for field work and linear investments. |
A practitioner’s view
How we choose an architecture
The systems we build live for a long time and work alongside others: ERP, user directories, databases and applications from years ago. So the choice of technology starts with questions about the process and its surroundings, not with what happens to be fashionable.
- Where the system should run. On-premise, in Microsoft Azure or in a hybrid model. Requirements for availability, data location and who will maintain the solution decide.
- What it has to talk to. We design the boundaries of responsibility between systems and retry mechanisms so that a repeated message does not create a duplicate and the failure of one system does not stop the others.
- Who signs in and what they can see. Role-based access control, change auditing and protection of data in transit are part of the architecture from day one.
- Who will take over maintenance. We choose mature, well-documented technologies that will still be easy to staff several years from now.
We use the same tools in our own products: sara.next, SGSync and whiblo. We therefore know them not only from building but also from years of maintaining them.
A good technology stack is one nobody has to think about five years later.
The criterion that guides our choiceQuality and security in a project
- Manual and automated tests matched to the nature of the project
- API, integration, regression and acceptance tests
- Code reviews and dependency control
- Roles, permissions and change auditing
- Monitoring and updates after rollout
Systems with history
We also know the technologies companies want to leave behind
We do not assume a client starts from empty infrastructure. We maintain older environments and move them to a modern architecture.
HCL Notes / Domino
Maintenance and development of applications, database analysis, migration of data and business logic, replatforming.
MoreMS Access
Moving forms and logic to web applications with a central database.
MoreFoxPro
Analysis of older systems, reconstruction of rules and gradual migration.
MoreJBoss, WildFly, .NET
Maintenance skills in the environments where our clients’ older systems run.
MoreA question about a specific technology?
Tell us what environment you work in. We will say plainly whether it is our area and how we can help.





