Home / Services / Public sector IT services
Service · 07 / 12

Public sector IT services.

We have worked with Latvian public institutions since 2010. Those projects ran under Latvian public procurement rules and Cabinet of Ministers regulations — that is the experience we bring, not the statute that binds your institution. We deliver against the technical specification in the tender, GDPR, and the cybersecurity law that actually applies to you — the NIS2 directive binds member states, and what binds you is the law in your own country that transposes it.

Timeline
As per tender
Tech
16 tools
Included

If your institution needs it, we get involved before the procurement and help draft the technical part of the specification and deadlines that can realistically be met, provided this does not affect our ability to take part in the tender afterwards. We usually call for a public consultation on the technical specification. During implementation we work strictly to the technical specification — both with systems already in place and building new ones with Laravel, Symfony, WordPress, Joomla, Drupal, Moodle or Statamic. We handle authentication with single sign-on (SSO) over SAML, OpenID Connect or OAuth2, and we connect to other systems over REST or SOAP. We have implemented national e-identity and official e-delivery integrations several times, so we know the typical test-environment errors and how to prepare a mock solution during development. We deliver the interface in the languages the specification names. We build accessibility to WCAG 2.1 AA — semantic structure, keyboard navigation, contrast, screen reader support — and we run the check before handover. Before acceptance we carry out a security audit with our own audit tool and verify compliance with the ICT and security requirements the tender sets, with GDPR, and with any other regulations or laws the project requires. Data stays in the European Union, and if the procurement requires storage in a named country, we provide that as well. We hand over a working system, full documentation, audit results and certificates — everything needed to sign the acceptance certificates. After handover we maintain the system under an SLA in line with the procurement contract.

Technologies used
Single sign-on (SSO) over SAML, OpenID Connect or OAuth2 Official e-delivery REST API / SOAP WCAG 2.1 AA Laravel Moodle Docker Symfony WordPress Drupal Joomla Statamic Vue.js React PostgreSQL MariaDB
  • Single sign-on (SSO) over SAML, OpenID Connect or OAuth2, and official e-delivery
  • Compliance with the ICT and security requirements the tender sets
  • GDPR and personal data protection
  • Public procurement experience
  • Certified security audits
  • Multilingual user interface
  • Accessibility (WCAG 2.1 AA)
Process

How it works.

01
Procurement
We help prepare the technical specification if needed.
02
Implementation
Strictly to specification, with full documentation.
03
Compliance
Audits, certificates, acceptance records.
04
Maintenance
An SLA in line with the procurement contract.
FAQ

Frequently asked.

Yes, we have worked with public institutions since 2010. We know the language of technical specifications, procurement procedures and the documentation acceptance records require.
We can advise on the technical part and realistic deadlines. Note that in some cases this can affect our right to bid on the same tender — we always discuss that upfront.
Yes, we have implemented both several times. We also know the typical pitfalls in the test environment and how to set up a mock during development.
We build to WCAG 2.1 AA — semantic structure, keyboard navigation, contrast and screen reader support. We test before handover.
In the European Union, in line with GDPR and the institution's requirements. If the tender requires storage in Latvia, we provide that too.