Please see below summarized information about the WebSpellChecker usage limitations and pricing policy. The following pricing model gives you more flexibility and control over how you use our products. You can choose the appropriate Cloud plan and use as much or as little as you need. If you find yourself needing more than 50 million words or prefer a more secure version, consider the WebSpellChecker Server version.
Cloud Pricing Plans (WProofreader / SCAYT / WSC Dialog / Web API) | Server Version (Full set of products) | |||
|---|---|---|---|---|
| Pricing Plans | Basic | Plus MOST POPULAR | Custom | Bespoke |
| Price | $150 per year | $250 per year | The annual cost is defined based on the amount of text processed, and additional features required. | Tailored pricing based on the agreed metrics and licensing terms. Contact us at [email protected]. |
| Renewal | $150 per year | $250 per year | ||
| Processed Words, year | Up to 20 million words | Up to 50 million words | Over 50 million words | |
If the Cloud customer end ups exceeding the limit, the service will stop working. However, our team monitors the usage, and notify customers beforehand with the proposal to purchase another set of words. In this case, new price depends on the potential customer usage (per year) and the price of the appropriate usage plan. | ||||
| Banner | No | No | No | No |
| Term (Validity) | 1 year | 1 year | 1 year | 1 year |
| Number of Domains | 1 domains and unlimited sub-domains | Unlimited | Unlimited | Unlimited |
License Type / Activation Key | One Encrypted Customer ID that works for 2 main domains and unlimited number of sub-domains. | One Encrypted Customer ID that works for any domain. | One Encrypted Customer ID that works for any domain. | License Ticket (per server) |
| Management and Control | Personal Account
| Personal Account
| Personal Account
|
|
| Data Security |
|
|
|
|
| Support | Limited Support | Limited Support | Custom support services | Custom support services |
| Support term / Upgrade rights | 1 year | 1 year | ||
| Support amount | 1 support ticket / month | 2 support tickets / month | ||
| Support request type | Critical issues which affect the normal work of services. | Critical issues which affect the normal work of services. | ||
| Documentation with online samples | Yes | Yes | Yes | Yes* Also includes offline Demo Samples and Documentation. |
| Assistance type | Emails, LiveChat | Emails, LiveChat | Emails, LiveChat, Desktop Sharing, Phone | Emails, LiveChat, Desktop Sharing, Phone |
| Response time | 2 business days | 1 business day | 1 business day | 1 business day |
| Business hours | 10:00 am — 7:00 pm GMT+3 (Mon-Fri) | 10:00 am — 7:00 pm GMT+3 (Mon-Fri) | 10:00 am — 7:00 pm GMT+3 (Mon-Fri) | 10:00 am — 7:00 pm GMT+3 (Mon-Fri) |
| Customization services | No | No | No | Available in a scope of the Custom development services. |
| Languages | 16 Default languages | 16 Default languages | Extended languages support | Extended languages support |
| User Dictionary | Local Storage + Server | Local Storage + Server | Local Storage + Server | Local Storage + Server |
| Custom Dictionary | Yes | Yes | Yes | Yes |
| Grammar | Yes Available for 14 languages | Yes Available for 14 languages | Yes Available for 14 languages | Yes Available for 14 languages |
Usage Calculation Explanation
Let us explain how the Cloud usage is calculated. The way how the requests are sent directly depends on the way the users enter their texts. Let us share with you several possible scenarios. For example,
a. A user inserts some portion of text with 100 words, the whole text will be divided into small portions up to 10 words and sent to the server for spell checking. Thus, as a result, you will have about 10 requests in this case.
b. A user starts typing in the textarea, typed several words and stopped for a few seconds. These two words will be sent to the server to check. So, in this case, you will have a request with only two words.
However, there is one thing that you should keep in mind. There is a mechanism of “caching/remembering” previously checked words during this active session (until the page reload). Thus, it remembers already checked words and won't send them again for spell checking.
For example, if you have text something like “Hello, how are you ” and the user adds at the end of the sentence a word “today”, so a new sentence is “Hello, how are you today”, then the only one word “today” will be sent to the server for checking.
After that, the user adds “. Hello” and pauses for a few seconds, so a new sentence is “Hello, how are you today. Hello”. In this case, it doesn't send any requests as all these words have been already checked, and we know that “Hello” is a correct word.
