Software for the Public Administration, built by the rules.
For public entities and PA suppliers that need to develop AgID-compliant software: AgID guidelines, WCAG 2.1 AA + EN 301 549 accessibility, integration with SPID, CIE, ANPR, PagoPA, NIS2 conformity where applicable.
What happens today.
Building software for the Italian Public Administration requires complying with a specific body of rules: AgID Guidelines for design, software quality, ICT security, accessibility (WCAG 2.1 AA + EN 301 549 for public procurement), interoperability via standard APIs, integration with national enabling platforms (SPID, CIE, ANPR, PagoPA).
Adding these compliances at the end of a project is expensive and often produces software that is 'compliant on paper' but struggles at the AgID audit. Building it compliant from the start is the realistic path: predictable timelines, evidence ready, no inspection surprises.
AgID compliance is not an add-on. It is the foundation of public software.
The solution, broken into parts.
-
AgID Guidelines integrated into the design
Design system compliant with AgID Guidelines for digital-service design. UI components accessible by default (focus visible, contrast ratio, screen reader). Automatic validation with axe-core and Pa11y in CI.
-
SPID, CIE, PagoPA integration
Integration of national enabling platforms: SPID (identity federation), CIE (electronic ID card), PagoPA (payments), ANPR (registry), where relevant NoiPA, IO. Official interoperability tests run pre-release.
-
WCAG 2.1 AA + EN 301 549 accessibility
Natively accessible development, validated with automatic tools (axe-core, Pa11y) and manual tests with assistive technology (NVDA, JAWS, VoiceOver). EN 301 549 conformity for public ICT procurement. Formal accessibility declaration.
-
Documentation + AgID audit kit
All AgID-required documentation: ADRs (Architecture Decision Records), threat model, security-test evidence, conformity declarations (accessibility, security), software-development Code of Conduct. Versioned, kept in sync with the code.
The typical profiles who benefit.
-
Direct public entities (Municipalities, Regions, Ministries)
Municipalities, Regions, Ministries, Public Agencies that need to develop internal management software or citizen portals. Selectable via MePA, direct award, open tenders.
-
PA suppliers (RTI, sub-contractors)
Companies bidding on public tenders as prime contractors or RTI members. Must deliver software that passes the AgID audit. We can work as specialized sub-contractors on AgID-critical components.
Transparency on what the client does.
Before we start we need a few accesses and decisions. All reasonable, no surprise asks.
-
PA scoping
- Entity type / classification (Central PA, Local PA, AgID-supervised)
- Project reference documents (tender, capitolato, technical annexes)
- Any additional sector guidelines (e.g. healthcare, school, fiscal)
-
Technical decisions
- Target cloud (AgID-qualified or Polo Strategico Nazionale)
- Enabling platforms to integrate (SPID, CIE, PagoPA, ANPR)
- Specific accessibility or multilingual constraints if any
Indicative numbers, not quotes.
- TIME
- Typically 4-12 months depending on complexity. AgID compliance typically adds 20-30% to the time of an equivalent private project.
- COST
- Range €70,000-400,000. Funding is often covered by PNRR funds or the entity's budget.
- MODEL
- Fixed milestones aligned with the tender schedule. Periodic demos with the RUP (project manager).
Indicative numbers. For an accurate quote, let's talk.
Answers to the most common questions.
Are you registered on MePA?
Yes, we are registered on MePA with active bids for software-development services and ICT consulting. We can be selected via Trattativa Diretta (TD), Richiesta di Offerta (RdO), or below-threshold direct award. Administrative documentation available.
Can we bid on public tenders with you as RTI?
Yes. We bid on public tenders as prime contractors or as members of a Temporary Business Grouping (RTI). We can cover the AgID-compliant software-development part complementing partners covering other verticals (compliance consulting, infrastructure, PA project management).
How do you handle the accessibility declaration?
We produce the formal accessibility declaration at end of project, validated with internal audit (axe-core, Pa11y, manual test with screen reader). The declaration is published on the AgID Form and kept up to date. We update the declaration when new software releases impact accessibility.
Recognize your case?
Write a couple of lines about your context. We'll reply within 24-48 hours with an initial assessment and a first orientation on time and cost.
Let's talk