SaaS & On-premises. Container Friendly.

The SaaS architecture enables you to use our AWS powered infrastructure.
All collected data is redacted for PII and privately encrypted using your own 256-bit AES keys. Learn more.

On-prem data mode enables you to leverage our AWS infrastructure without sending out sensitive data. Perfect for PII, PCI and HIPAA compliant applications. Learn more.

In On-premises mode OverOps is deployed fully behind your firewall,
requiring no connection to the cloud. Ideal for highly regulated industries. Learn more.

Production Performance

Runs in the World's Most Demanding Environments

CPU overhead
OverOps employs self-throttling at the JVM level, combined with continuous guidance provided by the analysis engine to limit the number of error snapshots taken. This ensures CPU overhead by the agent is always kept under a 3% threshold.
No GC overhead
OverOps runs at the native JVM level and does not allocate Java objects at run-time. Collected information is placed directly in shared memory outside of the managed heap. This ensures that no overhead is added to your application's garbage collection (GC) time.
No Throughput Overhead
Since OverOps only reacts to errors, it does not affect normal code execution. Even if a transaction is experiencing a high degree of failures (expected or unexpected), the OverOps agent will adjust itself to ensure no impact to throughput.
Network overhead (< 50mb per hour)
Error information captured by the JVM agent is placed into shared memory and sent for storage by the collector process. The size of event snapshots is capped at 50Mb per hour (only aggregate event statistics will continue to be collected beyond that).
No reliance on logs
The agent collects statistics on exceptions and errors logged directly from the JVM in real-time, regardless of if and how events are eventually logged to disk. As such, OverOps does not access or upload log files from your machine.
No dependency on OverOps
The JVM micro-agent is not dependent on the availability of OverOps servers or collectors. If at any time these become unavailable, the agent enters a dormant state with no effect on the execution of code within the JVM.

Enterprise Security

AES Encryption.
PII Redaction.
Access Control.

256-bit AES Encryption
All source code and variable state collected is privately encrypted using a 256-bit AES Encryption key before leaving the production node. Only you have access to secret encryption keys which are not stored by OverOps.
PII Redaction
OverOps redacts PII variable data before it leaves the production environment. Variable state is redacted based on configurable variable value patterns and code symbology: variable, field and class names. PCI and HIPAA compliant.
Access Control
Robust support for two-factor authentication with OAuth (e.g Google Apps and GitHub), LDAP and SAML. Administrators can limit access to OverOps to a specific VPN or network. Communication between all OverOps components is made over outbound HTTPS port 443.

Easy to Deploy

A Simple JVM Agent
HotSpot, OpenJDK and Zulu,
IBM J9. Versions 6-8.
No changes to code or build
Simply install the micro-agent and add
an -agentlib argument to your JVM.
All JVM Languages
Support all JVM languages and frameworks -
from WebLogic to Scala and Groovy.
Containers and Automation