â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
- The editor code.The script and stylesheet are loaded either from the vendorâs content delivery network or from your own site.
- 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.
- 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
- Code from a vendor network: each page view sends the visitorâs address, browser details and the page address to the vendor. The document does not travel, but the fact that the page was opened does.
- A vendor service: the content itself travels. An uploaded image, the text sent for an AI rewrite, or every keystroke of a shared document is processed on the vendorâs servers.
- A licence or usage check: at least the key and the site address travel, and the count of editor loads if the plan is metered.
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
- No servers to run. Collaboration and export backends are real systems with storage, scaling and monitoring. The vendor operates them.
- Updates arrive without work. Security fixes reach your users when the vendor ships them.
- A named party responsible for availability, where the vendor publishes a service commitment.
And what it costs you, beyond the price:
- The vendor becomes a processor of your usersâ content, to be listed and reviewed like any other.
- A vendor outage, a blocked domain or an expired key can stop your editor from loading.
- Your Content Security Policy must allow the vendorâs domains.
- Updates also arrive when you did not plan for them, unless you pin a version.
- Pricing often follows usage. See editor pricing models.
What a self-hosted editor gives you
- Content stays in systems you operate. Uploads go to your storage, and AI requests go through your server to a provider you chose.
- It works on a closed network. An intranet or an offline deployment has no vendor domain to reach.
- You choose when to update, and can test a version before your users see it.
And what it costs you:
- You apply the updates. A security fix protects nobody until you install it.
- You run the services. Uptime, backups, TLS and scaling for uploads, AI and collaboration are your work.
- Nobody else answers for availability.
Questions to ask a vendor
- Can I serve every file from my own origin, with no request to your domains at run time?
- For each of image upload, AI, collaboration, export and spell check: whose server does it use, and can I replace it with mine?
- Does the editor contact you to check a licence or count usage? What happens to my users if that request fails?
- Which features exist only in the cloud plan?
- 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.