Sunbird RC (Registries & Credentials)

Open-source registries and verifiable-credential building blocks with named-cloud deployments.

4 sources checked by an editor on · Product website ↗

Deployment terms: BYOC · control plane · data plane · private offer

· Open requirements shortlist · Estimate operating costs

Compare this listing with another →

What lands where

  1. Supplied by

    Vendor or project

    CloudFormation; Terraform; Helm / Kubernetes operator; Kubernetes manifests

  2. Operated by

    Your team

    Customer operates the application and its cloud resources, including secrets, backups, monitoring and upgrades. Review any support access and configured external services; preserve application data, configuration and keys for migration or exit.

Deployment boundaries by provider
  • AWS: Customer cloud account · Customer-operated

    Resources in the customer's cloud account, subscription, project or tenancy. Managed cloud services still have shared responsibilities.

    AWS CDK ↗ · Source checked 2026-11-19

  • Google Cloud: Customer cloud account · Customer-operated

    Resources in the customer's cloud account, subscription, project or tenancy. Managed cloud services still have shared responsibilities.

    GCP Terraform ↗ · Source checked 2026-11-19

Application operations and account ownership are separate from infrastructure operations. Confirm external services, telemetry, support access and backup destinations for the chosen path.

Install methodCloudFormation; Terraform; Helm / Kubernetes operator; Kubernetes manifests
InfrastructureServers / containers
Sunbird RC services, database and identity/storage dependencies deployed by AWS CDK/Helm or GKE Terraform/Helm. Persistent application containers and VMs are classified as servers even when the provider manages their infrastructure.
Licensing modelOpen Source / Open Core
MIT for the reviewed upstream edition; optional commercial services and bundled components have separate terms.
LicenseMIT for the reviewed upstream edition; optional commercial services and bundled components have separate terms.

Buyer diligence

Answers apply to the reviewed edition and deployment. Expand a row for qualifications and sources.

How to read these facts

Not researched means no field-specific review is recorded. Not confirmed means sources were checked but did not establish an answer. Availability, eligibility and edition-dependent findings retain the scope given in their evidence. A vendor’s hosted-service certification does not automatically cover your deployment. Evidence coverage is not a feature score.

5 of 12 fields researched (42%) · 3 documented · 2 unresolved. Evidence coverage is not a feature score.

Single sign-on
Not confirmedEvidence and scope for Single sign-on

The registry architecture uses Keycloak for authentication and its entity API documents token generation. A separate guide describes Meripehchaan SSO using a custom Keycloak 14-based build with configurable nonce validation. This does not confirm a currently supported, version-matched external IdP/browser-login path for every RC 2.1 deployment or frontend; verify broker/client, claims/roles and dependency compatibility.

Documented custom integration and old dependency boundary; current release/installation-wide federation remains unconfirmed · Source ↗ · Registry identity component scope ↗ · Entity authentication is a separate token path ↗ · Reviewed 2026-11-20

Sources checked — unresolved · Editor reviewed.

Deployment artifact / IaC
DocumentedEvidence and scope for Deployment artifact / IaC

The reviewed source supplies deployment configuration for Sunbird RC services, database and identity/storage dependencies deployed by AWS CDK/Helm or GKE Terraform/Helm. Set organization-specific secrets, networking, storage and compatible image versions before use.

Reviewed deployment source collection; application images and infrastructure components have separate versions · Source ↗ · Deployment artifact ↗ (main (moving branch)) · Reviewed 2026-11-19

Documented · Editor reviewed.

Minimum footprint / sizing
Not confirmedEvidence and scope for Minimum footprint / sizing

The official architecture and deployment recipes span registry, PostgreSQL, identity, search and optional workflow/queue services, but do not establish a current whole-stack CPU/RAM/storage minimum for this workload. Enabled services, registry records, credentials, query rate and replicas must be sized separately; a sample cluster is not a 1 TB HA capacity guarantee.

Registry component scope; current numeric workload and HA sizing remains unconfirmed · Source ↗ · Official AWS CDK/Helm deployment collection ↗ · Reviewed 2026-11-20

Sources checked — unresolved · Editor reviewed.

License pricing
DocumentedEvidence and scope for License pricing

MIT for the reviewed upstream edition; optional commercial services and bundled components have separate terms.

Sunbird RC (Registries & Credentials); software terms only, excluding cloud charges, labour and separately licensed services · Source ↗ · Reviewed 2026-11-19

Documented · Editor reviewed.

Release snapshot / cadence
DocumentedEvidence and scope for Release snapshot / cadence

Reviewed upstream v2.1.0 release. Provider images and packages have separate versions; this snapshot does not establish support duration or a future release cadence.

Sunbird RC (Registries & Credentials) upstream application; verify compatibility with the selected package · Source ↗ · Reviewed 2026-11-19

Documented · Editor reviewed.

Show all fields (7 not researched)
Marketplace delivery
Not researched Supply a public source.
Cloud commitment eligibility
Not researched Supply a public source.
SCIM provisioning
Not researched Supply a public source.
Compliance attestations
Not researched Supply a public source.
Security controls
Not researched Supply a public source.
Air-gapped operation
Not researched Supply a public source.
Operating cost estimate
Not researched Supply a public source.

Scope & considerations

The product is a registry and credential platform. Municipal permitting or licence-renewal workflows require a separate configured application. Deployment packaging and individual registry-component releases have independent versions and licences.

Community & maintenance

The reviewed upstream contributor history includes tejash-jl, jyotsnaraveendran, dileepbapat, alongside the project installation and maintenance history. This establishes community participation, not a commercial support or production-capacity guarantee.

Category fit

Backend platforms
Open-source registries and verifiable-credential building blocks with named-cloud deployments.

Compare within Backend platforms

  • Appwrite Self-HostedSelf-hosted backend services for authentication, databases, storage, functions and messaging.
    • AWS
    • Azure
    • Google Cloud
    • DigitalOcean
    Customer-operated · Open Source / Open Core
  • Gravitee API Management Self-HostedOpen-source and commercial self-hosted API management platform with documented EKS, AKS and GKE deployment paths.
    • AWS
    • Azure
    • Google Cloud
    Customer-operated · Open Source / Open Core
  • HashiCorp Consul EnterpriseCommercial service networking, discovery and service-mesh platform deployed into customer cloud infrastructure.
    • AWS
    • Azure
    • Google Cloud
    Customer-operated · Commercial Only
  • Hasura GraphQL Engine v2GraphQL API engine that exposes connected databases through permission-aware application APIs.
    • Azure
    • Google Cloud
    Customer-operated · Open Source / Open Core
  • KeystoneJS (Keystone 6)Self-hosted content backend with a configurable GraphQL API and administration interface.
    • Northflank
    Customer-operated · Open Source / Open Core
  • Kong Gateway Self-ManagedOpen-source and commercial self-managed API gateway with supported AWS, Azure and Google Cloud deployment platforms.
    • AWS
    • Azure
    • Google Cloud
    Customer-operated · Open Source / Open Core
  • Medplum Self-HostedOpen-source FHIR healthcare backend, clinical application and automation platform deployed in customer cloud infrastructure.
    • AWS
    • Azure
    • Google Cloud
    Customer-operated · Open Source / Open Core
  • Parse ServerNode.js application backend for data APIs, users, permissions and server-side application logic.
    • AWS
    • Azure
    • Google Cloud
    • DigitalOcean
    • Heroku
    Customer-operated · Open Source / Open Core

Showing 8 of 11 other listings in Backend platforms. These products address related workflows; read their category-fit notes before comparing scope. See all of Backend platforms →

Installation outline

  1. Choose the documented deployment option and a dedicated cloud environment. Follow the launch methodology.
  2. Review the vendor's installation documentation, required permissions and outbound data flows.
  3. Deploy to a non-production environment; configure identity, networking and monitoring.
  4. Test backup recovery and upgrades before promoting to production.

Watch this listing with RSS

Evidence trail

Every claim on this page traces to the sources below. They document the deployment option; they do not constitute a security certification.

  1. Deployment sourcesChecked
  2. Cloud deployment evidenceChecked

    The linked sources describe each deployment path, edition and support scope. Community templates and partner statements are identified in the notes.

    • AWS CDK ↗ · AWS

      Vendor / upstream documentation · Reviewed 2026-11-19. Vendor support commitment: not assessed; confirm the selected release and contract.

      Sunbird RC services, database and identity/storage dependencies deployed by AWS CDK/Helm or GKE Terraform/Helm. The product is a registry and credential platform. Municipal permitting or licence-renewal workflows require a separate configured application. Deployment packaging and individual registry-component releases have independent versions and licences.

    • GCP Terraform ↗ · Google Cloud

      Vendor / upstream documentation · Reviewed 2026-11-19. Vendor support commitment: not assessed; confirm the selected release and contract.

      Sunbird RC services, database and identity/storage dependencies deployed by AWS CDK/Helm or GKE Terraform/Helm. The product is a registry and credential platform. Municipal permitting or licence-renewal workflows require a separate configured application. Deployment packaging and individual registry-component releases have independent versions and licences.

  3. Infrastructure evidenceChecked
  4. Licensing evidenceChecked
  5. Community & maintenance evidenceChecked

Suggest a correction · Back to directory