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 for Child Rights
    • 💸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
  • Piloting DPI via DaaS is now a simple 3-step process!
  • How DaaS Solves Speed, Cost, Data Ownership, and Capacity Constraints
Export as PDF
  1. Initiatives
  2. DPI as a Packaged Solution (DaaS)

A 3-step process from idea to implementation!

PreviousReusable DaaS ArtefactsNextFunded DaaS Program overview

Last updated 11 months ago

Piloting DPI via DaaS is now a simple 3-step process!

  1. Countries can choose the use case they want to pilot after reviewing the products on offer

  2. Have conversations with CDPI, DPGs, and ecosystem market players to understand and procure the DPI DaaS package

  3. Configure it to their systems and infrastructure with the help of pre-trained Service providers who can support (along with the DPG) building local capacity for long term scale and sustainability of the DPI.

How DaaS Solves Speed, Cost, Data Ownership, and Capacity Constraints

The benefits of the DaaS approach are manifold:

  1. Significantly faster rollout

  2. Less costly due to minimal upfront costs, smaller teams, and use of open-source components

  3. Clear government ownership of the core IP of the system, data, and cloud instance

  4. Significantly reduced tech capacity requirements

  5. Ability to shift from input (capex) to outcome (opex) based costing (i.e., pay per user, not for each input cost)

  6. Can help tackle incumbency issues to demonstrate proof of concept as a convincing argument

  7. Choice of one or more service providers at the same time

  8. Choice of clouds and portability

  9. Achieve scale and speed to de-risk churn and changes within the system

🚀
3️⃣