# Decentralisation, OpenSource Overview and Compatability

**Decentralisation**

The platform will be decentralised where efficient solutions can be found but not at the expense of user experience or overall objective of building a universal profile.

Areas where decentralisation is likely:

* Trust Registries (issuers ie trusted orgs) - DIDs are onchain (in time will support multiple DID methods (if beneficial) so any user or org can leave profile with their DID intact.
* Badges (soulbound nfts and vcs) are on chain and so users are not bound to profile.io.

**OpenSource Approach**

Ensure composable elements of user profiles are opensource to ensure compatibility across web frameworks and apps.

Issuer components can also be open sourced.

To consider each element of the infrastructure in terms of suitability for open source.

Core platform updates will be determined by central team unless a point is reached where an alternative approach is required.

**Compatibility**

Credential Issuance and verification is open to multiple technical approaches, networks (and offchain credentials) and providers, with profile.io as a selected destination for credentials. We will engage wider developer community to achieve this compatibility.

App/Dapp integration requires standardised approach to integration.

Profile composable elements and ZK authorisation to be compatible across tech stacks via open source approach.


---

# Agent Instructions: Querying This Documentation

If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://docs.profile.io/system-overview/decentralisation-opensource-overview-and-compatability.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.