Minimum Requirements

This article outlines the essential checklist to complete prior to a Curator deployment. Adhering to these requirements ensures a smooth and efficient deployment process.

Note: This guide serves as a general framework. Specific deployment scenarios may involve additional steps not addressed here.

For cloud or hybrid systems, please also review the AWS-specific requirements and Azure-specific requirements to confirm all necessary policies and permissions are properly configured.

We recommend consulting the following documentation to ensure all prerequisites for system setup are met:

For details on IPV software/applications and third-party tools included in a Curator installation, see the Software Inventory article.

Security Note: Some articles are restricted to partners for security purposes. Ensure that content is exported and shared only with authorized individuals.

Operating Systems

Curator supports the following operating systems:

Windows

Microsoft® Windows® 11
Microsoft® Windows® 10
Microsoft® Windows® Server 2025
Microsoft® Windows® Server 2022
Microsoft® Windows® Server 2019 Standard is no longer officially supported, but is believed to function

Mac

masOS 15.[0-5] Sequoia
macOS 14.[0–5] Sonoma (Arm-based Macs only — from version 14 macOS is not supported on Intel Macs)

Supported Browsers

Google Chrome (Windows & macOS)
Microsoft Edge (Windows — Chromium-based version only)
Safari (macOS)

Service Accounts
A service account is required to run Windows services and manage tasks such as accessing hi-res files, creating directories, and moving/copying files. Ensure the account has appropriate read/write permissions to access relevant storage locations.

Storage Permissions
Grant Curator appropriate permissions to move, copy, and write files to configured storage locations. All servers running Curator services must have access to the storage. For complex storage setups, consult with IPV or a partner prior to deployment.

Certificates
Curator requires a valid SSL/TLS certificate to secure HTTPS communication. The certificate must come from a trusted authority (e.g., GoDaddy) and be provided in .pem format. The certificate should either be pre-installed on the servers or shared with IPV before deployment.
Please consider MacOS Certificate Requirements for enviroments where Mac devices will be used.

Ports
Ensure required ports are accessible between servers. Refer to the architecture drawings and firewall ports documentation for details. Custom port configurations may be provided for specific deployments.

Authentication Providers
Curator supports integration with various authentication providers for Single Sign-On (SSO), including:

Active Directory
Azure EntraID
Google
Okta

After Curator setup, authentication providers can be configured in Gateway > External Providers. For more information, see the External Providers article. Note that each provider has unique configuration requirements.

Metadata Model
A metadata model should be defined prior to deployment. This includes deciding on metadatanames for organizing and managing Curator assets. You can use the default metadata provided in a Curator deployment or create a custom metadata model tailored to your business needs. Typically, this process involves collaboration with IPV’s workflow design team using a metadata workbook or workflow narrative.

Workflows and Plugins
Establish the necessary workflows and plugins before the Curator deployment to allow the engineer to customize the system according to your business requirements. Collaborate with the workflow design team to explore available options and create a workflow narrative document.

Databases
Curator databases will be configured based on the deployment type:

On-Premise Systems: MySQL
AWS Hybrid/Cloud Systems: Amazon RDS
Azure Hybrid/Cloud Systems: Azure SQL
Provide database accounts with full access to the deployment engineer. For on-premise systems, engineers can typically create the required accounts.

Support Access
To ensure full system support, IPV may require access to your servers via VPN or other secure login methods. Ensure these access requirements are addressed prior to deployment.