How Veloopti SaaS works

Home > An Overview > Basics > How Veloopti SaaS works

---

Overview

One of the major architecture factors in developing Veloopti was to save you from having to engage expensive engineers to do things that we think we should do, or to do the things we think we should do for you; for instance performing a version upgrades.

Veloopti is built as a multitenant application which means there is a single Veloopti environment that serves multiple organisations. We upgrade the Veloopti environment progressively as new features and functionality are developed. Sometimes we will upgrade with multiple enhancements in a week and other times there may be none. What is good for you is that you don’t need to do anything to benefit from these upgrades in your organisation.

The Veloopti environment is dynamically managed with application servers being added and removed as the need arises.

We have built Veloopti so that any sysadmin or application administrator who understands the OS or application that they are responsible for will be easily able to build monitoring for it. They will need to know the service name or executable or disk or Windows event log or syslog entry or local/remote port or IP address or SNMP trap ID or SNMP OID or WMI path that needs to be monitored. And ff they don’t know then you will need to get someone who does.