Built by engineers who have lived through QES complexity

More than 10 years ago, QES workflows were entirely local.

Signing meant:

• installing drivers manually
• dealing with USB tokens and smart cards
• debugging OS-level issues
• integrating directly with provider-specific libraries

Every system was tightly coupled to:

• a single provider
• a specific device
• a specific operating system

There was no abstraction layer. Every integration was custom.

We built those systems.

As QES adoption grew across Europe under eIDAS Regulation, complexity didn’t decrease - it multiplied.

Different countries, providers, and workflows introduced:

• incompatible APIs
• different signing formats, including XML and PDF
• hardware and remote signing models
• varying operational requirements

Even within markets like Bulgaria and Romania, multiple trust providers and device types had to be supported simultaneously.

Teams were rebuilding the same logic over and over again.

Every product team was becoming a QES infrastructure team - whether they wanted to or not.

Before starting QES Development company, we delivered multiple custom QES implementations for:

• healthcare platforms
• enterprise systems
• regulated integrations with national services
• multi-provider signing environments

One of the most complete examples is the Medentic system:

• desktop application for local signing
• secure socket communication layer
• API-based orchestration
• support for multiple QES providers
• XML and PDF signing workflows

All connected into one working system used in production.

After years of building custom solutions, one thing became clear:

The problem is not signing. The problem is the lack of a unified signing layer.

So we built it to provide:

• a consistent integration model
• a reusable signing infrastructure
• a bridge between local devices and cloud systems
• a way to support multiple providers without rebuilding everything

We build the infrastructure that removes friction between your product and qualified electronic signatures.

So your team can focus on your product - not on:

• token drivers
• desktop communication
• provider inconsistencies
• signing edge cases

Our product provides:

• a unified API for QES workflows
• a secure cloud-controlled orchestration layer
• a desktop bridge for hardware-based signing
• support for XML and PDF qualified signatures
• diagnostics, logging, and operational tooling

The goal is simple:

One integration layer for complex QES systems.

Even as QES moves toward cloud and remote signing, local devices and hybrid workflows remain critical.

Certified devices like USB tokens and smart cards are still widely used and required in many environments.

Because we built systems in the old world, we understand:

• where things break
• why they fail in production
• how to design around those realities

That experience directly shapes how we build today.