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
  • DaaS is not very different from what governments already do today!
  • DaaS is simply a combination of these things - a small innovation that we believe could have a big impact.
Export as PDF
  1. Initiatives
  2. DPI as a Packaged Solution (DaaS)

Pre-packaged DaaS kits

PreviousDaaS in a nutshellNextReusable DaaS Artefacts

Last updated 8 months ago

The pre-packaged DaaS kits offer an easily deployable model for various DPI building blocks through packaged product pilots. Through DaaS, you can easily demonstrate proof of success of the DPI approach for your use case, country, context, and outcomes - helping build traction for a full-scale rollout.

The DaaS products significantly reduce the time, cost, and workforce required to build local, use-case driven DPI. While open-source projects offered by Digital Public Goods (as shown in the diagram above) reduce the time taken to build core DPI components, they do not today reduce the time needed for deployment, and technology management infrastructure.

DaaS combines best-in-class open-source DPGs with a new class of pre-trained technology service providers to pre-package DPI for ready deployment for pilots. In addition to this, it combines program and policy guidance so that the time to deployment of the DaaS package is further reduced.

DaaS thus leverages best-in-class Digital Public Goods (DPGs) to create a pre-built package that every country can use to test out a pilot, using a set of pre-trained Technology Service Providers. Countries retain full control over the pilot and all systems built (including the IP), and can customise (by adding extensions) the systems post the pilot and before they scale.

Countries can also select the type of cloud they prefer - public or private clouds - to drive growth, inclusion and scale. Private clouds may be more appropriate under some data protection regulatory frameworks. Countries can also choose to host the package on-prem if they have the hosting infrastructure.

DaaS is not very different from what governments already do today!

DaaS brings together elements that have been a part of digital governments and national infrastructure building for generations:

  1. Cloud (public or private) is not new - it is used for a variety of government digital services.

  2. Packaged product software purchases are not new - they are part of routine government operations (such as through the Microsoft suite, Email providers, etc.)

  3. Open Source DPGs are not new either - multiple governments use open-source components such as X Road for data sharing or open protocols for best-in-practice tech principles.

DaaS is simply a combination of these things - a small innovation that we believe could have a big impact.

🚀
📦