Pricing details
With BrowserHawk To-Go (BHTG) you pay a small monthly fee of just $99.95 plus a usage fee.
Monthly pricing for the BHTG libraries and service options is outlined below. All pricing is in U.S. dollars.
Detailed examples and a pricing calculator are also available.
TIP: Use the Pricing Calculator to estimate your monthly cost.
Browser Detection Library (CORE)
Detect and log 120+ browser and system settings or dynamically render site content based on browser/system configurations.
| | First 500,000 requests | $3.50 | per 10,000 requests |
| | Next 2,000,000 requests | $2.50 | per 10,000 requests |
| | Next 7,500,000 requests | $2.00 | per 10,000 requests |
| | Requests beyond 10,000,000 | $1.85 | per 10,000 requests |
Quick example: A site with 50,000 visitors costs $99.95 plus $17.50, per month.
($99.95 base monthly rate, plus usage fee calculated as: 50,000 / 10,000 = 5 units billed x $3.50 each). [More examples]
Page Load Time Library (PLT)
Monitor the actual page load times as experienced by each visitor to your site.
| | First 500,000 requests | $0.88 | per 10,000 requests |
| | Next 2,000,000 requests | $0.63 | per 10,000 requests |
| | Next 7,500,000 requests | $0.50 | per 10,000 requests |
| | Requests beyond 10,000,000 | $0.46 | per 10,000 requests |
Quick example: A site with 50,000 visitors costs $99.95 plus $4.40, per month.
($99.95 base montly rate, plus usage fee calculated as: 50,000 / 10,000 = 5 units billed x $0.88 each). [More examples]
Error Tracking Library (ERR)
Automatically log all JavaScript errors that users encounter on your site.
| | First 500,000 requests | $0.53 | per 10,000 requests |
| | Next 2,000,000 requests | $0.38 | per 10,000 requests |
| | Next 7,500,000 requests | $0.30 | per 10,000 requests |
| | Requests beyond 10,000,000 | $0.28 | per 10,000 requests |
Quick example: A site with 50,000 visitors costs $99.95 plus $2.65, per month.
($99.95 base monthly rate, plus usage fee calculated as: 50,000 / 10,000 = 5 units billed x $0.53 each). [More examples]
Browser Troubleshooting Library (RET)
Instantly add a self-help, automated browser troubleshooting and analysis page to your site.
| | First 500,000 requests | $0.35 | per 10,000 requests |
| | Next 2,000,000 requests | $0.25 | per 10,000 requests |
| | Next 7,500,000 requests | $0.20 | per 10,000 requests |
| | Requests beyond 10,000,000 | $0.19 | per 10,000 requests |
|
| | First 250 tests executed | $0.49 | per test |
| | Next 1,000 tests executed | $0.25 | per test |
| | Next 10,000 tests executed | $0.12 | per test |
| | Tests beyond 11,250 | $0.07 | per test |
|
| | First 250 emailed results | $0.25 | per test result emailed |
| | Next 1,000 emailed results | $0.15 | per test result emailed |
| | Next 10,000 emailed results | $0.08 | per test result emailed |
| | Emails beyond 11,250 | $0.05 | per test result emailed |
Quick example: A site with 50,000 visitors that runs 50 tests costs $99.95 plus $26.25, per month.
See example 5 for details.
Database storage for logging and reporting (LOG)
Log data to BHTG network for real-time reporting and analysis.
| | Storage in BHTG network | $0.79 | per 10,000 rows |
| | Storage on your servers | $0.00 | (no reporting) |
Quick example: Storage costs for a site with 50,000 rows stored costs $3.95 per month.
[More examples]
What are "requests"?
"Requests" are the primary measure of usage of the service.
When one of your web pages loads a BHTG library for a user during their visit, it results in one request.
Once a library is loaded, it is cached in the user's browser for 24 hours. Subseqent page loads typically will
not result in additional requests for libraries that are cached.
If you will use a library on most or all pages, estimate the
number of monthly requests for that library by looking at your site's average monthly visits. If you will
use a library only on select pages, estimate the requests by looking at
the number of visits per month just for those pages.
For example, if your web site averages 100,000 visits per month and you use the CORE and PLT libraries throughout your site, you can estimate
your requests for CORE and PLT to be about 100,000 each per month. Or as another example, if you only use these libraries from a small section
of your site that receives 5,000 visits a month, then you can estimate your requests at 5,000 despite the overall traffic of 100,000 visits.
Note that any requests served over SSL (secure pages) count as 5 requests each. See example 7 below for details.
Pricing examples
The following walk-thrus demonstrate how pricing is calculated under some common scenarios.
Example 1: Development and local testing
Assume an account is created for the purposes of trying out BHTG and learning how it works.
A developer adds the CORE library to a test version of their web site and hits a page which
uses the library. This generates one "request". The developer continues to test various pages on the
site which use the library that day, but since the library is now cached, all testing that day results in just
this single request. Testing on subsequent days only generates one request per day, due to caching.
Now assume the developer wants to log the browser and system configuration data obtained from using the CORE library. For each visit
the developer makes to the test site, a row is then inserted into the BHTG database.
Later the developer
adds the PLT library to try out the page load time tracking. This results in one request per day for the PLT library,
and one row logged to the BHTG database for each page viewed.
Assume that during the course of the month the developer has tested several web pages every day, resulting in
750 page views. The charges for this month are:
CORE library: First 10,000 requests is $3.50. Total used 30 (one per day)
PLT library: First 10,000 requests is $0.88. Total used 750 (one per page view)
Storage: 10,000 rows stored is $0.79. Total rows stored is 780 (30 for CORE, 750 for PLT)
Total charges for the month: $3.50 + $0.88 + $0.79 = $5.17 for usage, plus base monthly fee of $99.95.
Now assume that ten additional developers beging working with the test site. The pricing is identical to the above,
because this only adds 10 more requests per day per library, and the storage still uses less than 10,000 rows (780 rows x 11 developers = 8,580 rows).
Further, assume that the developers become busy with other tasks and the following month they do not work on the project, and no requests are made to the service.
The total charges for the next month would only be $0.79 to cover the BHTG storage fee (for the 8,580 rows residing in the database). Or the developer could choose to remove the rows prior to the new month and the total storage charges would be $0.00.
Example 2: Use of CORE library in production with logging
Assume the CORE library is used to gather browser and system configuration data and log it to the BHTG network for analysis and reporting.
The web site that this is used on receives 100,000 visits during the month. This results in 100,000 requests for the CORE library, which will then
log one row of browser and system configuration data for each visit. The charges for this month are:
CORE library: 100,000 requests / 10,000 = 10 units billed @ $3.50 = $35.00
Storage: 100,000 rows / 10,000 = 10 billable rows @ $0.79 = $7.90
Total charges for first month: $35.00 + $7.90 = $42.90 usage fee, plus base monthly fee of $99.95.
In the second month, the charges are the same assuming the same usage levels, except the storage fee is $1.80 because now there are an additional 100,000 rows of data in storage (totaling 200,000 rows).
By default only the latest three months of data is retained in the system. You can set the storage retention time from 1 - 36 months.
Example 3: Use of CORE and PLT libraries in production with logging
Building on example #2, assume that in addition to logging browser and system information from the CORE library, that the PLT library is added.
So in addition to the 100,000 requests already being generated by the CORE library, the PLT library will now generate 100,000 requests as well.
The PLT library will also log one
row to storage for each page viewed on the site. Assume this site averages 3 page views per visit. Therefore 300,000 (100,000 visits x 3 page views per visit)
rows of PLT data will be logged per month, plus the 100,000 rows of browser and system configuration information from CORE (1 row logged for each visit).
The charges for this month are:
CORE library: 100,000 requests / 10,000 = 10 units billed @ $3.50 = $35.00
PLT library: 100,000 requests / 10,000 = 10 units billed @ $0.88 = $8.80
Storage: 400,000 rows / 10,000 = 40 billable rows @ $0.79 = $31.60
Total charges for first month: $35.00 + $8.80 + $31.60 = $75.40 usage fee, plus $99.95 base monthly fee.
In the second month, the charges are the same assuming the same usage levels, except the storage fee is $63.20 because now there are an additional 400,000 rows of data added to the existing 400,000 rows in storage from the first month (so the storage fee is based on 800,000 rows).
By default only the latest three months of data is retained in the system. You can set the storage retention time from 1 - 36 months.
Example 4: Use of CORE, PLT, and ERR libraries in production with logging
Building on example #3, assume that in addition to logging data from the CORE and PLT libraries, that the ERR library is added.
So in addition to the 100,000 requests generated by using CORE and the 100,000 requests generated by using PLT, the ERR library will now also generate 100,000 requests.
The ERR library will only log one row to storage for each JavaScript error that occurs on a page. Let's assume during the course of a month this is 250 errors.
In addition to the 400,000 rows of data from CORE and PLT being logged, another 250 rows are logged for errors.
The charges for this month are:
CORE library: 100,000 requests / 10,000 = 10 units billed @ $3.50 = $35.00
PLT library: 100,000 requests / 10,000 = 10 units billed @ $0.88 = $8.80
ERR library: 100,000 requests / 10,000 = 10 units billed @ $0.53 = $5.30
Storage: 400,250 rows / 10,000 = 41 billable rows @ $0.79 = $32.39
Total charges for first month: $35.00 + $8.80 + $5.30 + $32.39 = $81.49 usage fee, plus $99.95 base monthly fee.
Example 5: Use of RET library in production
Assume you want to add a link to your site that visitors can click to troubleshoot their browser or to check
their settings against your site's requirements. You can do this simply by adding the RET library.
Let's assume your site receives 100,000 monthy visits, and that the troubleshooting link is clicked on by
100 visitors a month. Further assume that 20 of these visitors use the option to email their
test results to your help desk. The charges for this month are:
RET library: 100,000 requests / 10,000 = 10 units billed @ $0.35 = $3.50
RET library: 100 tests run @ $0.49 per test = $49
RET library: 20 test results emailed to help desk @ $0.25 per test = $5
Total charges for the month: $3.50 + $49 + $5 = $57.50, plus $99.95 base monthly fee.
Example 6: Use of RET and CORE libraries in production
Assume you want to silently check visitors for incompatible browser settings
when they take a specific action on your site, such as when they load a page or click on a login button.
Also assume that when users do not meet your requirements you want to display the browser troubleshooting information
automatically, while remaining silent for users that pass your browser checks.
This is done by using the RET library in conjunction with the CORE library.
Assume the web site receives 100,000 monthly visits, 100 users fail to meet your requirements and are
presented with the browser troubleshooting page automatically, and 20 of them use the option to email their
test results to your help desk. The charges for this month are:
CORE library: 100,000 requests / 10,000 = 10 units billed @ $3.50 = $35
RET library: 100,000 requests / 10,000 = 10 units billed @ $0.35 = $3.50
RET library: 100 tests run @ $0.49 per test = $49
RET library: 20 test results emailed to help desk @ $0.25 per test = $5
Total charges for the month: $35 + $3.50 + $49 + $5 = $92.50, plus $99.95 base monthly fee.
Example 7: Use with requests served over SSL
Any requests made to the service over SSL (secure pages using the https protocol) count as 5 requests each.
Assume you want to use the CORE library on your web site which receives 30,000 visits per month, of which 5,000 requests are served under SSL.
That would result in a total usage of 50,000 requests (25,000 non-SSL requests + 5,000 SSL requests x 5). The charges for this month are:
CORE: First 500,000 requests / 50,000 = 10 units billed @ $3.50 = $35.00
Total charges for the month: $35.00, plus $99.95 base monthly fee.
Example 8: Volume discounts
This example demonstrates how volume discounts are applied. Let's assume you are using the CORE and PLT library
and your site receives 1,000,000 monthly visits. This generates 1,000,000 requests for CORE and PLT. The
charges for the month are:
CORE library: First 500,000 requests / 10,000 = 50 units billed @ $3.50 = $175
CORE library: Next 500,000 requests / 10,000 = 50 units billed @ $2.50 = $125
PLT library: First 500,000 requests / 10,000 = 50 units billed @ $0.88 = $44
PLT library: Next 500,000 requests / 10,000 = 50 units billed @ $0.63 = $31.50
Total charges for the month: $175 + $125 + $44 + $31.50 = $375.50, plus $99.95 base monthly fee.
|
|