Enterprise Data Catalog
The Enterprise Data Catalog empowers organizations to unlock the full potential of their data. Acting as a centralized hub, it simplifies data discovery, strengthens governance, and ensures every team member can access, understand, and trust the data they need to drive business success.
Designed with collaboration and efficiency in mind, the catalog transforms scattered data into a strategic advantage—helping businesses create a data-driven culture where insights are just a few clicks away.
Key features at a glance
Data Discovery: Uncover and understand the right data quickly with intuitive search and exploration tools.
Agile Data Governance: Manage data access, quality, and compliance seamlessly across your organization.
Data Lineage: Visualize the journey of your data—from its origin to its transformation—ensuring accuracy and trust.
AI Context Engine: Supercharge insights by embedding your business context into generative AI, delivering smarter, faster results.
The Enterprise Data Catalog is geared towards businesses looking to harness their data for strategic advantages, ensuring data quality, compliance, and fostering a data-driven culture. Learn more about the Enterprise Data catalog
Deployment options
Every organization is different, and so are its data needs. That is why the Enterprise Data Catalog offers three flexible deployment options:
Public instance on multi-tenant platform
Private instance on multi-tenant platform
Single-tenant installation
Public instance on multi-tenant platform
Public instances on the multi-tenant platform offer the ability to share data with and use data from the broader data.world community and other organizations. Public instances live on data.world multi-tenant shared infrastructure, which offers enhanced performance, scalability, and manageability.
If your institution wants to publish data or discover new data from a wide audience, a Public instance is ideal.
Enterprise catalog resources are stored securely in the organization namespace.
Users create accounts as part of the open data community, but as the enterprise you can set up single sign-on (SSO) to ensure only authorized users can access the catalog resources in the organization namespace.
Private instances offer some tailoring of the user experience, including a Browse card on Organization profile pages for curated navigation shortcuts.
Private instance on multi-tenant platform
Private instances offer the benefits of a multi-tenant SaaS infrastructure with enhanced security, ensuring users and content remain isolated from the broader data.world community. This option also provides customization to suit your enterprise needs. If you require strong assurances that data and users won't be shared outside your company, a Private instance is suitable.
Both the users and the resources within Private instances are completely logically isolated. Users in a Private instance cannot access community resources or resources in other Private instances, and vice versa.
User accounts are owned by the enterprise and revert to the enterprise if users leave. Enterprise single sign-on and SAML are used for validation and authorization.
Every Private instance has a private corporate community representing the activity across the company and datasets that have been set as discoverable.
Private instances provide an enhanced user experience, featuring tailored options such as a Browse card on the Application home page for curated navigation shortcuts. This is in addition to the Browse card found on Organization profile pages.
Single-tenant installation
Single-tenant architecture dedicates a separate application and infrastructure environment for each customer. This model provides additional security and compliance by using isolated infrastructure accounts.
Single-tenant provides all the same benefits as Private instances with the security controls of a walled garden, and UX customization options, with an additional layer of security: a fully separate cloud infrastructure account. If your security and compliance policies require an isolated infrastructure account, then Single-tenant may be right for you.
Logical isolation: Both the users and the resources within Single-tenant are completely logically isolated. Users in a Single-tenant cannot access community resources or resources in other Single-tenant or Private instances, and vice versa.
Account-level isolation: The servers underlying the data.world installation use a separate cloud infrastructure account from any other customer. Some customers require account-level isolation as part of their security and compliance policies, and this deployment option enables that.
Key features of deployment options
The following table highlights the key features of each deployment option so you can choose the best fit for your organization.
Features | Deployment options | ||
|---|---|---|---|
Multi-tenant | Single-tenant | ||
Public instance | Private instance | ||
Enterprise single sign-on (SSO) | ✅ | ✅ | ✅ |
✅ | ✅ | ✅ | |
User accounts | Bring your own user with enterprise SSO | Separate corporate user accounts | Separate corporate user accounts |
Directly access open data community datasets and organizations | ✅ | - | - |
Custom sub-domain [you].app.data.world Note: The customer sub-domain is defined by the customer during the deployment process. The system allows alphabets (case insensitive) numbers between 2 and 26 characters) with no special characters in the sub-domain name. For example, it can be eight8bank.app.data.world | - | ✅ | ✅ |
Logical isolation (walled garden) | - | ✅ | ✅ |
Private corporate community | - | ✅ | ✅ |
Account level isolation | - | - | ✅ |