Virtual Staining, Your Way: Cloud or On‑Prem

Traditional staining consumes tissue with every iteration. Pictor Labs preserves tissue while expanding insight.

Our virtual staining technologies are designed to integrate into existing laboratory infrastructure, delivering results in minutes rather than days and supporting capacity without requiring a new workflow.

Choose the deployment model that fits your environment, while maintaining consistent performance across studies and workflows.

Match deployment to your workflow, scale, and research environment

From centralized research cores to distributed study teams, both deployment options are designed to support high-volume image processing and integration into existing workflows.

On‑Prem

Local

Organizations requiring full control over their data, operating in controlled environments, or integrating with existing imaging pipelines.

Choose this if you need:

  • Local processing to support time-sensitive study workflows
  • Full control over data handling and system environment
  • Integration into existing imaging, analysis, or data infrastructure
  • Consistent performance in restricted or high-security environments
Learn more

Cloud

Hosted

For teams scaling studies, collaborating across sites, or minimizing infrastructure overhead.

Choose this if you need:

  • Elastic processing capacity as datasets and study scope expand
  • No requirement for local GPU infrastructure
  • Rapid deployment across teams or locations
  • Centralized access for distributed research workflows

One Virtual Staining Engine. Built to Fit How Your Team Works.

Designed to support high-volume study and imaging workflows.

Scanner / image source Automated image detection Secure image upload On-Prem virtual staining Local · low-latency processing Seamless lab integration No data leaves environment Predictable availability Pictor cloud virtual staining Scalable · on-demand processing Scales with study demand No on-site infrastructure Accessible across sites Consistent virtual staining output

Feature comparison

Key differences in how each model supports processing, scale, and infrastructure

On-Premises
Cloud
Processing location
Customer environment
Pictor-managed cloud
Data storage
Stored within the customer environment
Cloud storage (per agreement)
Hardware required
Pictor Labs-managed on-premise deployment system
Integrates into existing systems
Internet required
Not required for processing
Required
IT requirements
Appliance deployed within the customer network environment
Access to Pictor-hosted cloud service

Implementation and infrastructure details

Infrastructure requirements, data handling, and operational responsibilities.

On‑Prem

Local

Infrastructure requirements

  • Dedicated on-premise server or GPU-enabled workstation
  • Network integration with scanner or image management system
  • IT support for installation, updates, and monitoring

Data storage

Input images, intermediate outputs, and generated virtual stains remain within a local network and storage systems. No image data leaves the customer environment.

Operational responsibilities

CustomerManages hardware, security controls, and data backups. Controls system access and permissions.

Pictor LabsProvides software installation package and updates.

Cloud

Hosted

Infrastructure requirements

  • Secure internet connection
  • Image upload integration (manual upload or API integration)
  • No local GPU hardware required

Data storage

Images are processed using flexible storage options, including Pictor-managed cloud, customer-managed cloud, or local environments. Data retention, storage location, and encryption standards are defined by the agreed service policy.

Operational responsibilities

Pictor LabsManages cloud infrastructure, security configuration, and system updates.

CustomerManages user access and image submission. Data handling and retention policies are defined contractually.