Centre for Digital Public Infrastructure
english
english
  • THE DPI WIKI
    • πŸŽ‰About the DPI Wiki
    • πŸ”†What is DPI?
    • ✨DPI Overview
    • πŸ“DPI Tech Architecture Principles
      • πŸ”—Interoperability
      • 🧱Minimalist & Reusable Building Blocks
      • πŸ’‘Diverse, Inclusive Innovation
      • πŸ’ Federated & Decentralised by Design
      • πŸ”Security & Privacy By Design
    • 🎯DPI Implementation & Execution Guidance
    • πŸ†šDPG and DPI
    • ❓What DPI can I build?
    • πŸ₯‡First use case for DPI
    • πŸ“˜Inputs for designing a DPI informed digital transformation strategy
    • πŸ’°How much does it cost to build DPI?
    • πŸ“’Is my system a DPI?
      • TL; DR - Is my system a DPI?
  • Mythbusters and FAQs
    • πŸ”―DPI and Mandating Adoption
    • πŸ”―DPI and Private Competition
    • πŸ”―DPI and Privacy / Security
    • πŸ”―DPI and the Digital Divide
  • Technical Notes
    • πŸ†”Identifiers & Registries
      • Digital ID
        • Capabilities on ID system
        • ID-Auth
        • Face Authentication
        • eKYC/ Identity profile sharing
        • Single Sign On (SSO)
        • QR Code for Offline ID
    • πŸ“‚Data Sharing, Credentials and Models
      • A primer to personal data sharing
      • Data standards
      • Verifiable Credentials
      • Building Data Analytics Pipelines
      • eLockers
      • Non-personal Anonymised Datasets
    • πŸ”Trust Infra
      • Digital Signatures and PKI
      • eConsent
      • eSign
    • πŸ›’Discovery & Fulfilment
      • Platforms to Protocols
    • πŸ’ΈPayments
      • Financial Address
      • Interoperable QR Code
      • Interoperable Authentication
      • Interoperable Bill Payments
      • Cash in Cash Out (CICO)
      • Financial Address Mapper (G2P Connect)
      • G2P Payments
  • Initiatives
    • 🌐DPI advisory
    • πŸš€DPI as a Packaged Solution (DaaS)
      • πŸ’‘Why do we need DaaS?
      • 🎯DaaS in a nutshell
      • πŸ“¦Pre-packaged DaaS kits
      • ♻️Reusable DaaS Artefacts
      • 3️⃣A 3-step process from idea to implementation!
      • πŸ“ˆFunded DaaS Program overview
      • πŸ‘©β€πŸ’»Cohort 1: DaaS Offerings
        • Digital authentication
        • Digital credentials
        • ID Account Mapper
      • πŸ–₯️Co-create with us!
      • πŸ’¬Upcoming DaaS cohorts
        • Functional Registries
        • AI Assistant
      • ❓FAQs on DaaS
        • Country x DPG MOU /LoI FAQs
        • Ecosystem Participation Terms FAQs
    • πŸ“‘DPI Residents Program
    • βš–οΈDPI-CPA
    • πŸ’ΈG2P Connect
    • πŸ“¨User Centric Credentialing & Personal Data Sharing
    • βš•οΈDPI for Health
    • 🌍Agri Connect (forthcoming)
  • References
    • Glossary
    • Curated Specifications
  • Additional Info
    • 🀝Licensing
    • ✍️Contact Us
Powered by GitBook
On this page
Export as PDF
  1. Initiatives
  2. DPI as a Packaged Solution (DaaS)

DaaS in a nutshell

PreviousWhy do we need DaaS?NextPre-packaged DaaS kits

Last updated 6 months ago

DPI as a packaged Solution (DaaS) refers to rapid deployment of DPI, through (instead of greenfield implementations) through non-procurement routes.

There are multiple operational modules for DaaS:

  1. Benefit from Open Source Artefacts + Funded & Pre trained Service Provider: Countries can choose to join the to receive of their chosen product (digital public goods), and pre-trained service provider (trained by the digital public good owner) to support deployment, along with policy frameworks, program management kits, legal templates and costing models.

  2. Benefit from only Open Source Artefacts: Countries can also choose to reuse any of the reusable implementation DaaS to rapidly upgrade their existing systems to DPI (for example, reusing an eSign module to add authentication on any ID) using an existing vendor, at their own cost and according to their own timelines.

  3. Benefit from only Pre-trained Service Provider: Countries can also choose to deploy an offering from a private pre-existing vendor who has been trained under the DaaS program by the DPG owner

The reason DaaS stresses on non-procurement is to ensure rapid deployments of minimalist DPI blocks that can exponentially increase benefits to individuals and institutions in society - and procurements by governments, while necessary in some cases, tend to be a year or two long process and are not required for simple upgrades to existing systems.

DaaS differs from traditional pilots or POCs because the infrastructure is built for population-scale from day one using country resources and capacity, and can reach full coverage in a matter of months. This is supported by the fact that DaaS applies only to minimalist layers such as authentication on top of existing ID (and not ID enrolment itself - which even on a best-effort basis would take years to cover the whole population).

Regardless of whether countries choose to join the funded DaaS cohort or independently execute DPI blocks, it can be helpful to that can help expedite the process of execution, regardless of the DPI block chosen, the choice of vendor, or the scale of execution.

DaaS will fast track DPI adoption to any β€˜hard to reach areas’, applicable beyond the globalisation effort.

‒⁠ ⁠reusable for sub national/state level adoption within any large countries (such as state level registries)

‒⁠ reusable wherever decentralised private adoption of a module is required (such as verifiable credentials)

A presentation on DaaS can be viewed here:

πŸš€
🎯
upgrades of existing infrastructure
funded DaaS program
pre-packaged offerings
artefacts
reuse some standardised DPI artefacts