-
Notifications
You must be signed in to change notification settings - Fork 0
DOC Billing
The total cost of running a filter depends on the complexity of the filter which we measure in Data Processing Units (DPUs), how long the filter is run for, the number of transactions it produces. We charge £0.003 per 1,000 transactions or £0.000003 per transaction.
For example, each ICE transaction that we deliver costs £0.000003. If we create a filter that costs 1 DPU and run it for 6 hours, and the subscriber receives 100,000 transactions, the cost will be:
(DPU * HOURS * DPUCost) + (TransactionCost * TransactionDeliveredCount) = £9.80
Daily Costs
Spot Midrates (1 * 24 * 0.20) + (0.00001 * 500000) = £9.80
Swap Points (1 * 24 * 0.20) + (0.00001 * 500,000) = £9.80
Forward Rates (1.4 * 24 * 0.20) + (0.00001 * 500,000) = £11.72
Forward Points (1.6 * 24 * 0.20) + (0.00001 * 500,000) = £12.68
Weekly Costs
Spot Midrates (1 * 120 * 0.20) + (0.00001 * 2,500,000) = £49.00
Swap Points (1 * 120 * 0.20) + (0.00001 * 2,500,000) = £49.00
Forward Rates (1.4 * 120 * 0.20) + (0.00001 * 2,500,000) = £58.60
Forward Points (1.6 * 120 * 0.20) + (0.00001 * 2,500,000) = £63.40
Interest Rate Differentials (1.8 * 120 * 0.20) + (0.00001 * 2,500,000) = £68.20
Monthly Costs
Spot Midrates (1 * 480 * 0.20) + (0.00001 * 10,000,000) = £198.00
Swap Points (1 * 480 * 0.20) + (0.00001 * 10,000,000) = £198.00
Forward Rates (1.4 * 480 * 0.20) + (0.00001 * 10,000,000) = £234.40
Forward Points (1.6 * 480 * 0.20) + (0.00001 * 1000000) = £253.60
Interest Rate Differentials (1.8 * 480 * 0.20) + (0.00001 * 1000000) = £272.60
You cannot predict the license fee in advance because it is impossible to predict how many messages users will post. We can provide an estimate of the number of transactions a stream will generate by running a tests for a few minutes and generating those results.
The cost of running historic queries depends on data processing usage plus the licensing costs. Data processing usage is calculated based on the duration of the Historic query and the sample size of the output data; it is deducted from the monthly DPU usage. Licensing costs depend on the volume of data retrieved.
For example, we create a Historic Query of a simple stream costing 0.1 DPU, for the timeframe of one month, with 10 percent as the sample output data size. The data processing usage for this Historic Query is calculated to be 288 EPU and it is deducted from your monthly DPU allowance. As per the usage statistics, the volume of data retrieved is a total of 10,000,000 transactions and enrichments. Since Currency Pair transaction charges $0.20 for every 1,000,000 transactions that we retrieve for the query, the licensing costs of the Historics Query will be $242.44 approximately.
The DOC charges licensing fees on behalf of our partner sites. The license fee that you pay is exactly proportional to the number of objects your stream produces. Or, in the case of Historics queries, the number of objects retrieved by your query.
If want to create very highly targeted streams, you should typically expect to receive a low volume of data and so your license fees will be very low. For example, a filter for all forward rate transactions of GBP/CHF with a 01Y tenor, isn't going to generate very much output, even on days when the market does something exceptional.
On the other hand, a filter that looks for any mention of, say, EUR/USD will probably generate substantially more output and cost more in license fees.
A DPU is a Data Processing Unit, a reflection of the computational complexity for the processing that is being performed by the DOC. A higher number represents a more complex stream. We measure DPUs on a per hour basis because running a stream for five hours costs five times as much as running it for one hour.
This will depend on the size of the subscription you have purchased. The default cost is 20 GB pence per DPU.
Yes, you will be charged even if you stop a Historics Query midway. You will be charged for the licensing costs of the volume of data retrieved until you stopped the query. The data processing usage until you stopped the query will also be deducted from your monthly DPU usage.
You purchase credits on the ETHEL platform. Credits are priced in GB Pounds.
A credit costs £1. One credit is equivalent to 5 DPUs so the effective price of one DPU is 20 cents.
We believe customers should only pay for what they consume. The DOC is a cloud platform, allowing you to consume only what you need and retain the flexibility to scale, either up or down, whenever necessary. The DPU amount paid by subscribers is determined by the complexity of the rules created of a stream.
Applications need to handle dynamic loads to survive. We provide dynamic vertical scaling to handle unexpected data spikes as well as horizontal build out to support application growth over time.
Please contact our Support team.
Via the REST API: For Streams, hit the /dpu endpoint to find details of DPUs for a stream. For Streams, hit the /usage endpoint to find how many objects the DOC has delivered to you.
For Historics queries, hit the historics/prepare endpoint to get details of DPUs for your Historics query.
Via the DOC UI, visit our Billing page.
The minimum DPU charge is currently 1 DPU per hour, no matter how simple your stream is.
If you run just one stream that costs just 0.1 DPU, the total charge is 1 DPU per hour, which equates to 20 pence. In other words, the minimum DPU cost to use the platform is 20 pence per hour.
However, if you run ten streams, and they all cost 0.1 DPU, the DOC will still charge only 1 DPU per hour for all ten.
You can pay a fixed price for the processing but not for the licensing. The DOC offers a range of subscriptions which include prepaid DPUs. The license cost of the content is variable and depends on the number of objects your stream returns. Clients who choose to prepay for DPUs benefit from a discount.
Each request has a fixed cost of 10 DPUs plus 2 DPUs per day. For example:
1 day = 12 DPU
30 day = 70 DPU
There are no licensing fees charged for a Historics Preview since you will not receive any of the transactions that match your filter, you will only receive aggregate statistics for your selected filter.
Billing for Managed Sources has two components:
There is a charge for the complexity of your query, based on the number and type of operators.
Each source is also billed as follows:
| Managed Source | Description |
|---|---|
| Facebook Pages | 50 DPUs per search term per month. |
| 50 DPUs per Facebook page per month. | |
| Google+ | 50 DPUs per Google+ page or keyword search per month. |
If you create a filter and run it twice, sending to two different destinations simultaneously, you will be billed once for the DPUs you receive and once for the data license fee.
This is true for both our Streaming API and our Push delivery mechanism. The only condition is that you must be consuming the same stream hash for the cost deduplication to apply.
Transactions are charged to your account at the time the transactions are made available for you to consume. For example, this might be the moment an interaction is written into your Push delivery buffer.