CLOUD CHECKER

Brand Owner (click to sort) Address Description
CLOUDCHECKR NETAPP, INC. 3060 Olsen Dr. San Jose CA 95128 CLOUD CHECKER;Providing temporary use of online, non-downloadable computer software for cost optimization, namely, budget tracking and alerts, spend data analysis and reporting, actionable savings recommendations including automatic optimization of reserved instances or other pre-purchase cloud infrastructure resource options, full cost customization and manipulation, and tagging for inter-departmental chargebacks and invoicing; data security, namely actively monitoring enterprise-scale cloud infrastructure resources to determine if their configurations expose the organization to intentional or unintentional data breaches or hacks, and informing users of risks and possible corrective actions;
CLOUDCHECKR CloudCheckr Inc, 342 N. Goodman St. Rochester NY 14607 CLOUD CHECKER;Providing temporary use of online, non-downloadable computer software for cost optimization, namely, budget tracking and alerts, spend data analysis and reporting, actionable savings recommendations including automatic optimization of reserved instances or other pre-purchase cloud infrastructure resource options, full cost customization and manipulation, and tagging for inter-departmental chargebacks and invoicing; data security, namely actively monitoring enterprise-scale cloud infrastructure resources to determine if their configurations expose the organization to intentional or unintentional data breaches or hacks, and informing users of risks and possible corrective actions;
 

Where the owner name is not linked, that owner no longer owns the brand

    
Technical Examples
  1. Various methods and apparatuses are described in which a software programming interface connects one or more functional checker components and one or more protocol checker components to an interconnect monitor component. A computer readable medium stores code for the one or more functional checker components for Intellectual Property (IP) cores, one or more protocol checker components, the interconnect monitor component, and the software programming interface. The monitor component has code to build data structures containing protocol data types requested by a checker component and code on where to deliver data based upon a particular type of data requested by the checker component.