dc:id
Connect familiar account providers, shape sign-in around your service and give applications explicit API access. Support native sign-in and organizational administration with clear permissions and ownership.
Explore identity and accessdc:id manages identity and application access. dc:pki manages private certificate authorities, issuance and revocation. dc:trust manages scheme rules, participant evidence, assessment and accreditation decisions.
Choose a service for an immediate need, or plan them together around one business journey. Authentication, cryptographic trust and assurance each contribute a distinct part of a connection you can explain.
Explore the three services Explore dc:trust Plan your implementationConnect familiar account providers, shape sign-in around your service and give applications explicit API access. Support native sign-in and organizational administration with clear permissions and ownership.
Explore identity and accessIssue private certificates under clear authority, purpose and lifetime rules. Keep application keys at their source, support offline-root custody and plan how connected systems use trust and revocation information.
Explore private certificate trustTurn a scheme’s requirements into a visible assurance process. Connect participants, agreements, evidence and independent approval, then track whether accreditation remains current.
Explore framework assuranceMake access feel like your service. Give applications a clear purpose. Keep private certificate trust under your control. Make scheme assurance decisions from clear rules and evidence.
This 30-second highlights film introduces dc:id identity and access, dc:pki private certificate trust and dc:trust scheme governance and assurance, including participant evidence and independent approval.
All key messages appear on screen, so the film works without sound. ML-DSA mutual TLS requires compatible systems.
Explore the dc:trust assurance service for scheme governance, participant evidence and independent approval.
Watch the 30-second highlights Explore the illustrated dc:pki walkthrough Discuss your first connectionData Clan connects software delivery with data, operating models and organizational responsibility. Shape the identity journey, certificate service and assurance process around the result you need.
Discuss self-hosting, supported operation, data location and integration requirements with a UK-based team. Agree service scope, integration and operating responsibilities.
Cross-service customer branding and Customer Accounts carry a consistent customer experience across the services while preserving local resource permissions and existing sign-in overrides.
Review Data Clan’s corporate Cyber Essentials Plus certificate and the scope recorded in the registry. Corporate certification and a participant’s scheme accreditation are separate assurance decisions.
Compare the services and alternatives Review service scope and deployment Explore the wider Data ClanUse dc:id to connect supported identity providers and explicitly managed application identities. Agree what the receiving service must validate and allow.
Use dc:pki to issue private certificates under your authority’s rules, then configure relying systems to validate the connection and current revocation information.
Use dc:trust to organize scheme requirements, agreements and role-specific evidence. Record an assessment and approval by a different person, with a history that remains available when circumstances change.
Name the people responsible for identity, key custody, evidence review and ongoing support. Each service retains its own permissions and responsibilities.
A customer portal can begin with dc:id. A private service integration can begin with dc:pki. An industry scheme or partner network can begin with dc:trust’s operator workflow.
When the challenge spans all three, plan identity, certificate trust and assurance together. A signed-in account or a valid certificate does not, by itself, establish that an organization meets a scheme’s requirements. Your relying service must enforce the permissions and decisions appropriate to its work.
Explore business use cases Plan how the services connectThe shared customer-branding profile carries organization and service names, logos, colours, light and dark themes, and support links between dc:id, dc:pki and dc:trust through explicit export and import.
Customer Accounts group the service resources a customer owns or can access. Each service checks its own identity, tenant or workspace permissions. In dc:id, an existing tenant’s explicit sign-in branding can remain independent of the account default.
Account and branding portability preserves local memberships, credentials and sender approvals. Configure customer-owned domains and approved email identities through the relevant service and provider arrangements.
Plan a branded customer experience Discuss your customer journeyTell us who needs to connect, what they need to do and what evidence would give your organization confidence. We can explore dc:id, dc:pki, dc:trust or a combination, then agree a focused next step.
For dc:trust, include the scheme or network you operate and the roles you need to assess. For identity or certificates, name the application or service connection. UK-based support and availability in other regions are agreed around your requirements.
Discuss Identity and Trust servicesExplore Data Clan’s data, technology and organizational expertise, meet the people and review the work behind our approach.
Data Clan — company and expertise Meet the Clan Policies and supplier assurance