Support QES and AdES in your software, without the implementation complexity

We provide the signing infrastructure and delivery support behind complex eIDAS workflows, from hardware and cloud signing to a single unified API for integration into your product.

Book a Discovery Call

Hardware and cloud signing.

Sign Device (HSM)

Desktop App

John Doe (Acme Inc)

Issuer: B-Trust (BORICA AD)

Valid to: 2026-12-15 (320 more days)

Ivan Doe

Issuer: Info Notary

Expires in 12 days (2025-02-14)

Elena Todorova

Issuer: StampIT

Enter PIN to unlock

Unified API Connected

PDF and XML workflows.

Your Software

Loading...

Unified API

Integrate desktop signing, secure devices, cloud signing, and qualified document workflows through one maintainable API layer.

Native OS Support

Hardware Signing

Support smart cards, HSM-backed flows, and desktop-dependent signing.

Cloud Signing

Handle remote signing workflows through the same integration model.

Multi-format signing

Support PDF (PAdES), XML (XAdES), ASiC, CAdES, DOCX, XLSX, and JSON workflows.

Multi-format signing

Support PDF (PAdES), XML (XAdES), ASiC, CAdES, DOCX, XLSX, and JSON workflows.

Platform

Infrastructure for production-grade signing workflows

Connect your product through one unified signing layer that supports desktop-connected local QES signing, cloud signing workflows, workflow orchestration, and broad QTSP coverage across eIDAS markets.

Unified Signing Layer

Connect your product through one integration surface for local signing, cloud signing, and qualified signing workflows

QTSP Integrations

Support multiple qualified trust service providers through one signing layer, with broad provider coverage across eIDAS markets.

Workflow Automation

Orchestrate end-to-end signing workflows across desktop devices and cloud systems.

Desktop Bridge

Run a dedicated desktop bridge for local QES signing, secure device access, and guided user signing flows.

Cloud Signing

Run cloud signing workflows through a production-ready service layer with controlled rollout and operational support.

+32

Use Cases

Built for high-friction QES workflows

Designed for software teams and regulated environments where QES signing must work across local devices, provider integrations, and production workflows without becoming a systems burden for the product team.

Connect clinicians, desktop signing environments, local QES devices, and regulated healthcare systems through one reliable signing workflow built for everyday operations.

Native IDE Support

Embed QES signing into your product through one maintainable integration layer instead of accumulating provider-specific logic, desktop complexity, and country-by-country signing debt.

SOC 2
ISO 27001
GDPR
99.9% uptime

Support workflows where qualified XML signing, secure communication, document submission, and local execution all need to work together inside one controlled process.

“Looks really good. Did you design in code or Figma first?”

Case Studies

Driving digital signing adoption in real workflows

Examples of how we help companies bring QES signing into everyday operations through production-ready workflows, local-device support, and cloud-connected signing infrastructure.

We built Medentic's signing infrastructure around a unified layer that connects hardware QES devices, desktop software, and regulated healthcare submissions into one workable production flow.

MedenticHealthcare SaaS

Unified Signing LayerDesktop BridgeCloud Signing

Outcome 01

Desktop-connected QES signing for regulated healthcare workflows

Outcome 02

Secure submissions to HIS.bg and NHIF.bg through one cloud-connected signing layer

Explore case studies

Capabilities

What qes.dev supports

A focused capability layer for teams that need QES signing to work across local devices, regulated formats, and production workflows.

Hardware-token signing

Support smart-card and hardware-token signing scenarios where qualified signatures depend on secure local devices.

Memory Usage

56 GB / 128 GB45%

Desktop signing workflows

Run signing flows across Windows, macOS, and Linux when local execution is required for QES operations.

PDF signing and validation

Implement qualified PDF signature workflows together with trust-aware validation and verification steps.

Qualified XML signing

Support XML-heavy workflows where structured document signing and regulated exchanges are part of the operational process.

Unified API orchestration

Coordinate product systems, local signing environments, and workflow execution through one maintainable integration model.

Cloud-controlled workflows

Manage signing orchestration, workflow control, and service delivery through a cloud-connected signing layer.

Frequently asked questions

Qualified-signature infrastructure usually raises technical, operational, and scope questions early in the buying process. These are the questions we expect most often from product, engineering, and operations teams.

Can't find what you're looking for? Contact our customer support team

Integrate QES or EUDI Wallet with confidence.

Build an eIDAS-compatible signature flow.

Design your qualified-signature workflow properly from day one

Bring your workflow, product constraints, and integration challenges. We help you design and deliver a production-ready QES or EUDI Wallet implementation - across providers, devices, and eIDAS requirements.

Book discovery call

Support QES and AdES in your software, without the implementation complexity