← Industries/Govtech & Public Sector
Promethean for Govtech & Public Sector
Selling AI into public-sector workflows means surviving the strictest audit posture there is. EU AI Act §5(a) Annex III makes most citizen-facing AI high-risk; GDPR Art. 22 + national administrative-law requirements demand meaningful human oversight; eIDAS adds identity-verification evidence. Promethean's verifiable per-decision chain is what makes 'every benefits-eligibility decision can be reproduced and contested' true rather than asserted.
Who this is for
Compliance + product teams in govtech SMBs (citizen-services · benefits eligibility · identity verification · public-administration AI). Typically:
- Seed–Series B govtech SMB with 5–60 engineers; selling into national, regional, or municipal authorities.
- 1–3 AI features in production: typically eligibility-classification, document extraction, citizen-chat.
- Decision volume: 1k–500k decisions per month per government customer (modest by commercial standards).
- Procurement cycles are long; the audit-trail demand is non-negotiable.
- Customers' Court of Audit + national Ombudsman + EDPB all scrutinise the AI-decisioning surface.
The regulatory pressure
EU AI Act Annex III §5(a) + §5(d) — public benefits + emergency dispatch
§5(a) covers AI used by (or on behalf of) public authorities to evaluate eligibility for essential public assistance benefits. §5(d) separately covers emergency-call triage + dispatch-priority AI. Both are high-risk; Chapter II applies — record-keeping (Art. 12), human oversight (Art. 14), transparency to deployers (Art. 13).
Deep-dive →GDPR Art. 22 — solely-automated decisions in public administration
Public-administration decisions affecting citizens (welfare, tax, housing, immigration) clearly produce legal effects. Solely-automated decisions need a legal basis (Art. 22(2)(b)) + safeguards including meaningful human intervention.
Deep-dive →eIDAS Regulation (910/2014, EU) — electronic identification
Identity-verification systems used by public services must meet eIDAS LoA (Level of Assurance) standards. AI-augmented identity verification needs per-decision evidence.
National administrative-law transparency requirements
Most EU member states require explainable AI in public decisions. Examples: the post-SyRI Dutch transparency expectations (The Hague District Court, 5 Feb 2020, NJCM v. The Netherlands), France's Loi pour une République numérique (Art. 4, 2016) on algorithmic transparency for public-sector decisions. Per-decision evidence is the substrate of that explanation.
Where LLMs typically run in Govtech & Public Sector
Benefits-eligibility pre-screening
Classifier producing eligible / ineligible / needs-review per applicant. Always-human reviewer gate on negative decisions; fallback to manual queue when uncertain. Spec hash binds the policy version per decision.
Document extraction (ID, certificates, tax)
Extractor producing structured fields from citizen-submitted documents. Reviewer-gate on low-confidence + schema violations; chain shows extraction error rate per document type.
Citizen-services chatbot
Drafter providing answers to common queries. AI Act Art. 50 transparency disclosure mandatory; reviewer-gate on flagged outputs (sensitive topics, escalation paths).
Triage routing (emergency / non-emergency)
Router classifying citizen requests by urgency + routing to the right team. Always-human reviewer gate on high-urgency classifications (mis-routed emergency = serious harm).
How the substrate maps to your audit
| Your LLM feature | What the regulator asks | Promethean evidence |
|---|---|---|
| Benefits pre-screening | Per-decision evidence under AI Act Art. 12 + GDPR Art. 22 challenge. | L12 entry with reviewerVerdict + specHash + modelIdentity per applicant. |
| Eligibility appeal | Meaningful human review available + override rate visible. | Always-human reviewer gate; override rate computable from chain. |
| Algorithmic-transparency disclosure | National laws require explanation of the decision logic. | specHash references the active spec; spec is publishable to satisfy disclosure. |
| Court of Audit annual review | Provide all AI-decisioning records for the audit period. | Time-bounded chain export; verify.mjs runs on the auditor's air-gapped machine. |
| eIDAS identity-verification | LoA-appropriate evidence per identity check. | Reviewer-gate on flagged checks; per-decision identity-confidence captured. |
Which Promethean tier fits
Recommended for typical SMBs in Govtech & Public Sector
Enterprise€2,499 / month flat
Unlimited · 15-min Bitcoin-anchored OTS · framework handoff templates (all 7) · SSO · HSM custody + on-prem (roadmap).
Govtech almost always demands Enterprise tier (€2,499/mo): all 7 framework templates including AI Act Annex III handoff, on-prem deployment option (roadmap; national-authority IT often forbids hosted SaaS), HSM key custody (roadmap; citizen-data sovereignty), SSO via SAML (mandatory in most public-sector procurements). Scale (€1,199/mo) works for SMBs serving municipal customers where on-prem isn't required and federation full (roadmap) is on the upgrade path.
Larger Govtech & Public Sector operators with multi-tenant or framework-template needs upgrade to Scale (€1,199 / month flat).
What this looks like in practice
Hypothetical: a benefits-eligibility AI SMB in a national-audit-office review
A govtech SMB providing AI pre-screening for a regional benefits agency is reviewed by the national Court of Audit following 2,000 citizen complaints in a single year. The audit asks: 'Show every decision in the affected period; show reviewer engagement on appeals; demonstrate spec consistency.' Without Promethean: months of legal exposure, lost contract. With Promethean: chain-export filtered to the affected period; reviewer-verdict aggregates show 24% appeal-override rate (meaningful human intervention); specHash shows no silent policy changes during the period. The Court of Audit runs verify.mjs against the chain. The contract is preserved; the lessons-learned report references the audit trail as best practice.
Frequently asked
We need on-prem deployment for our national-authority customer. Does Promethean support it?
On-prem deployment is on the Enterprise-tier roadmap; today Enterprise runs hosted on Promethean infrastructure (Vercel EU Frankfurt + Upstash EU). The substrate's SDK already runs in your operator infrastructure regardless of tier; once on-prem ships, the hosted dashboard + cron + framework-template generators will be deployable on-prem for Enterprise customers. The verifier (verify.mjs) is always operator-side (or auditor-side) — Apache-2.0, ~500-line Node stdlib, zero Promethean infrastructure required at verification time.
Citizen data sovereignty: does Promethean infrastructure hold citizen records?
Hosted-tier deployments use Vercel (EU Frankfurt) + Upstash (EU Frankfurt) — all data resides in the EU. For future on-prem Enterprise deployments (roadmap), no data will leave the customer's infrastructure. The L12 chain itself stores SHA-256 hashes of inputs/outputs, not raw citizen data — even hosted-tier deployments don't see raw citizen records.
Our procurement requires ISO 27001 / SOC 2 / national equivalents. Where is Promethean?
SOC 2 Type II is on the roadmap; ISO 27001 + EU CSA Cybersecurity Certification Scheme planned post-revenue-validation. The substrate's cryptographic primitives (Ed25519 + SHA-256 + hash chain + OpenTimestamps anchoring) provide stronger evidence than most certifications by themselves, but procurement still wants the formal cert. For Enterprise customers, we can produce per-customer compliance attestations against the substrate's specific behavior in advance of the formal certification.
What about national algorithmic-transparency obligations (France, Netherlands, etc.)?
France's algorithmic-transparency obligations (loi pour une République numérique, 2016) and similar Dutch + Belgian laws require public-administration AI to be explainable. The substrate's spec is the structured explanation: closed-enum schemas, model identity, reviewer policy, fallback behavior. The spec is hash-committed into every L12 entry, so 'this decision was made under this version of this spec' is verifiable. Pair the spec with your operator-side policy documentation and you have the transparency layer the law expects.
Public-sector procurement is 12-24 months. Does Promethean fit?
Self-service Enterprise pricing (€2,499/mo = ~€30k/year) is below most public-sector PO thresholds for IT services. A CIO or CISO can usually expense it under operational-tooling budget without committee. For larger national-authority deployments where the contract is part of a multi-million-euro digital-transformation programme, the Enterprise tier folds in as a controls-strengthening line item rather than a standalone procurement.
Definitions used on this page
The substrate primitives referenced above (L12 receipt chain, spec hash, reviewer gate, fallback behaviour, OpenTimestamps anchor, tenant ID) all have canonical definitions in the glossary: