Pricing

SaaS and on-premise installations are charged differently:

  • In SaaS we charge for the used resources (disk, processing time) plus a small monthly subscription fee

  • While on-prem (on your servers) instances pay for the number of users

SaaS (Hub or Private)

We calculate the used resources on daily basis. Then at the end of the billing period we sum up the resources for each day and submit the sum to the billing service (Paddle).

Calculating Disk Usage

Every time you upload a new resource, generate new chromatograms or peaks this adds more signal to store.

Your Daily Usage is the maximum what you stored for that day, so:

  1. Say you already have 10GB of data

  2. Today you upload another 5GB, now you have 15GB

  3. Then you delete 3GB. You maximum for today still stays at 15GB - and that’s what you’re going to be charged for.

  4. The next day you’ll start with 12GB, and if you don’t upload anything - that’s what you’ll be charged for that day.

Some SaaS instances (like Peaksel Hub) have Free Plan included. Those resources will be subtracted when you’re charged. So the calculations are:

  1. Take the maximum used disk space for today. Say, it’s 9.9GB.

  2. Subtract the Free Plan resources. Say, it was 0.5GB, so we end up with 9.4GB.

  3. Round (the usual mathematical rules) to the nearest GB → you get to pay for 9GB

Counting requests

What we count is the requests that access the detector data. We count only the modification requests and only those that access the detector signal (each detector is counted separately).

As with the disk space, we:

  1. Sum up requests on daily basis

  2. Subtract the Free Plan for that day

  3. Round to the closest 100

Examples of what’s counted as a modification request:

  • Uploading injections. Every injection counts, even if only a single file was uploaded. If an Injection has N detectors, then it’s counted as N.

  • Chromatogram extraction

  • Chromatogram integration

  • Peak detection. If there are 2 DetectorRuns in an injection, and we need to get both, then it’s counted as 2 requests. Same goes for any other action.

  • Changing peak boundaries

  • Manual peak selection

  • Changing baseline

  • Changing a chemical structure/mass spec settings that causes reintegration.

What’s NOT counted:

  • Playing with integration parameters without pressing Apply button

  • Looking through spectra of a detector run or of a peak

  • Deleting chromatograms/peaks