Up and running in your own infrastructure
BoldDocServer runs as a Windows container on Windows Server, next to your SharePoint farm. Pull a versioned image, configure it for your environment and connect SharePoint through WOPI.
Three steps to your first document
The documentation walks you through each one.
- 1
Run the container
Deploy BoldDocServer from a versioned image on a Windows Server host that can run Windows containers, in the same network as your SharePoint farm.
You’ll need:
- Windows Server host
- Container runtime
- Network access to SharePoint
- 2
Configure your environment
Supply the SharePoint endpoint, the HTTPS certificate for the BoldDocServer address and any secrets at deployment time. No code changes, and nothing is built into the image.
You’ll need:
- SharePoint endpoint
- HTTPS certificate
- Secrets
- 3
Connect SharePoint
Register BoldDocServer with a WOPI binding from the SharePoint Management Shell, then open a Word, Excel and PDF file from a library to check it.
You’ll need:
- SharePoint farm administrator
- A maintenance window if you’re replacing Office Online Server
What you’ll configure
Everything environment-specific is supplied at deployment time. Exact setting names are in the documentation.
| Setting | What it’s for | Example |
|---|---|---|
| BoldDocServer address | The HTTPS address that SharePoint and browsers use | https://bolddocserver.yourcompany.local |
| SharePoint endpoint | Where BoldDocServer sends WOPI requests | https://sharepoint.yourcompany.local |
| HTTPS certificate | Secures the BoldDocServer address | A certificate trusted by SharePoint and your users’ browsers |
| Secrets | Keys and credentials the container needs | Supplied at deployment, never built into the image |
| Reverse proxy (optional) | Publishes BoldDocServer through infrastructure you already run | Your existing proxy or load balancer |
The same image from test to production
Each release is a versioned image. Test it against a test farm, then promote the same image to production with that environment’s configuration.
To roll back, redeploy the previous version with the same settings.
- Repeatable deployments
- No code changes between environments
- You choose when to upgrade
What you need, and how to start
What you need
- SharePoint Server 2016, 2019 or Subscription Edition
- Windows Server to run the BoldDocServer container, in the same network as your SharePoint farm
- An HTTPS certificate for the BoldDocServer endpoint
- Network access to that endpoint from SharePoint and from users’ browsers
- Optional: a reverse proxy in front of BoldDocServer
Start your 30-day free trial
Run the container in your own environment, connect SharePoint and try BoldDocServer with your own documents for 30 days. The documentation walks you through each step.
Frequently asked questions
Which SharePoint versions are supported?
SharePoint Server 2016, SharePoint Server 2019 and SharePoint Server Subscription Edition.
Do we need to change SharePoint?
You add a WOPI binding that points SharePoint at BoldDocServer. Libraries, permissions and content stay as they are.
How do upgrades work?
Each release is a versioned image. Deploy the new version with your existing configuration, test it, and roll back by redeploying the previous version if needed.
Can BoldDocServer run behind a reverse proxy?
Yes. BoldDocServer can be deployed behind a reverse proxy where supported by your deployment architecture.
Explore more features
How it works
SharePoint keeps the files; BoldDocServer connects through WOPI and provides the editor.
Learn more →Word, Excel and PDF
What each format can do, in the Document Editor, Spreadsheet Editor and PDF Viewer.
Learn more →Browser editing and collaboration
Edit, comment and track changes in the browser, saved straight back to SharePoint.
Learn more →Security and data control
Follow a document through BoldDocServer and see who controls each part.
Learn more →Try BoldDocServer free for 30 days
Keep SharePoint, give your users browser editing back, and be ready before Office Online Server support ends on December 31, 2026.