Public portals
Online submissions and appointments, with instant confirmation, attached documents and a status the applicant can see without calling the counter.
Digitising a process inside a public institution
The process already exists inside an institution: someone receives the request, someone else checks it, a third person endorses it and at the end someone signs. Digitising it does not mean putting the form online; it means moving that whole path into a system that knows who comes next, what deadline applies and what happens when the deadline passes.
We build these systems on BPMN process engines: the workflow is drawn, not written in code, so it can change without rewriting the application. We have worked on five national systems in operation, as a collaborating company, alongside the partners holding the contract with the institution.
- BPMN
- Camunda
- Spring Boot
- Angular
- Keycloak
- Elasticsearch
01
What we build
The pieces work together: a portal without a backoffice solves nothing, and a backoffice without a workflow is still a spreadsheet with buttons.
Case-handling backoffice
The application where civil servants process requests: verification, additions, endorsement, decision, communicating the outcome. Every step with an owner and a deadline.
Executable BPMN workflows
The process is modelled graphically and run by a process engine. Versioned, changeable mid-flight, and you can see exactly where a case stopped and for how long.
Statutory registers
The registers the law requires, generated from the system’s own data instead of kept in a parallel file: numbering, history, export, archiving.
Official documents
Reports, decisions, letters and orders generated on the approved forms, with the numbering and fields of the official template, not rebuilt by hand for each case.
Integrations
Links to the registries and applications the institution already runs, with central authentication and role-based permissions, so data is not entered twice.
02
What you get
A process that can change
When the procedure changes, the diagram changes. No code release, no three-month wait.
Full traceability
For every case you can see who did what and when. During an inspection the answer comes out of the system, not out of a colleague’s memory.
Audit-ready
Activity log, role-based permissions, personal data handled separately and export on request.
People who stay on the system
The same people who wrote the process answer after launch too, for workflow changes and new reports.
03
How a project runs
The same method as the rest of our work: process first, code second.
- 01
Process analysis
We sit with the people doing the work and write the process as it happens, exceptions included. The diagram comes from there, not from the regulation.
- 02
Architecture and a staged quote
We settle the workflow, the data model and the integrations, then split the work into stages that can be used one at a time. Each stage has a goal and a deadline.
- 03
Delivery and operation
Each stage goes to the real environment and is checked with real data. After launch we stay on monitoring, process changes and reports.
Relevant projects
Questions about this service
How long does it take to digitise a process?
A well-bounded process — an appointment, a request, an endorsement — reaches production in 6–10 weeks, the first of which is analysis only. A system with several processes and integrations is built in stages, each one going live when it is ready rather than at the end.
How much does it cost?
It depends on how many processes are in scope and how many integrations the institution needs. We quote per stage, with each stage’s goal and deadline written down, so you can stop or continue after the first delivery. The first conversation and the architecture proposal are not billed.
What does it mean in practice that the process runs "on BPMN"?
The workflow is drawn in a standard diagram — who receives, who checks, what happens when a deadline is missed — and the application executes exactly that diagram. When the procedure changes, the diagram changes; the application code stays the same.
Do you work directly with the institution or as a subcontractor?
So far we have worked as a collaborating company, alongside the partners holding the contract with the institution — that is how the five systems in our portfolio were built. We can also work directly or in a consortium.
What happens after launch?
We stay on the system: monitoring, alerts, process changes and new reports on request. A mission-critical system is not handed over and forgotten — procedures change, and the system has to keep up.
Contact
Which process should stop running on paper?
Tell us how it runs today, exceptions included. We come back with the process diagram and a plan in stages.
Office: Barajul Dunării 3, District 3, Bucharest