Blueprint by Tiny
Return to Tiny.cloud
Return to Tiny.cloudTry TinyMCE for Free
Search by

Important changes to Tiny Cloud pricing metric effective June 3, 2019

Michael Fromin

June 1st, 2019

Written by

Michael Fromin
Michael Fromin

Category

News & Updates

Overview

On June 3, 2019, our pricing for Tiny Cloud subscriptions changes from ‘active users’ to ‘editor loads’. Any new Tiny Cloud premium subscriptions started on or after June 3 will use this new metric, as well as renewals which occur after June 2, 2019.

Please note this change refers only to paid Cloud subscriptions. If you self-host, this does not apply to you.

Why did we make this change?

The technology we used to track the number of unique users is sometimes known as ‘fingerprinting’ and while there are legitimate uses for it (such as ours), fingerprinting has begun to be blocked by browsers such as Chrome and Firefox. We support these efforts by Chrome and Firefox as a safer web with more privacy protection is better for all of us.

So, after considering different options, we landed on ‘editor loads’ as our new metric. We felt it represents a good measure of the value that our customers are getting from TinyMCE.

What is an ‘editor load’?

Every time your application executes tinymce.init({}) an editor load has occurred. For example, if you have 3 textarea elements on a page and you use tinymce.init({}) to turn each of them into a TinyMCE instance, you have executed 3 editor loads.

Will this change the cost of a current subscription?

The cost of a current Tiny Cloud subscription should not change due to this switch in metrics. We looked at our cloud usage data and assigned a number of editor loads that correlate with editor activity we were seeing on a per-user basis.

For Tiny Cloud subscriptions prior to June 3, the number of monthly editor loads will be converted to 30x the number of users that had been originally purchased. For example, if you had previously subscribed to the 10-user plan, you will now have 300 editor loads per month.

Your number of editor loads will be reflected on the subscription invoice you will receive at the time of your next renewal.

How can I determine how many editor loads my application will need?

This will depend on how your application works and how your users interact with your application. We know that user behavior can be hard to predict, so even if you ever unexpectedly exceed your editor load allotment, Tiny Cloud will scale up to meet your needs, and any needed change to your plan will be resolved at a later date and you will not be charged retroactively.

How does an application implementation impact editor loads?

How you implement TinyMCE will have an impact on the number of editor loads. Some examples include:

In many applications, the editor appears but the user does not need to modify the content in the editor. Applications that are designed to wait until the user needs to edit content before initializing TinyMCE will generate a lower number of editor loads than those that don’t.

Applications sometimes use elements like tabs or accordions to show and hide portions of the UI. This is generally implemented in one of two ways:

  1. Remove elements from the DOM when they are hidden and re-implement them in the DOM when they are shown.
  2. Hide and show elements visually. In this approach, the DOM is not structurally modified

If an application uses approach #1 each time the DOM element containing TinyMCE is re-implemented (and TinyMCE is initialized) that will be an editor load. If the application uses approach #2 the act of showing and hiding portions of the page won’t cause TinyMCE to be initialized each time it is unhidden.

How would a single page application (‘SPA’) impact editor loads?

Unlike traditional web applications, SPAs load the main HTML page once and rely on loading and unloading components dynamically as a user interacts with the web application. How an SPA framework loads and unloads components can impact the frequency with which TinyMCE is initialized. Most frameworks provide an ability to cache components so they are not reloaded from scratch each time they are needed. There are pros and cons of such caching but doing so would often reduce the number of editor loads.

What about my application’s users and their behaviors?

The one area you likely can’t control is how users interact with your web application. The more often someone accesses your application, refreshes the browser and saves and reloads a page in your application, the more the editor will be loaded. No doubt you want your users to engage with your application more, not less, and we have kept our pricing affordable to encourage this.

If you still have questions about this change, please contact us and we will do our best to answer any questions as quickly as possible.

Tiny Cloud
Michael Fromin
byMichael Fromin

Michael is the Director of Client Services at Ephox + TinyMCE.

Related Articles

  • Depiction of semantic versioning containing text - "Major. Minor. Patch!"
    News & Updates

    Improving our engineering best practices with semantic versioning

    by Millie Macdonald in News & Updates

Build beautiful content for the web with Tiny.

The rich text editing platform that helped launch Atlassian, Medium, Evernote and more.

Begin my FREE 30 day trial
Tiny Editor