Run the same service on your own infrastructure
RichTextEditor Cloud is an ASP.NET Core API on SQL Server behind IIS. Same collaboration, documents, and conversion API as the managed service — your data, on your servers, no per-seat pricing.
Fits a Windows stack
The service is an ASP.NET Core API backed by SQL Server, hosted on IIS. If your team already runs Windows Server, it drops into your existing operations.
Same API, your data
Collaboration rooms, documents, conversion, accounts, and API keys behave exactly like the managed cloud — the content never leaves your infrastructure.
Single-artifact deploy
The API publishes and serves the exported frontend from one origin — no separate web host and no cross-origin setup to manage.
Tenant isolation built in
Every API key is an isolated tenant with plan-based quotas enforced automatically, so a self-hosted instance can still serve multiple teams safely.
1 · Build one artifact
A build step exports the Next.js frontend and publishes the API together, so a single artifact contains both the site and the service.
2 · Deploy to IIS
Copy the published output to your IIS site. The app runs in-process under the ASP.NET Core Module; a health endpoint reports readiness for your monitoring.
3 · Point it at SQL Server
Supply the database connection string and payment provider keys through environment variables — never in the repo. On first run the schema migrates automatically.
Managed or self-hosted — same API
Prototype on the managed cloud, then move to your own servers when you need data residency or want to avoid per-seat cost. Nothing in your integration changes.
Try the managed cloud API reference