The price for a Mercury installation can vary, depending on what you want. Mercury isn't an off-the-shelf software product like our RBackup product, so we are free to help you design a package that best suits your budget and your needs. There are many factors to consider when pricing Mercury, which can swing the cost one way or another.

We are free to license Mercury in a number of ways. Typically we license a Server capable of handling a maximum number of clients (20,000 to 1,000,000 and beyond) for a base fee starting at $30K, and charge fees for installation and maintenance, localization, customization, integration, and other chores based on how many hours it will take us to achieve the software you want. We charge separate fees for support, depending on what level of support you want, and most of the time, we charge license fees for each active Client.

We are open to partial-partnering deals. We negotiate all the fees after we are sure we know what you expect from us.

Here's a pricing example. This is for demonstration purposes only. This example is not meant to be a price quote. Your price will be different.

Suppose you want to duplicate what BackUPMAX (backupmax.com) has done with its Personal Edition. You want the exact feature set, pricing plans, business model, and all we need to do is change graphics, change the payment gateway, install it on your servers, and train your people. (Well, there's much more to it than that, but let's assume.) Suppose we do none of your website work except the minimum necessary to integrate your payment gateway and software provisioning with online ordering, done exactly like BackUPMAX.

Suppose you're going to do all your own end-user support, and RBS will provide support only for your one lead support technician as a single point of contact during our US business hours. We will not communicate with your end users. We WILL be available 24/7 for issues that threaten to bring down your servers. You will employ a fully-trained high level engineer who is responsible for your server, and who knows our software.

Let's assume, for the sake of this example, that we will not need to do any localization or translation, but we will need to rewrite the user documentation for your company.

Your support people will be trained by remote, or they can make a trip to Memphis for two days. We can come to your site at a different price.

We'll use a pricing model that calls for separate licensing for the Server and the Clients. In this case, we license a server at the maximum number of users you might need, and charge a monthly fee for each ACTIVE user, which will vary from month to month as users go on and off your service. Our client fee is a dollar amount, charged regardless of your charges to your customer. If you give it away, we still charge the same amount. This covers our possible support costs, since the more customers you have, the higher our support load and liability will be.

To understand the work involved in each of the Phases below, it might be helpful to have a look at this document: Mercury Pre-Quote Worksheet

We might begin pricing this deal like the following:

Annual Maintenance Fee is 20% of this price, $13,800. Client licensing is $0.30/month per active user. There would be no ongoing Server licensing fee.

We might be able to bring this solution online within three weeks.

RBS will provide the Oracle 11g back-end, and all application-layer software with the exception of your remote control solution, if you will offer that to your end users.