A rich text editor that runs on your servers.
You host the editor files, the uploads, and the AI and collaboration backends. Nothing is metered.
Details
RichTextEditor is a set of files you copy to your own server. Your pages load it from your origin, users’ images go to an endpoint you write, and AI requests go through your server to the provider you choose. There is no editor-load counter and no subscription.
Your origin, your endpoints.
Load it from your own origin
Copy the richtexteditor folder to your site and reference it. The same files work in plain JavaScript, React, Vue, Angular, Svelte, ASP.NET, Blazor and PHP pages.
<!-- Served from your own origin. No cloud key and no editor-load counter. -->
<link rel="stylesheet" href="/richtexteditor/rte_theme_default.css" />
<script src="/richtexteditor/rte.js"></script>
<script src="/richtexteditor/plugins/all_plugins.js"></script>
<div id="editor"></div>
<script>
var editor = new RichTextEditor("#editor");
</script>Check it yourself
Do not take a vendor’s word for where requests go. Open your browser’s network panel on a page with the editor and look at every request it makes. The article Does your rich text editor phone home? walks through the check for any editor, including this one.
What self-hosting leaves to you
- You operate the backends. Upload storage, the AI proxy and the collaboration provider run on your infrastructure, so their uptime, TLS and backups are yours. A managed option exists at cloud.richtexteditor.com if you prefer not to.
- You set the security policy. Choose your Content Security Policy, allowed content and authentication. The CSP guide lists the settings the editor needs.
- No third-party attestations are published. There is no SOC 2 report or third-party accessibility report today. The trust pages state what is and is not available.
- Updates are yours to apply. A license includes one year of updates. You decide when to install a new version.