Data residency and source-code handover — what do we offer?

For public-sector projects we deliver EU-only data residency by default: AWS Frankfurt / Azure West Europe / GCP Belgium, or NISZ Tier IV or a private Tier III/IV Hungarian data centre. Source-code handover (per the procurement contract) is a standard commitment: the entire Git repository, documentation, build scripts and deploy pipeline are handed over to the customer at project closure. Where the contracting authority sets a stricter licence (e.g. EUPL v1.2), we comply.

What is RNY (Provision Registry) integration?

RNY (Rendelkezési Nyilvántartás, sometimes referred to as KÉR) is a central electronic-administration service under Act CCXXII of 2015 and related decrees. Citizens declare their preferred e-administration channel (Ügyfélkapu, phone identification), powers of attorney and periodic notifications here. Integration into a municipal / administrative system: query the citizen's identity and declarations before processing a case via web service. We deliver an RNY client module against the API path defined by Government Decree 451/2016 (XII. 19).

Is ÁNYK / ONYA NAV form connectivity still needed?

Yes, but it's shifting. NAV (the Hungarian Tax and Customs Authority) is gradually retiring the classic desktop ÁNYK (General Form Filler) — expected sunset around 2027. The new ONYA (Online Form-Filling Application, onya.nav.gov.hu) is the browser-based alternative. We build NAV reporting into public-sector software so it works on both paths: ÁNYK-compatible XML export and ONYA REST API handoff (where available), with Ügyfélkapu / KAÜ authentication.

Does NIS2 require the office to register?

Hungary's Act LXIX of 2024 takes the NIS2 Annex I 'public administration' point onto central and regional public administration as essential entities. Fines start at EUR 10M or 2%, the Article 21(2) ten measures (risk analysis, business continuity, supply-chain security, cryptography, MFA) and Article 23 24h/72h/1-month incident reporting are mandatory. For municipalities, size threshold and criticality jointly decide the exact classification. We deliver the NIS2 gap audit, Article 21(2) implementation plan and the reporting pipeline (toward SZTFH where applicable).

How much does a public-procurement custom build cost?

Our EKR-tendered ranges: municipal / administrative case-management system 6-12 months, HUF 35-110M. RNY / KAÜ / ONYA integration 3-5 months, HUF 15-32M. NIS2 essential-entity compliance program (central body) 6-9 months, HUF 35-90M. EU AI Act Annex III high-risk AI rollout (FRIA, Annex IV, post-market) 4-7 months, HUF 22-55M. The procurement-contract overhead (technical documentation, clarifications, on-site handover, source-code escrow / handover) adds 10-20% over commercial ranges. Exact quote after a 30-minute scoping call.

EKR · RNY / KAÜ · ÁNYK/ONYA · NIS2 · AI Act

Software development for the public sector

Custom administrative, municipal and central-body software with procurement-aware delivery. RNY / KAÜ / ONYA integration, EU-only data residency, NISZ or private Tier IV data centre options, NIS2 essential-entity compliance and EU AI Act Annex III. Last updated 2026-05-04.

Request a public-sector scoping call

30-minute consultation

TL;DR

Act CXLIII of 2015 public procurement procedures run on EKR by default.
NIS2 Annex I classifies public administration as an essential entity — fines >= EUR 10M or 2%, Hungary's Act LXIX of 2024 in force 2026-01-06.
The RNY (Provision Registry) + KAÜ pair is the central point of citizen identification and declarations across e-administration.
NAV's classic desktop ÁNYK framework is being phased out (sunset around 2027); ONYA is the browser-based alternative.
Project ranges: HUF 15-110M depending on scope, EU-only data residency, full source-code handover by default.

Pain map — what public-sector IT leads are dealing with

Concrete, named problems from municipal and central-body customers.

EKR technical spec — too narrow or too broad

The technical spec attached to an Act CXLIII of 2015 procurement notice is often either tailored to a single supplier or so generic that bids are incomparable. We deliver a typical integration profile and an open-source component list for the call so the market can compare actual suppliers.

Source-code handover hurried, with poor documentation

Contracted source-code handover at project closure is too often a single ZIP file with no build instructions. We hand over Git repo + README + Makefile / Dockerfile + DEPLOY.md + ARCH.md by default, so the next supplier can build within 2-3 days.

RNY / KAÜ / Ügyfélkapu integration — manual rebuild every time

In many administrative systems the RNY / KAÜ client lives as an ad-hoc, write-once layer. Every KEÜSZ (Central E-Administration Service) version bump triggers another firefighting project. We deliver a contract-pinned, version-tolerant client layer.

NIS2 essential entity in public admin — no roadmap yet

Many offices haven't lit up the Article 21(2) ten-measure implementation and 24h/72h reporting pipeline under Act LXIX of 2024. Bodies under SZTFH oversight carry active risk — fines start at EUR 10M or 2%.

EU AI Act Annex III — high-risk AI in administration

Automated administrative decisions (welfare entitlement, pension calc), educational testing AI and law-enforcement risk assessment are all high-risk under Annex III. By 2026-08-02 you need an FRIA, Annex IV technical file and post-market monitoring.

Regulatory landscape for public-sector software

Only items grounded in official sources (NJT, EUR-Lex, EKR).

Regulation	Applicable	Scope	Penalty
Act CXLIII of 2015 — Public Procurement	In force (2026-01-01 latest version)	EKR-run procedures, contracting authority comms	Procedure invalidation, KIK referral
NIS2 — Dir. (EU) 2022/2555	HU 2026-01-06 (Act LXIX of 2024)	Essential entity (Annex I — public administration)	>= EUR 10M or 2%
EU AI Act — Reg. (EU) 2024/1689	2026-08-02 high-risk AI	Administrative decisions, education, law enforcement (Annex III)	<= EUR 15M or 3% (Art. 99(4))
Government Decree 451/2016 (XII. 19.) — e-administration	In force	RNY and related KEÜSZ service usage	Administrative sanctions
Procurement-contract source-code handover	Contract-bound	Full source code + docs at project closure	Breach-of-contract penalty
GDPR — Reg. (EU) 2016/679	2018-05-25	Citizen data, automated decision-making (Art. 22)	<= EUR 20M or 4%

Integration matrix — what we connect to

Every named system has a documented API and live integrations in production at our public-sector customers.

System	Protocol	Note
EKR — Electronic Procurement System	Web UI + document exchange	ekr.gov.hu, bid submission and communication channel.
RNY — Provision Registry	Web service / REST	Central e-administration KEÜSZ, citizen-declaration and POA lookup.
KAÜ — Central Identification Agent	OAuth2 / SAML 2.0	Ügyfélkapu, eID card, phone-identification auth point.
ÁNYK / ONYA — NAV forms	XML / REST	ÁNYK desktop is being retired; ONYA is the browser-based alternative at onya.nav.gov.hu.
NISZ government cloud	Private network / VPN	Tier IV data centre for government bodies.
Magyar Államkincstár — KIRA payroll	XML batch / REST	Central payroll system also used in the municipal sector.
ÁHT — public finance information	XML / web service	Public-finance bodies' financial reporting.
EU CEF eDelivery / eIDAS	AS4 / SAML eIDAS	Cross-border public-administration document exchange.

Why pick us for a public-sector project

Procurement-aware delivery

EKR technical documentation, clarification rounds, on-site handover, source-code handover — pre-documented.

EU-only data, Hungarian Kft.

AWS Frankfurt / Azure West Europe / GCP Belgium or NISZ / private Tier IV Hungarian data centre; every contract via Hungarian Kft.

RNY / KAÜ / ONYA module ready

Version-tolerant client layer, KAÜ OAuth2 / SAML, dual ÁNYK + ONYA export, eIDAS where needed.

NIS2 + AI Act roadmap

Article 21(2) ten-measure mapping, 24h/72h reporting flow, FRIA + Annex IV technical-file template.

Pricing for public-sector projects

Our published project ranges (see /pricing.md), adjusted for public-sector overhead (about +10-20% for procurement docs and on-site handover).

· Municipal / administrative case-management system: 6-12 months, HUF 35-110M
· RNY / KAÜ / ONYA integration: 3-5 months, HUF 15-32M
· NIS2 essential-entity compliance program: 6-9 months, HUF 35-90M
· EU AI Act Annex III high-risk AI rollout: 4-7 months, HUF 22-55M
· Source-code handover + 4-eyes review pipeline: 2-3 months, HUF 5-12M
· Continuous compliance retainer: HUF 0.8-2.5M / month

Talk in person, near our office

In a 30-minute scoping call we map the administrative IT environment and procurement needs and give you a tight estimate. Call +36 30 098 0767 or drop in.

Budapest office: Bank Center, Szabadság tér 7., 1054 Budapest, 1st floor, office 112. Mon-Fri 9:00-18:00 by appointment · balint@appforge.hu

Official sources

Last updated 2026-05-04. This page does not replace legal or procurement advice.

Internal links if you want to go deeper: NIS2 checklist · EU AI Act checklist · System integration.

GYIK

Public sector — frequently asked

Under Act CXLIII of 2015, contracting authorities run public procurement procedures through EKR (Elektronikus Közbeszerzési Rendszer, ekr.gov.hu) by default. Procuring-side communication, document exchange and bid submission all happen there. We've delivered EKR-tendered projects for years and know the rhythm of technical specs, suitability criteria and clarification rounds. The new EKR features rolled out from 30 June 2024 (structured search, SME notifications) also help with market analysis.

Kapcsolódó megoldások

Let's start the public-sector scoping call

In 30 minutes we map the administrative IT environment and give you a tight time-and-cost estimate.

Request a public-sector scoping call →30 perc ingyenes konzultáció