Data Clan Identity and Trust services

Choose the right identity and trust services.

Explore what each service establishes, how the responsibilities fit together and how to put them to work. Start with the service overview and deployment guide, then go deeper where your connection needs it.

How the three services fit Service scope and deployment

Guides for your next conversation.

Common questions.

Do I need all three services?

Start with the service your outcome needs. dc:id provides identity and access, dc:pki provides private certificate trust, and dc:trust provides scheme governance and assurance. Plan their integration where the business relationship spans more than one.

Does dc:id replace Microsoft Entra ID, Google or Okta?

dc:id connects configured Microsoft, Google and Okta providers and provides managed application identities, native sign-in and organizational administration. Compare provider coverage, lifecycle needs, deployment and operating responsibilities with your wider environment.

Can I use my own branding?

Yes. Portable branding and Customer Accounts provide a consistent experience across dc:id, dc:pki and dc:trust, while preserving existing tenant overrides. Profile transfer keeps local permissions and email-sender approvals separate.

Are dc:pki certificates publicly trusted?

dc:pki provides private certificates for systems configured to trust your authorities. These differ from certificates automatically trusted by public web browsers.

How do we use post-quantum certificates?

Use dc:pki’s ML-DSA certificate hierarchies alongside RSA options. Confirm TLS key establishment, credential formats and client/server compatibility across the complete connection.

Can the services be self-hosted?

Yes. Self-hosting gives your organization control over its environment. Agree hosting, maintenance, integration and support responsibilities for the services you adopt.

What does it cost?

Contact Data Clan to discuss the product, deployment and support scope you need. Pricing and service terms are agreed for that scope.

How do we get started?

Start with one application, private connection or participant role. Data Clan can help define the requirements, connect the services and agree a practical implementation.

Where is this available?

Data Clan is UK-based, with availability in other regions on request. Discuss your required region, deployment and data-location requirements with us.

Can people have accounts directly in dc:id?

Yes. Native registration, passwords, passkeys, authenticator MFA, email codes or confirmation links, and recovery support accounts directly in dc:id.

Can customers manage their own organizations and users?

Yes. Customer workspaces, organization memberships, application assignments, scoped roles and user/session controls support delegated administration of the resources assigned to each administrator.

Can applications use dc:id without a person signing in?

Yes. Standard machine application management supports client-credentials access, explicit API scopes, short-lived tokens and managed secrets. Each receiving API validates and enforces the agreed access contract.

Will dc:pki renew and install every certificate automatically?

dc:pki provides issuance, revocation, policy controls and integration APIs. The consuming application’s integration determines renewal scheduling, installation and trust distribution. Agree that lifecycle as part of implementation.

Is dc:id for enterprise identity management as well as customer access?

Yes. dc:id supports workforce and external application sign-in, organizational access and machine identities, with configured federation, native sign-in, roles and delegated administration.

What does dc:trust provide?

dc:trust connects frameworks, versioned schemes, participant agreements, evidence, assessment and independent approval. Member submissions, scoped decisions, change feeds and protected archival support connected assurance workflows.

Does signing in or holding a certificate establish accreditation?

Identity and certificates establish different facts from scheme assurance. dc:trust records an evidence-based decision for an assessed role; it does not make every signed-in identity or certificate holder an accredited participant.

Will customer account imports synchronize every service?

Account and branding packages support explicit portability. Memberships, resource permissions, credentials and approved email identities remain local, with export and import providing the synchronization mechanism.

What is dc:trust responsible for?

dc:trust provides framework governance and participant assurance. dc:id provides authentication and identity administration; dc:pki provides certificate authorities, issuance and revocation.

What would a more trusted connection make possible?

Tell 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 services

The wider expertise behind Identity and Trust.

Explore 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