Pauling vs. OpenEye / Cadence Orion

Pauling is conversational comp chem on the cloud -- describe what you want and the platform runs it. No scripting, no workflow builders, pay-per-compute. Orion is cloud-native and technically strong (FRED, ROCS, EON), a step ahead of desktop tools -- but it's still a traditional enterprise platform with its own scripting language (Floe) and enterprise pricing.

Category Pauling OpenEye / Cadence Orion
Cloud-nativeBuilt on Google Cloud Dataflow from day oneCloud-native on AWS -- one of the first cloud comp chem platforms
InterfaceConversational AI -- natural languageFloe visual workflow builder + Python scripting
DockingUniDock (GPU-accelerated Vina) -- high throughputFRED/HYBRID -- fast, well-validated, strong enrichment in benchmarks
Shape-based screeningNot availableROCS -- industry-leading 3D shape/pharmacophore similarity
Electrostatic similarityNot availableEON -- unique electrostatic comparison capability
ScalingAuto-scales to hundreds of workers; 10M+ compound screensScales well on AWS via Orion Floe parallelization
Cost modelPay-per-compute, no license feesEnterprise licensing through Cadence; significant annual commitment
MD capabilitiesGROMACS with auto parameterization (ACPYPE), checkpoint save/resume, MM-PBSAOrion MD (OpenMM-based) -- more limited, less established than GROMACS
ADMET profilingIntegrated into conversational workflowAvailable via Floe cubes but requires workflow assembly
Learning curveLow -- no scripting, no workflow designModerate -- Floe SDK, Python Toolkit, cube development
File format handlingAutomatic conversion (PDB, SDF, MOL2, SMILES, CIF, PDBQT)OEChem handles formats; Floe workflows need explicit I/O configuration
Pocket detectionP2Rank (ML-based, automatic)OEDocking includes site detection but less automated