DataMapper Setups: Private Tenant vs Multitenant
Read more below on the two setups and their features as well as the benefits and downsides by choosing the one or the other. If you wish to know more, please check the provided links in the description below.
DataMapper Set-Ups: Multitenant vs. Private Tenant
A. Multitenant Set-Up
In the multitenant setup, DataMapper hosts multiple customers' data within a shared Azure tenant located in the West Europe region. This setup leverages Azure's robust infrastructure to provide a secure and scalable environment where customers' data is logically separated but physically co-located.
Key Features:
- Shared Azure Tenant: Customers' data resides in a shared Azure tenant managed by DataMapper.
- Resource Groups: Each customer has their own dedicated resource group within the shared tenant, ensuring logical isolation and management of their resources.
- Location: All data is stored in Azure's West Europe data center.
- Security: Implements stringent security measures including data encryption, access control, and continuous monitoring to ensure data integrity and confidentiality. Detailed security information can be found here.
- Data Processing:
- Metadata and JSON Storage: Stores metadata and a JSON file of the content, not the original file.
- Text Extraction and OCR: Uses text extraction or OCR scanning if necessary to process the text.
- AI/ML Processing: Applies AI/ML algorithms to detect risks in the data and enable search functionalities.
- Metadata Storage: Retains parts of the metadata (e.g., document owner, created date, location) to display information like file age and path.
B. Private Tenant Set-Up
The private tenant setup allows customers to have their data stored within their own Azure tenant, providing an added layer of control and customization over their data environment.
Key Features:
- Dedicated Azure Tenant: Each customer has a dedicated Azure tenant managed by themselves, ensuring exclusive access and control over their data.
- Customization: Offers flexibility for customers to configure their own security, compliance, and governance policies as per their specific requirements.
- Location: Data location is determined by the customer's choice within their Azure subscription.
- Data Processing:
- Metadata and JSON Storage: Similar to the multitenant setup, only metadata and a JSON file of the content are stored, not the original file.
- Text Extraction and OCR: Performs text extraction or OCR scanning if necessary.
- AI/ML Processing: Utilizes AI/ML for risk detection and search functionalities.
- Metadata Storage: Maintains necessary metadata (e.g., document owner, created date, location) to provide details like file age and path.
- Required Set-Up: Customers need to deploy and manage the necessary infrastructure in their own Azure tenant. Detailed setup instructions can be found here and here.
Benefits:
- Enhanced Control: Customers have complete control over their data, including security and compliance configurations.
- Compliance: Facilitates adherence to specific regulatory requirements by allowing customers to manage their data within their own environment.
Downside:
- Resource Requirements: Requires internal IT resources (e.g., DevOps) to manage the setup and ongoing maintenance of the resources, potentially increasing operational complexity and costs.
For more information on the private tenant setup, please visit this page.
Summary
Both setups of DataMapper offer robust data processing capabilities, including metadata storage, text extraction, and AI/ML-based risk detection. The choice between a multitenant and a private tenant setup depends on the level of control and customization desired by the customer. The multitenant setup provides a secure, managed environment in Azure's West Europe data center, where each customer has their own resource group, while the private tenant setup offers customers full control over their data within their own Azure environment.
Questions? Feel free to reach out to our team on support@safeonline.dk