OnlyOffice vs Collabora: which one fit 2GB VPS?
See vendor RAM floors, wetin free CODE and ONLYOFFICE Docs limit, docx fidelity, and which office server fit 2 to 4 GB VPS beside Nextcloud.
OnlyOffice vs Collabora: answer for small VPS
OnlyOffice vs Collabora na choice between two document engines wey fit connect to file server wey you don already dey run, and for most readers na Nextcloud be that. For 2 GB VPS, choose Collabora and use the copy wey Nextcloud bundle, because e no add second container or another web address. For 4 GB or more, ONLYOFFICE Docs worth the extra memory if your team dey work mostly with .docx and .xlsx, because na formats wey the editor fit handle directly.
Another name dey show for every search about this question. ONLYOFFICE DocSpace na separate product wey get its own interface, and e no be the component wey Nextcloud dey connect to. To install DocSpace because tutorial talk say "OnlyOffice" na the commonest reason people dey think say edit button for Nextcloud need big server.
Di products wey people dey often mix up
- ONLYOFFICE Docs, wey dem still dey call Document Server, na the editing engine by itself. E no get file manager. The Nextcloud connector dey talk to this one. Community Edition free, under the GNU AGPL v3.
- ONLYOFFICE DocSpace na workspace: rooms, member management, sharing, and im own web interface, with Docs bundled inside am. E overlap with Nextcloud instead of extending am. Current installation guides dey call this workspace ONLYOFFICE Apps. The published minimum, wey dem check for October 2026, na 6 CPU cores and 12 GB of RAM for the install script, while dem recommend 8 cores and 16 GB. The development/testing Docker build dey ask for the same 6 cores and 12 GB. E pack the workspace services inside one container, but e still run Document Server, MySQL and OpenSearch for containers of their own, and ONLYOFFICE mark that build as for testing, no be production.
- Collabora Online na LibreOffice wey dey run for the server. The document layout and drawing dey happen for the server, then dem send am go browser as images. The free build na CODE, short for Collabora Online Development Edition.
Nextcloud dey ship two apps for the Collabora side. richdocuments, wey dem list for the app store as Nextcloud Office, na the connector to a Collabora server. richdocumentscode carry CODE inside the Nextcloud installation, so you no need run any container and you no need write any proxy rule. Nextcloud own manual describe this built in server as suitable for personal use or small teams, and e recommend dedicated Collabora install for better performance.
Update the built in CODE app to 26.4.303 or later: earlier versions get critical command injection vulnerability for its proxy.
If you never settle the file server matter, Seafile compared with Nextcloud na the decision wey come first, because the office server na attachment to whichever one you run. If Nextcloud don already dey run, a Nextcloud instance for VPS with TLS and backups na the box wey this guide assume.
How much RAM each one need?
Di data wey dey behind dis chart
[
{
"label": "Collabora CODE",
"min_ram_gb": 1
},
{
"label": "ONLYOFFICE Docs (Docker)",
"min_ram_gb": 4
},
{
"label": "ONLYOFFICE DocSpace",
"min_ram_gb": 12
}
]Na these figures wey each vendor publish. We check the ONLYOFFICE figures again against ONLYOFFICE own pages on 27 October 2026, while the Collabora figure come from Collabora FAQ as last confirmed on 25 October 2026. The Collabora and Docs figures cover the office server sizing requirements, while the DocSpace figure cover the whole stack, including database and search engine; these no be measurements of idle memory use. Collabora FAQ budget 1 GB for the system, plus 50 MB for each user. ONLYOFFICE ask for 4 GB for Docs under Docker, plus 4 GB of swap and 40 GB free disk, while the page for DEB and RPM package installs list 2 GB. DocSpace ask for 12 GB and six CPU cores when you install am with the vendor script, and e recommend 16 GB.
Now add Nextcloud to the same machine. PHP-FPM (FastCGI process manager) workers, the database, and the background job runner all need memory. The kernel page cache wey make file listings feel fast also need memory. For a 2 GB VPS, Nextcloud and the office server must share that small memory budget. The built-in CODE app still need memory for itself: its README list 1 GB plus 100 MB per user. E ships the Collabora binaries inside the Nextcloud app, and Nextcloud proxy the editor traffic to am locally. This reduce speed and save you one container to run and maintain.
Wey the two engines dey use memory in different ways
Collabora dey render for server. Every document wey dey open get im own process inside container, and you fit monitor am with docker exec collabora ps -ef while person dey edit. Memory dey increase as the number of documents wey dey open at the same time increase. So idle server no dey cost much memory, but ten editors wey dey work at once no be the same thing.
ONLYOFFICE Docs dey push layout work go browser. Im editor na JavaScript, while server dey store file, coordinate co-editing, and run format conversions. Since version 9.4, wey dem release for May 2026, the Community Edition container dey run nginx in front of one consolidated server process. PostgreSQL and RabbitMQ no dey inside am. ONLYOFFICE script installation guide, wey dem check on 2 November 2026, talk say: "RAM: at least 2 GB, but depends on the host OS. More is better". Im Docker installation guide still list 4 GB, but na installation requirement be that. E no mean say na so much memory the system go use when nobody connect. Version 10.0, wey dem release on 10 October 2026, add AI tools wey you no fit install for Docs Community Edition. Different installation apply to ONLYOFFICE Desktop Editors. Docs Enterprise and Developer editions get the AI tools inside dem.
The vendor requirements no show how the memory use for the two engines compare. Measure memory use when system dey idle and when people dey edit with your own documents before you size shared server.
Wetin the free builds limit
CODE no get any document or connection limit for im default mode. Collabora staff confirm this for Collabora own forum for September 2026. The 10 document and 20 connection caps wey older guides dey mention apply only when person switch on the optional Home Mode, and e no dey on by default. Wetin separate CODE from the paid Collabora Online build na stability and support. Collabora describe CODE as rolling release wey dey under constant development, with no SLA or long term support. E suit home use and small teams, but e no suit production. Collabora Online na the stable edition with Long Term Support, SLA, and security updates. For sizing, Collabora FAQ, as dem last confirm am on 25 October 2026, suggest 10 users per CPU thread and 50 MB of RAM per user, plus extra 1 GB for the system.
ONLYOFFICE Docs Community Edition no get connection cap since version 9.4, wey remove the old limit of 20 simultaneous connections. Its Docker system requirements page separate from the Docker install guide, and e give sizing tiers instead: 100 to 200 users for dual core 2.8 GHz machine with 4 GB of RAM, and 200 to 400 users for quad core. E also note say the real number depend on the size and type of documents wey people open. Treat these numbers as vendor ceilings wey dem measure under vendor conditions.
Wich one dey handle .docx and .xlsx better?
ONLYOFFICE dey work directly with Office Open XML (OOXML), so dem open, edit, and write .docx file back for the same format wey e arrive with. Collabora na LibreOffice underneath, and e native format na OpenDocument (ODF), so every OOXML file go pass through import step when dem open am and export step when dem save am. Both good enough for everyday documents. The difference dey show for files wey dem build for Microsoft Word or Excel with plenty formatting. E dey show as small layout shifts, no be lost data.
No use comparison pages, including this one, take decide this matter. Take your two worst files: the one wey get tracked changes and the one wey get pivot table. Open each one for both editors, save, download, then compare am with the original. Twenty minutes of this go answer the fidelity question for your documents. Na this specific version of the question matter.
If na one person dey edit file once in a while, one single-file office suite fit help you avoid running document server at all.
License, and where the paid line dey
ONLYOFFICE Docs Community Edition dey under GNU AGPL v3 license, and e get extra terms wey require attribution, copyright notices, and clear labelling for modified versions. The license no give right to use ONLYOFFICE trademarks. Collabora Online source code dey under Mozilla Public License 2.0. Both projects na open source, and both companies dey sell supported build.
The things wey free build no get dey different for each case. Collabora free build no get cap for e default mode. Wetin e no get na stability and support: na rolling development release wey no get SLA. ONLYOFFICE free build no get cap, and ONLYOFFICE dey sell Enterprise and Developer editions wey add support and more features. For house use or small team, both free builds dey enough. For company, read the license terms before you plan rollout, because AGPL obligations and per user pricing na separate problems wey get separate answers.
Installing either one na one container
ONLYOFFICE Docs, bound to loopback because reverse proxy go terminate TLS (transport layer security) for front:
sudo docker run -i -t -d -p 127.0.0.1:8081:80 --restart=always \
-e JWT_SECRET=replace_this_with_a_long_random_string \
onlyoffice/documentserverSet JWT_SECRET by yourself. JWT (JSON web token) signing don dey on by default since ONLYOFFICE Docs 7.2, and if you no provide secret, the container go generate one. Generated secret fit change when you recreate the container, and the connector go stop working without any useful message for screen.
First start fit take some minutes. Check am:
curl http://127.0.0.1:8081/healthcheckThat endpoint go return true once the editors inside the container ready to use. Anything else, including false, means make you read docker logs for the container before you change Nextcloud settings.
Collabora CODE:
docker run -t -d --name collabora --restart always \
-p 127.0.0.1:9980:9980 \
-e "aliasgroup1=https://cloud.example.com:443" \
-e "extra_params=--o:ssl.enable=false --o:ssl.termination=true" \
collabora/codealiasgroup1 na the list of Nextcloud addresses wey this container go accept work from, and the port suppose dey inside am. Setting ssl.enable=false makes coolwsd, the Collabora server process, speak plain HTTP inside the container, because reverse proxy for front dey handle TLS. Set ssl.termination=true to tell Collabora say TLS dey end for the proxy. Check am:
curl http://127.0.0.1:9980/hosting/capabilities
curl http://127.0.0.1:9980/hosting/discoveryThe first one go return JSON, while the second one go return XML. Refused connection means the container still dey start or e don exit, so read docker logs collabora.
Connect editor to Nextcloud
For Collabora, install Nextcloud Office app, open Administration settings, then Office, choose the option to use your own server, and enter the address wey users' browsers fit reach, like https://office.example.com. Nextcloud dey hold the files, while Collabora dey fetch dem through WOPI (web application open platform interface), so four separate network paths must work:
- Browser must reach Nextcloud.
- Browser must reach Collabora server.
- Nextcloud must reach Collabora server.
- Collabora must reach Nextcloud.
Test the last two by hand. From Nextcloud server, curl https://office.example.com/hosting/capabilities suppose print JSON. From inside Collabora container, curl https://cloud.example.com/status.php suppose print Nextcloud status JSON. The path wey fail na the one wey you need fix.
For ONLYOFFICE, install the connector app, then enter the ONLYOFFICE Docs address and secret key for its settings. The secret must match JWT_SECRET exactly. If the container generate its own secret, read am from inside the container at /etc/onlyoffice/documentserver/local.json, under services.CoAuthoring.secret.inbox.string. Then verify am from your Nextcloud directory, as the web server user:
php occ onlyoffice:documentserver --checkE go either confirm the connection or print the error wey connector dey encounter. This dey faster than reading browser console. ONLYOFFICE connector also get advanced fields for cases where browser address and server-to-server address no be the same, for example when Nextcloud dey reach editor through private network. Fill those fields instead of sending internal traffic go public address and back.
Wetin dey make editing break behind reverse proxy
Almost every report of “e no go open” na one of these.
Protocol mismatch. Nextcloud for https with the office server address written as http go fail, because browser no go allow insecure frame load inside secure page. Use https for both.
Proxy rules for Collabora dey miss. Proxy must forward /browser, /hosting/discovery, /hosting/capabilities, /cool, /cool/adminws, and websocket connections for /cool/(.*)/ws go port 9980. If websocket rule miss, document frame go load then remain empty, because editor dey open websocket immediately after loading and e no dey get reply.
Wrong aliasgroup1. Container dey reject requests from address wey nobody tell am about, and docker logs collabora dey record No acceptable WOPI hosts found. The value must match the Nextcloud URL wey your users dey type, including port.
Nextcloud dey refuse to call local address. Nextcloud blocks outgoing requests to local and private addresses by default, and log line na Host violates local access rules. Set 'allow_local_remote_servers' => true for config.php when editor really dey reachable only through local address.
WOPI allow list wey too narrow. Nextcloud Office settings get allow list for WOPI requests. This list limit the addresses wey fit fetch files. E good make you use this setting, but e fit also make editing break after container come back with new IP address. If documents stop opening immediately after rebuild, check this field first.
ONLYOFFICE no fit download the file. Connector reports Error while downloading the document file to be converted.. Document server don receive instruction to fetch file from Nextcloud but e no fit: address wey dem give am no dey reachable from inside container, or Nextcloud dey present certificate wey e no accept, or the secret no match. Run curl against that exact URL from inside the container with docker exec, and the reason usually go be one line.
Wetin actually fit run for 2 GB and 4 GB
For 2 GB, run Nextcloud with the built-in CODE app and stop there. E slower pass standalone server, the first time you open a big spreadsheet fit take several seconds, and e no need proxy configuration at all. For one household, na the correct answer be that one.
For 4 GB, run Nextcloud plus one standalone CODE container, and configure swap so one sudden load no go bring the server down. Na for here editing dey start to feel normal.
If you wan run ONLYOFFICE Docs beside Nextcloud, plan for 6 to 8 GB, or give Docs its own small server. Its 4 GB Docker installation requirement no mean say na that idle memory e go use, and e no prove say every shared 4 GB server go swap. The script and package guides list at least 2 GB, depending on the host OS; Nextcloud still need extra memory on top of that.
DocSpace for small VPS na the mistake wey you need avoid. The published minimum for its script installation na 12 GB of RAM and six CPU cores, while 16 GB and eight cores dey recommended. Check wetin the guide go install before you follow am, and check when dem last confirm the requirements wey e quote against the vendor page. The install script na only one option too. Docs and CODE na single containers wey you start, stop, and delete by yourself. This one easier to understand than script wey dey install one whole stack.
For the wider question of wetin fit belong for small server at all, wetin dey worth self-hosting for 2026 cover the shortlist.
FAQ
Collabora or OnlyOffice better for Nextcloud?
No be say one better for every situation, and memory na usually the thing wey decide. Collabora starts from the 1 GB system baseline wey e own FAQ give when dem last confirm am on 25 October 2026. The free CODE build no get document or connection limit for the default mode, but Collabora target am for home use and small teams, no be production. ONLYOFFICE Docs list 4 GB for Docker installation and at least 2 GB for its script guide, before you add Nextcloud own requirements. E never get connection cap since version 9.4, and e works with .docx and .xlsx directly, so e dey keep Microsoft Office formatting closer to the original. Choose Collabora for small VPS. Choose ONLYOFFICE when the team dey work with Office formats all day and you fit give the editor its own memory.
How much RAM I need to edit documents for Nextcloud?
For 2 GB server, start with Nextcloud built-in CODE server app. E list 1 GB plus 100 MB for each user for the office server alone. E dey ship inside the Nextcloud installation, and Nextcloud starts am for you. So you no need deploy second container, even though the Collabora server still runs as its own process. 4 GB dey comfortable for Nextcloud plus standalone Collabora CODE container. ONLYOFFICE Docs list 4 GB Docker installation requirement and at least 2 GB for its script guide, depending on the host OS. So plan 6 to 8 GB when e shares machine with Nextcloud, or put am for separate server.
Why document frame dey open, then remain blank?
The editor loads over HTTPS, then e opens websocket. So blank frame almost always mean say the websocket never connect. For Collabora behind nginx, confirm say the proxy forwards /cool/(.*)/ws with connection upgrade headers, and say /browser, /hosting/discovery and /hosting/capabilities dey forwarded too. Then read docker logs for the container: No acceptable WOPI hosts found mean say the aliasgroup1 value no match the Nextcloud address wey browser use, including the port.
I need ONLYOFFICE DocSpace to edit files for Nextcloud?
No. DocSpace na standalone workspace with its own interface and user accounts, and the Nextcloud connector no dey talk to am. The part wey Nextcloud connects to na ONLYOFFICE Docs, the document server. DocSpace publishes minimum of 12 GB RAM and six CPU cores for script install, and e recommends 16 GB. Na why guides wey install am dey make people believe say browser editing needs big server.