How do you define a Resource?
A ‘Resource’ to Hyperglance is an instance/VM, Load balancer, Gateway, S3 Bucket, Database instance, or Peering Connection with all of its associated data, that is defined as a single entity or instance by its primary source platform. We don’t count Security Groups, Route Tables, interfaces, links, attributes or chart data as separate ‘Resources’. See here for a full list of resources.
How is Hyperglance invoiced?
Because Hyperglance is provisioned inside the marketplace you are invoiced directly by AWS or Microsoft, from your already established payment method. The cost is just another line item in your AWS or Azure bill. No need to ask procurement to add another provider.
How is Hyperglance billed?
Hyperglance is provisioned as an AWS or Azure instance so it is billed only when the instance is running. The cost per hour depends on the number of resources you need. For example, if you run a 500 resource Hyperglance instance in AWS for 20 hours in a month the cost would be 1.23 * 20 = $24.50 (plus EC2 charges).
Is Hyperglance SaaS?
No, Hyperglance runs in a VM/Instance inside AWS or Azure, deployed via the AWS or Azure Marketplace. There is no shared data and you control access.
How can I be sure my data is secure?
Hyperglance is not a SaaS platform and runs inside AWS or Azure. Hyperglance doesn’t call back to base and is self contained.
Can I add data to Hyperglance by myself?
Yes, Hyperglance comes with an extensive RESTful API that you can use to augment or create links, interfaces, alarms and attributes. You can also add hyperlinks to any entity.
Do you provide perpetual licencing?
Yes, please contact us for perpetual licencing prices – [email protected]