Skip to content

BoldDocServer objections

Type
reference
Status
draft
Owner
COE Team
Last reviewed
2026-11-07
Products
BoldDocServer

Draft. Not yet reviewed. Check facts before you use it with customers.

The buyer objections BoldDocServer pages should answer before sales has to. The website buyer-fit audit checks each one is answered where listed.

Summary

Fix these three on the site first:

  1. “Is this really a replacement for Office Online Server?” Show a clear OOS-to-BoldDocServer feature table, including what is not covered (PowerPoint is coming soon; Exchange and Skype for Business are out of scope).
  2. “Will it pass our security review?” Add a downloadable security overview and state which compliance attestations apply to BoldDocServer.
  3. “Who counts as a user?” Lift the end-user definition from the pricing FAQ to the top of the pricing page.

Details

1. “Does it fully replace Office Online Server?”

  • Answer: It replaces OOS for viewing and editing Word, Excel and PDF files from SharePoint Server libraries. PowerPoint is listed as coming soon, and Exchange and Skype for Business integrations are out of scope.
  • Proof: Document types; homepage FAQ.
  • Raised by: IT / security.
  • Site placement: comparison.

2. “Do our documents leave our network?”

  • Answer: No. BoldDocServer runs on your own servers, reads a file through WOPI while it’s open and saves back to the same file in SharePoint. It doesn’t store documents.
  • Proof: Security page.
  • Raised by: IT / security.
  • Site placement: security.

3. “Which compliance certifications cover it?”

  • Answer: Because it is self-hosted, your own controls and audits cover the deployment, and the security page explains the data flow for your assessors. Ask sales for current company-level attestations and the security documentation pack.
  • Proof: TODO: verify — whether Syncfusion’s SOC 2 Type 2 scope includes BoldDocServer; add a security overview PDF.
  • Raised by: IT / security.
  • Site placement: security.

4. “How does access control work?”

  • Answer: Users sign in to SharePoint as usual. SharePoint checks permissions and issues a token scoped to one user and one file, and BoldDocServer works only within that token.
  • Proof: Security page.
  • Raised by: IT / security.
  • Site placement: security.

5. “We run Windows servers. Why Docker and WSL 2?”

  • Answer: BoldDocServer ships as a versioned Linux container that runs on a Windows host with WSL 2, beside your farm, with IIS providing HTTPS. You choose when to upgrade, and the deployment guide covers each step, including the Redis dependency.
  • Proof: Deployment page; docs.
  • Raised by: Developer / architect.
  • Site placement: product page.

6. “Which SharePoint versions are supported?”

  • Answer: SharePoint Server 2016, 2019 and Subscription Edition, connected through a standard WOPI binding.
  • Proof: Homepage; pricing page inclusions.
  • Raised by: Developer / architect.
  • Site placement: FAQ.

7. “How much effort is the switch from OOS?”

  • Answer: A SharePoint admin points the WOPI binding at BoldDocServer instead of OOS; libraries, files and permissions stay as they are. Plan a test farm first, then a production cutover window.
  • Proof: How it works; TODO: add proof (step-by-step migration guide from OOS).
  • Raised by: Engineering manager.
  • Site placement: product page.

8. “Will it scale to thousands of users?”

  • Answer: It runs as containers you size and scale in your own infrastructure, and real-time collaboration can be enabled. Sales can review sizing for large rollouts.
  • Proof: TODO: add proof (sizing guidance and tested concurrency figures).
  • Raised by: CTO / VP Engineering.
  • Site placement: FAQ.

9. “Will documents look the same as in Office?”

  • Answer: Word editing supports comments and track changes; Excel supports formulas, charts and conditional formatting. Test your most complex files during the 30-day trial.
  • Proof: Browser editing; TODO: add proof (fidelity notes for complex documents).
  • Raised by: Business owner: operations.
  • Site placement: product page.

10. “What support do we get if editing breaks on a Monday morning?”

  • Answer: Support is covered by the published support SLA, with tickets through the support portal. Sales can confirm response targets for your plan.
  • Proof: Support SLA linked from the pricing page; TODO: verify — response targets that apply to BoldDocServer.
  • Raised by: Engineering manager.
  • Site placement: pricing.

11. “Who counts as an end-user, and what about occasional users?”

  • Answer: Pricing is per authorized end-user, and the pricing FAQ defines who counts. Ask sales if you have many occasional or read-only users.
  • Proof: Pricing FAQ; pricing and licensing.
  • Raised by: Procurement.
  • Site placement: pricing.

12. “What will this cost across our whole organization?”

  • Answer: Volume bands lower the rate as your user count grows, and the largest rollouts get a sales quote. Use the online estimator for your exact count.
  • Proof: Pricing page and calculator.
  • Raised by: Procurement.
  • Site placement: pricing.

13. “How do renewal and user-count changes work?”

  • Answer: The subscription is billed yearly and renews annually, which keeps updates current. Sales handles renewal quotes and changes to user counts.
  • Proof: Pricing FAQ.
  • Raised by: Procurement.
  • Site placement: pricing.

14. “This is a new product. Will it be around?”

  • Answer: BoldDocServer is built by Syncfusion, which has made document-processing and UI components for 25+ years, on the same document-editing technology.
  • Proof: Homepage.
  • Raised by: CTO / VP Engineering.
  • Site placement: FAQ.

15. “We’ll move to SharePoint Online eventually. Why invest now?”

  • Answer: It keeps editing working and supported on-premises until you move, with an annual subscription rather than a long commitment. Sites that must stay on-premises can keep using it.
  • Proof: Pricing FAQ on renewal.
  • Raised by: CTO / VP Engineering.
  • Site placement: FAQ.

Sources

Used by