Domain Neutral Persistent Identifiers for the Modern Web

Data GUIDs enable you to mint globally unique identifiers for data in a scalable distributed architecture.

Learn more

Our Core Features


Supports trillions of GUIDs across a distributed set of commons. Never worry about too many GUIDs again!

Open Source

The platform is open for modification and inspection. Pull requests welcome.


Lookups are free and minting is free. Always.



Unopinionated namespaces allowing for distributed lookups and global uniqueness.

Elegant Design

Crafted with extreme care for the Data Biosphere.


Use the Data Object Service API to resolve your GUIDs today.


Data GUIDs for all of your identifier needs

Data GUIDs were created by the Data Biosphere in order to meet their needs of tracking data across platforms both externally and internally. Data GUIDs only require a hash and a file size in order to be minted. URIs for the data and metadata about the data can be added later. These key capabilities enable Data GUIDs to be used to track live data, data being processed in workflow pipelines, and data being backed up to cold storage.

Resolve a Data GUID

Turn your Data GUID into information you can use!


Data GUIDs Review

Data GUIDs are are the way to go for identifying your data objects. I love the prefixes feature, which helps you resolve the location of the data object given the GUID. With the global uniqueness and the prefixes, these data GUIDs are also FAIR compliant.


Principal Investigator

A very common problem for programmers is describing data in such a way that does not assume its location. Data GUIDs provide an easy-to-use and extensible namespace for describing data that gives programmers confidence their data can be later reused, or retracted. By decoupling data representation from data access, Data GUIDs allow a ground up representation of uniqueness that can span most cloud and on-premises service architectures. That means that software written around Data GUIDs will be easier to migrate from one platform to another, and that strong guarantees can be given that two parties are computing on the same data.


Bioinformatics Programmer

It was always a burden when my identifiers were only unique within a database. Merging databases? Pulling data objects from multiple locations for analysis? What a headache! But with globally-unique identifiers for my data, I can analyze without worrying about identifiers being duplicated and my analysis being sullied. Well, at least being sullied by duplicate IDs. Thanks!


Project Manager

As a software architect, I appreciate that the GUIDs keep my end users happy. My software mints globally unique identifiers in multiple data commons or other storage solutions–GUIDs for files, for datasets, or even for collections of datasets–and then my users can search multiple data commons, know the data’s “home” database, and then do their analysis. They can even build apps on top of my software to automate much of the process. And when my users are happy, I’m happy.


Lead Software Architect