Skip to content
HP.00FlyttGo Technologies Group

Platform infrastructure · IaaS · SaaS · PaaS · Sovereign

Cloud platform infrastructure for enterprises and public-sector deployments.

IaaS · SaaS · PaaS · sovereign environments — the same eight modules deployed your way across the Americas, Europe, Africa, MENA and APAC. Mobility, workforce, identity, payments, government services, education and financial operations on one orchestration layer.

  • EU deployment
  • AF scale-ready
  • MENA interop
  • Sovereign-ready
  • Modular rollout
  • Multi-platform orchestration
  • Regional federation
  • SOC 2 · ISO 27001
Explore Platform EcosystemEngineering division · SE.00Request Partnership Discussion
RG.00·FlyttGo infrastructure operational across
  • NANA SaaS · IaaS
  • EU-NNordic EU
  • EU-WWestern EU
  • SALatin America
  • AFAfrica
  • MENAMENA
  • APACAPAC
OPS.LIVEFlyttGo infrastructure operational across EU · Africa · MENA deployment regions
  • OPS.01Transactions / sec
    4,280
  • OPS.02Active deployments
    184
  • OPS.03Regions reporting
    18 / 18
  • OPS.04p99 API latency
    132 ms

Simulated demo telemetry · live feed lands with the public metrics endpoint. SLA dashboards on /status.

TR.00

Deployed for

HP.IDXCapability pathways · eight clusters

Pick the pathway your programme starts from.

FlyttGo Technologies operates as eight distinct capability clusters on a single engineering substrate. Each cluster is a self-contained surface with its own intake, scoping cadence and deployment posture — chosen by the visitor, not assumed by the marketing site.

SM.00Service models

Four service models. One orchestration core.

FlyttGo runs as IaaS inside your cloud, as managed SaaS in primary regions, as a PaaS API surface for builders, and as sovereign infrastructure for regulated jurisdictions. Same modules, four delivery shapes.

  • SM.01
    IaaS

    Infrastructure as a Service

    Tenant-isolated compute, storage and network primitives running inside your AWS · Azure · GCP account. You own the substrate; FlyttGo orchestrates the workloads on top.

    • Enterprises
    • Public sector
    • Customer-cloud deployment (DM.02)
    • Per-tenant VPC + IAM
    • Region-aware data residency
    • BYO key management (HSM-backed)
    Customer-cloud deployment
  • SM.02
    SaaS

    Software as a Service

    FlyttGo-managed multi-tenant platforms across primary regions. Fastest path to production — sign in, configure, deploy. Mostly chosen by SaaS-native enterprises and rapid-pilot programmes.

    • Enterprises
    • Municipalities + agencies
    • FlyttGo-managed deployment (DM.01)
    • NA · EU · APAC primary regions
    • Per-tenant schema isolation
    • 60–90 day go-live
    Managed SaaS deployment
  • SM.03
    PaaS

    Platform as a Service

    API-first developer surface — versioned REST + federated GraphQL + signed webhooks + MCP discovery. Build your own products on top of the FlyttGo orchestration core.

    • B2B SaaS builders
    • System integrators
    • Government IT teams
    • TypeScript · Python · Go SDKs
    • OpenAPI 3.1 specs per release
    • OAuth 2.1 + organization-scoped tokens
    • Sandbox tenants in 5 minutes
    API architecture
  • SM.04
    Sovereign

    Sovereign infrastructure

    Self-hosted in certified national datacenters. Full operational handover to in-jurisdiction staff, optional air-gap, national HSM. Used where data residency is non-negotiable.

    • Ministries
    • Regulated enterprises
    • Defence + intelligence
    • Sovereign datacenter (DM.03)
    • In-jurisdiction data + key custody
    • Air-gap option per environment
    • Public-sector procurement frameworks
    Sovereign deployment

The same eight platform modules — Transify · Workverge · Civitas · EduPro · Identra · Payvera · Ledgera · FlyttGo Marketplace — run identically under each service model. The orchestration contract is constant; the substrate is the variable.

OR.00FlyttGoTech Core orchestration

One orchestration layer. Six interoperability planes.

FlyttGoTech Core is the runtime that lets the modules behave as one platform. Identity authenticates, payments settle, mobility dispatches, workforce executes, education routes, financial operations close the books — every event traversing the same audit envelope. Deployable as SaaS, customer-cloud, or sovereign environments.

OR.IDNOR.PAYOR.MOBOR.WRKOR.EDUOR.FINOR.COREFlyttGoTech
  • OR.IDN

    Identity layer

    Identra anchors every cross-module call — SSO, MFA, eIDAS-LoA, qualified-signature flows. Every audited action carries the same identity envelope.

  • OR.PAY

    Payments layer

    Payvera handles SCA, open-banking endpoints, and transaction monitoring. Settles into Ledgera with VAT-coded line detail in the same orchestration step.

  • OR.MOB

    Mobility layer

    Transify dispatches fleet, telematics and corridor coordination. Acts as the runtime under the FlyttGo marketplace and any third-party transport authority.

  • OR.WRK

    Workforce layer

    Workverge plans rosters, qualification states, and field-team assignments. Identra-bound; logs into the same audit trail as financial events.

  • OR.EDU

    Education layer

    EduPro routes admissions, scholarships and ministry-grade reporting. Federates identity with Identra and emits payments via Payvera for fees and stipends.

  • OR.FIN

    Financial operations layer

    Ledgera receives every monetary event from the planes above, posts double-entry, and emits SAF-T XML / VAT-100 / GAAP bundle / IFRS package on demand.

Every plane composes the same way under each deployment mode — FlyttGo-managed SaaS, customer-controlled cloud, or sovereign national environment. The orchestration contract is identical; the substrate is the variable.

HP.MAPGlobal deployment surface

One platform substrate, deployed across four continents.

Oslo headquarters, primary EU and US zones, sovereign envelopes across MENA and Southern Africa, active rollout across Cameroon, Uganda and Ethiopia. The same orchestration core operates under every deployment — what changes is which substrate runs the workload and who holds the keys.

Oslo, Norway — HQ · primary EUStockholm, Sweden — Nordic opsLondon, UK — UK · CommonwealthFrankfurt, Germany — Mainland EU SaaSAmsterdam, NL — EU edgeSan Francisco, USA — NA-West SaaSN. Virginia, USA — NA-East SaaSToronto, Canada — NA edgeYaoundé, Cameroon — Central Africa rolloutKampala, Uganda — East Africa rolloutAddis Ababa, Ethiopia — Horn of Africa rolloutNairobi, Kenya — East Africa hubLagos, Nigeria — West AfricaJohannesburg, ZA — Sovereign · ZADubai, UAE — Sovereign · GCCRiyadh, KSA — Sovereign · KSACairo, Egypt — North AfricaMumbai, India — South AsiaSingapore, SG — APAC hubTokyo, Japan — East AsiaSydney, Australia — OceaniaSão Paulo, Brazil — LatAm hub
  • Primary EU / NA
  • Sovereign envelope
  • Secondary region
  • Africa rollout
Open global coverage · GC.00Sovereign envelopes · SV.00EU · NA · LatAm · MENA · Africa · APAC · Oceania
DP.02
Deployment Architecture
3 deployment modes · sovereignty-aware · multi-region

Deploy on your sovereignty terms.

Three deployment modes to match any procurement or sovereignty posture. Deployment details.

DT.00 · TENANT ENTRYFlyttGo platform tenantDM.01FlyttGo-managedRegion-aware managed SaaSEU PRIMARYDM.02Customer cloudAWS · Azure · GCP tenancyBYOCDM.03Sovereign datacenterNational DC, optional air-gapIN-JURISDICTION
WM.00·Global deployment map
NA · SA · EU · AF · MENA · APAC · OCE
US-W · San Francisco — SaaS · customer-cloud westUS-WSan FranciscoUS-NW · Seattle — NA-West · enterprise SaaSUS-NWSeattleUS-MW · Chicago — NA-Central · enterprise edgeUS-MWChicagoUS-NE · Boston — NA-East · enterprise SaaSUS-NEBostonUS-E · Northern Virginia — SaaS · customer-cloud eastUS-ENorthern VirginiaUS-S · Atlanta — NA-South · enterprise edgeUS-SAtlantaUS-SC · Dallas — NA-South-Central · IaaSUS-SCDallasUS-SE · Miami — LatAm gateway · enterpriseUS-SEMiamiCA-E · Toronto — Edge presenceCA-ETorontoBR-SE · São Paulo — LatAm hubBR-SESão PauloNO-OS · Oslo — HQ + primary EUNO-OSOsloSE-ST · Stockholm — Nordic opsSE-STStockholmUK-LN · London — UK + CommonwealthUK-LNLondonDE-FR · Frankfurt — Mainland EUDE-FRFrankfurtNL-AM · Amsterdam — EU edgeNL-AMAmsterdamKE-NB · Nairobi — East Africa hubKE-NBNairobiZA-JN · Johannesburg — Sovereign · ZAZA-JNJohannesburgNG-LG · Lagos — West AfricaNG-LGLagosCM-YA · Yaoundé — Central Africa rolloutCM-YAYaoundéUG-KP · Kampala — East Africa rolloutUG-KPKampalaET-AA · Addis Ababa — Horn of Africa rolloutET-AAAddis AbabaAE-DX · Dubai — Sovereign · GCCAE-DXDubaiSA-RD · Riyadh — Sovereign · KSASA-RDRiyadhEG-CR · Cairo — North AfricaEG-CRCairoIN-MU · Mumbai — South AsiaIN-MUMumbaiSG · Singapore — APAC hubSGSingaporeJP-TY · Tokyo — East AsiaJP-TYTokyoAU-SY · Sydney — OceaniaAU-SYSydney
PrimarySecondarySovereign

Ledgera supports deployment on FlyttGo-managed, customer cloud, and sovereign national datacenters alongside Transify, Workverge, Civitas, EduPro, Identra, and Payvera.

DM.MX
Deployment-Mode Comparison
3 modes · 8 procurement dimensions · choose-by-row

The dimensions your procurement team actually compares.

Pre-shaped per deployment mode. Data residency, key custody, identity boundary, regulator posture, SLA and audit retention — tabulated so security, legal and ops can sign off in one review cycle.

DM.01
FlyttGo-managed SaaS
Fastest path · region-aware
Data residency
In-region (EU primary, opt. AF/MENA/APAC)
Encryption-key custody
FlyttGo KMS · per-tenant DEK
Identity boundary
FlyttGo IdP · SSO federated
Regulatory posture
GDPR · SOC 2 II · ISO 27001
Patch cadence
14-day rolling · region-windowed
Uptime SLA
99.95% per region
Audit retention
Append-only · 7-year default
Pilot-to-production
60–90 days
DM.02
Customer cloud
BYO AWS · Azure · GCP
Data residency
In customer tenancy region
Encryption-key custody
Customer KMS · BYOK / HYOK
Identity boundary
Customer IdP · OIDC/SAML in tenant
Regulatory posture
+ customer FedRAMP / DORA / NIS2 perimeter
Patch cadence
14-day rolling · customer change window
Uptime SLA
99.95% per region
Audit retention
Append-only · customer retention policy
Pilot-to-production
75–120 days
DM.03
Sovereign datacenter
In-jurisdiction · air-gap option
Data residency
100% in-jurisdiction · national datacenter
Encryption-key custody
National HSM · sovereign key root
Identity boundary
Sovereign eID · national trust list
Regulatory posture
+ jurisdictional (NSM · SDAIA · NCA · Cloud Act exempt)
Patch cadence
30-day staged · sovereign ops window
Uptime SLA
99.9% per facility · DR pair
Audit retention
Append-only · regulator-defined (often 10y+)
Pilot-to-production
120–180 days
Full deployment architectureProcurement & RFP intakeNumbers reflect default contractual baselines · per-deployment uplift available
PL.01
Platform Ecosystem Architecture
8 platforms · 7 infrastructure modules + 1 marketplace

One infrastructure ecosystem. Modular deployment platforms.

Governments, universities, transport operators and marketplace builders deploy FlyttGo platforms as modules. See the full ecosystem.

OF.00·Module orchestration flow
OF.01Identity→ IdentraOF.02Payments→ PayveraOF.03Mobility→ TransifyOF.04Workforce→ WorkvergeOF.05Financial ops→ Ledgera

FlyttGo Technologies Group platforms operate together as a modular infrastructure ecosystem supporting mobility coordination, workforce deployment, education intelligence, identity verification, payment orchestration and financial operations automation across cities, enterprises and government environments.

Ledgera integrates with Payvera and reports across Transify, Workverge, Civitas and EduPro.

IN.03
Institutional Deployment Sectors
9 sector profiles · public + enterprise · platform-mapped

Built for the institutions that actually run cities and regions.

Ministries, municipalities, universities and transport operators deploy FlyttGo platforms at pilot, metro or national scale. Industries overview.

TX.04
Infrastructure Stack Architecture
6 layers · service delivery → cloud-native runtime

A six-layer stack engineered to be deployed.

Multi-tenant, region-aware, standards-based. Architecture overview.

L5Service deliveryCivitas · EduPro · FlyttGo MarketplaceL4Mobility orchestrationTransify · WorkvergeL3Payments + financial opsPayvera · LedgeraL2Identity + authIdentra · OIDC · SAML · eIDASL1Data exchangePostgreSQL · PostGIS · Redis · KafkaL0Cloud-native runtimeNext.js · NestJS · Docker · Kubernetes · AWS · Azure · GCP
See full architecture
CR.00Trust center · alignment registry

Security, compliance & deployment readiness.

Certification alignment enables FlyttGo deployments to operate within enterprise security frameworks and regulated-sector infrastructure environments.

PLATFORM-LEVEL ALIGNMENT·CR.01–04
MODULE-SPECIFIC REGULATORY COMPATIBILITY·CR.05–06

FlyttGo platform infrastructure is designed to support regulated-sector deployments and certification-aligned operating environments across public-sector and enterprise implementations.

CR.RM·Certification pathways supported
  • ISO 27001
  • SOC 2 Type II
  • Public-sector sovereign deployment compliance environments

Pathways indicate engineered capability to operate inside the named compliance environment. Formal third-party attestation lands separately and is published on the security architecture page.

PR.00Procurement compatibility

From pilot to national infrastructure.

FlyttGo deploys at five procurement tiers — pick the tier that matches your programme. Frameworks, scope, cadence and statutory artefacts are pre-shaped per tier; engineering response within one business day.

  1. PR.01
    Pilot deployments
    60–90 days
  2. PR.02
    City rollouts
    90–150 days
  3. PR.03
    Regional deployments
    4–9 months
  4. PR.04
    National infrastructure programmes
    6–18 months
  5. PR.05
    White-label platform licensing
    Per agreement
See full procurement matrixSchedule infrastructure architecture discussionEngineering response within one business day
PR.05
Deployment Procurement Guide
6 questions · timeline · compliance · multi-tenancy · sovereignty

Common questions from deployment partners.

If your RFP or procurement process needs detailed answers on compliance, data residency, SLAs or commercial terms, request a solution brief.

  • A standard FlyttGo deployment goes from procurement sign-off to a production-ready tenant in 60–120 days, depending on deployment mode. Sovereign datacenter installations add 30–60 days for network and hardware provisioning.

Talk to deployment engineering
CT.06Deployment Engagement

Ready When You Are

Start Deploying Your Platform Infrastructure Today

Scope a deployment with the FlyttGo platform team — from pilot tenant to national rollout, across logistics, education, government and white-label workforce platforms.

Deploy your platform infrastructureSchedule infrastructure architecture discussion
Deployment lifecycle
  1. LF.01·60–120 days
    Pilot
    Single tenant · 1 region
  2. LF.02·6–12 months
    Regional rollout
    Multi-tenant · 1–3 regions
  3. LF.03·12+ months
    National rollout
    Federated · sovereign-ready
  • Multi-region · EU · AF · MENA
  • Modular platforms · Independent licensing
  • 60–120 day deployment cycle