Architecture

Self-hosted or cloud editor: what leaves your network

Cloud or self-hosted is three questions, not one: where the code loads from, whose servers the services use, and whether a licence check calls the vendor.

6 min read

“Cloud or self-hosted?” sounds like one question about a rich text editor. It is three. An editor has code that the browser loads, services that the code calls, and often a licence check. Each of the three can run on the vendor’s servers or on yours, and vendors mix them. This article separates the three, so you can ask a vendor precise questions and answer your own security review.

The three parts

  1. The editor code.The script and stylesheet are loaded either from the vendor’s content delivery network or from your own site.
  2. The services.Image storage, AI writing tools, real-time collaboration, document export and spell checking each need a server. That server is the vendor’s, or one you run.
  3. The licence check. Some editors contact the vendor to validate a key or to count usage. Others check nothing at run time.

A product can be self-hosted in the first sense and cloud in the second. “Self-hosted” on a pricing page usually describes the code only, so ask about the other two.

What leaves your network in each case

None of this is wrong in itself. It becomes a problem when it is unknown, or when your privacy notice, contracts or sector rules say the content stays with you.

What a cloud editor gives you

And what it costs you, beyond the price:

What a self-hosted editor gives you

And what it costs you:

Questions to ask a vendor

  1. Can I serve every file from my own origin, with no request to your domains at run time?
  2. For each of image upload, AI, collaboration, export and spell check: whose server does it use, and can I replace it with mine?
  3. Does the editor contact you to check a licence or count usage? What happens to my users if that request fails?
  4. Which features exist only in the cloud plan?
  5. If I stop paying, does the installed editor keep working?

Verify the answers

Answers on a sales call are not evidence. Open the browser’s network panel on a page with the editor, use each feature once, and read the list of requests. Every request to a domain that is not yours is something to explain. The article Does your rich text editor phone home? walks through the check, and the CSP article shows how a strict policy turns an unexpected request into a visible error.

How to choose

Choose by the service, not by the label. A team with no operations staff may self-host the editor code and still buy hosted collaboration. A team under strict data rules may accept more operations work to keep every request inside its own network. Write down, for each of the three parts, where it runs and who is responsible. That table is what your security reviewer will ask for.

RichTextEditor is sold as a self-hosted product: the files are served from your origin, and uploads, AI and collaboration use servers you run. The self-hosted editor page lists what that leaves to you.


RichTextEditor is a perpetual-licence JavaScript editor — one purchase, self-hosted, no metered editor loads. Download the evaluation or see how it compares.