FlyttGo Technologies Group AB
Government Capability Brief
Modular platform infrastructure for sovereign-ready public-sector deployment.
FlyttGo Technologies Group designs and operates modular cloud platform infrastructure deployed across European, African and Middle Eastern public-sector programmes. Eight independently licensed modules — identity, payments, mobility, workforce, education, government services, financial operations and marketplace — orchestrated through the FlyttGoTech Core. Three deployment modes: managed SaaS, customer cloud, sovereign national datacenter.
1.1 · Why this brief
This brief is issued to [Recipient organisation] in connection with the programme context disclosed in the engagement-desk record. It documents the capability surface FlyttGo brings to the programme, the deployment modes the programme can be delivered against, and the sovereignty framework that applies to every contract instrument.
1.2 · Capability summary at a glance
| Capability | What FlyttGo provides | Reference shape |
|---|
| Identity & access | National-eID-compatible identity broker, federated SSO, eIDAS-aligned trust services | Multi-tenant, sovereign HSM, regional residency |
| Payments & disbursement | Public-payment orchestration, PSD2-aligned, SEPA + national-rail integrations | In-jurisdiction processor, audited reconciliation |
| Workforce coordination | Public-sector workforce scheduling, certification tracking | Regional or national workforce population |
| Education intelligence | Admissions, scholarships, institutional analytics | Multi-institution, ministry-of-education tier |
| Mobility infrastructure | Dispatch, telematics, regional mobility coordination | Transport authority or ministry of transport |
| Municipal services | Citizen services, residents portals, council operations | Metro to national-municipal scale |
| Financial operations | Statutory bookkeeping, VAT/SAF-T export, audit-grade journal | Ministry-of-finance or central-audit tier |
| Marketplace | Regulated multi-sided platform infrastructure | National or regional exchange |
1.3 · Service-model declaration
FlyttGo operates against four service postures, each with a corresponding contractual frame:
- SaaS capability — operational platform tenants delivered managed, region-bound.
- PaaS orchestration architecture — the FlyttGoTech Core exposes an orchestration substrate that customers extend with internal services.
- IaaS-compatible deployment environments — the platform installs into the customer's existing AWS, Azure, GCP or bare-metal sovereign environment.
- Sovereign national infrastructure readiness — installations inside certified national datacenters with national HSM, national-eID integration, regulator-bounded operations.
2 · Platform capability matrix
Eight modules, each independently licensed. Modules operate against the same shared identity, audit and orchestration substrate; selecting a second module does not require a second integration cycle.
| Module | Function | Regulatory anchor | Posture |
|---|
| Identra · PL.05 | Identity broker, eIDAS-aligned, national-eID compatible | eIDAS · GDPR | SaaS or sovereign |
| Payvera · PL.06 | Public-payment orchestration, SEPA + national-rail | PSD2 · GDPR | SaaS or customer cloud |
| Civitas · PL.03 | Municipal & government services portal | GDPR · sectoral municipal law | Sovereign-leaning |
| EduPro · PL.04 | Admissions · scholarships · institutional analytics | Sectoral education-data law | SaaS or customer cloud |
| Workverge · PL.02 | Workforce scheduling and certification tracking | National labour law | SaaS or customer cloud |
| Transify · PL.01 | Mobility infrastructure, dispatch, telematics | Sectoral transport regulation | SaaS or customer cloud |
| Ledgera · PL.07 | Financial operations, statutory bookkeeping, SAF-T | IFRS / GAAP · national accounting law | SaaS or sovereign |
| FlyttGo Marketplace · PL.08 | Regulated multi-sided platform infrastructure | Sectoral marketplace law | Per programme |
3 · Deployment posture & sovereignty framework
3.1 · Three deployment modes
| Dimension | DM.01 Managed SaaS | DM.02 Customer cloud | DM.03 Sovereign datacenter |
|---|
| Data residency | EU primary regions | Customer tenancy region | 100% in-jurisdiction |
| Key custody | FlyttGo KMS | BYOK / HYOK | National HSM |
| Identity boundary | FlyttGo IdP | Customer IdP · OIDC/SAML | Sovereign eID |
| Regulatory posture | GDPR · SOC 2 · ISO 27001 | + FedRAMP / DORA / NIS2 | + NSM · SDAIA · NCA · Cloud-Act exempt |
| Patch cadence | 14-day rolling | 14-day · customer change window | 30-day staged · sovereign window |
| Uptime SLA | 99.95% per region | 99.95% per region | 99.9% per facility · DR pair |
| Audit retention | 7-year default | Customer policy | Regulator-defined (10y+) |
| Pilot-to-production | 60–90 days | 75–120 days | 120–180 days |
3.2 · Sovereignty framework
Cloud-Act exposure declared per deployment mode. Data residency enumerated per jurisdiction; key custody per the chosen mode; regulator-hand-off framework defined for sovereign installations; right-to-audit clause standard in every contract.
3.3 · Compliance certifications
- SOC 2 Type II — annual audit, NDA-shareable
- ISO 27001 — ISMS, Annex A coverage
- GDPR-ready — DPA, in-region residency
- WCAG 2.1 AA — accessibility
- PSD2 (Payvera) — EU payments, SCA
- eIDAS (Identra) — EU trust services
4 · Procurement & engagement
4.1 · Procurement compatibility
| Tier | Programme shape | Cadence |
|---|
| PR.01 | Pilot deployments | 60–90 days |
| PR.02 | City rollouts | 90–150 days |
| PR.03 | Regional deployments | 4–9 months |
| PR.04 | National infrastructure programmes | 6–18 months |
| PR.05 | White-label platform licensing | Per agreement |
4.2 · Reference programme shapes
Three anonymised reference programmes are documented in section GV.08 of the engagement surface (flyttgo.tech/government). Full reference details — recipient, contract instrument, statutory metrics, audit outcomes — released only under NDA.
4.3 · Engagement next steps
- Capability deep-dive — 60-minute architecture session with the FlyttGo platform team.
- Pilot scoping — formal scoping engagement under NDA; output is a written pilot brief and a price-shape proposal.
- Procurement engagement — moves to one of the five tiers above with the corresponding contract instrument.
