Technical catalogue

The components behind our solutions.

For each component, we show the data it accepts, the work it performs, the result it hands over and the systems it connects to.

Simple building blocks connected into one working process

SIFYBOX

Workflow, documents, funding, signatures and storage.

OODSIFYBOX

Document workflow and organisation

SIFYBOX's flagship workflow component turns a form, document or request into a controlled case. It manages steps, roles, deadlines and audit, and can connect the case to registries, finance, signing, storage and records systems for the confirmed deployment.

Input
Dynamic form and attachments
Outcome
Decision and new status
REST API · DOG · FS · ZST · EPK · CULOpen detail
DOGSIFYBOX

Document generation

Combines structured data, such as JSON from a workflow or business system, with a user-managed DOCX or XLSX template. Documents are generated consistently without manual rekeying.

Input
Data from OOD or another system
Outcome
DOCX or XLSX
OOD · EPK · CULOpen detail
FSSIFYBOX

Funding sources

Connects funding sources and approval rules to the authoritative finance system, recording how an operation is funded, who may approve it and what status the finance system actually returned.

Input
Finance dimensions and sources
Outcome
Approval, rejection or return
EIS: iFIS, JASU, SAP or Business Central depending on deployment · OOD · EPKOpen detail
ZSTSIFYBOX

Delegation

Keeps workflows moving during absence without sharing an account or changing permanent rights.

Input
Delegating and delegated person
Outcome
Temporary role delegation
OOD · FS · EPKOpen detail
EPKSIFYBOX

Electronic signature book

Gives leadership one place for everything they must approve or sign across business systems. Executives no longer need to open dozens of applications just to discover whether a task is waiting.

Input
Document and metadata
Outcome
Decision and status
OOD · WSCS / signing service · CULOpen detail
WSCSSIFYBOX

Document preview, signing and redaction

Adds secure document preview and PDF actions to a web application. Depending on the confirmed configuration, users can review, sign or prepare a redacted copy without leaving their business system.

Input
PDF document
Outcome
Signed PDF
EPK · REST API · Signing toolsOpen detail
CULSIFYBOX

Central trusted storage

Acts as a shared, often invisible document layer. Binary content is kept separately from business metadata and versioned under a stable GUID, so connected applications can exchange one controlled reference instead of copying files repeatedly.

Input
Document and metadata
Outcome
Stable GUID and link
CUL WS · OOD · EIS and domain applicationsOpen detail

Integration examples

The workflow connects to systems your organisation already uses.

Read, write and return-status capabilities are confirmed for the customer’s product, version and interface.

Finance systems

  • GINIS
  • iFIS
  • SAP
  • Microsoft Dynamics 365 Business Central
  • JASU
  • ABRA Flexi — in development

HR and payroll

  • EGJE
  • VEMA

Identity and sign-in

  • Microsoft Entra ID and Microsoft Graph
  • Keycloak, OpenID Connect and SAML 2.0
  • Shibboleth and CAS (Jasig / Apereo)
  • NIA and CAAIS for public officials
  • LDAP

Remote signing through WSCS

  • Software602 SecuSign
  • CESNET Remote Signature (ReMSig / eIDAS)
  • SEFIRA OBELISK Remote Signature
  • Other services with a suitable interface after technical validation

Research and education

  • Moodle
  • IS/STAG and SIS
  • DSpace and Zenodo
  • Web of Science and Scopus
  • SHERPA/RoMEO / Open Policy Finder

Documents and reference data

  • Online editing in ONLYOFFICE and Microsoft 365
  • ARES
  • Czech National Bank exchange rates
  • Czech contract register (ISRS)

Operational baseline

Databases, observability and delivery belong to operations—not the integration list.

The exact combination is confirmed by the release manifest and customer architecture. New deployments are designed so the customer controls updates from inside its environment without opening inbound deployment access.

Databases

  • PostgreSQL
  • Oracle Database
  • Microsoft SQL Server

Monitoring and logs

  • Zabbix monitoring
  • Grafana and Loki for metrics and logs
  • Sentry for application errors

Passwords, keys and certificates

  • HashiCorp Vault
  • Docker secrets or access-controlled files depending on the environment
  • Secrets do not belong in images or Git

Distribution without inbound access

  • Versioned Docker images
  • The customer performs a controlled pull from its environment
  • Docker Compose enables only the services required by the installation
  • Older components are moving to this model progressively

eGovernment cloud

DERS is listed in the Czech DIA Cloud Computing Catalogue.

DERS s. r. o. is currently listed as an indirect IaaS/PaaS provider for security level 3 (provider ID 131). Public authorities can verify the entry in the official catalogue.

Open the DIA catalogue

demo.ders.cz

A public taste of the DERS environment.

The demo is intended for a quick first look and may change or become unavailable without notice. It is not a guaranteed sandbox or part of an SLA. For integration testing, we arrange an environment with the required configuration.

Open the demo