/o3o/status reports the Community limit of 50; on this image the Community edition does not reach 50 connections. Using a plan's full connection count, including every Enterprise order, needs the MORA image built from source; orders above 50 connections also need that image built with a large enough cap.
The MORA Office Online image built from source with MORA branding: coming soon. Performance figures: not yet measured.Four ways to use it
One Docker bundle, one entry point. Pick what fits your system, or use all four.
Browser-based editing
Open and edit documents, spreadsheets and presentations (.docx, .xlsx, .pptx, .odt, .ods, .odp and other common formats) in the browser, with several people editing the same file. Files stay on your servers.
Nextcloud integration
The nextcloud profile in the compose file brings up Nextcloud 30, MariaDB and Redis for testing; scripts/setup-nextcloud.sh connects them automatically. With an existing Nextcloud: install the richdocuments app, run occ richdocuments:activate-config -w <editing server address> -c <Nextcloud address>, then click a file to edit it.
Embed in your software
Load /o3o/api.js and call new O3O.Editor(...). No Nextcloud needed: the gate fetches the file from the URL you pass, acts as an internal WOPI host and posts saved versions to your callbackUrl with an HMAC signature. 7 events, 5 methods, JWT HS256 signed configuration.
DocBuilder
A REST API under /v1/ with 11 endpoints: format conversion, building documents from o3oscript JSON scripts, filling {{field}} templates with repeating table rows, and extracting text, metadata and thumbnails. Synchronous or job-based.
Who it is for
A good fit for
- Companies and public bodies using Nextcloud who want to edit files where they are stored, without documents leaving their servers.
- Software vendors building document, records, contract, HR or ERP systems who want an embedded editor and saved versions via callbacks.
- Systems that generate documents such as quotations, contracts, payslips and reports by calling DocBuilder from the server, with no user interface.
- Technical teams that run things on-premises, keep control of their data and test with Docker on their own machines.
Not yet a fit if you need
- A cloud service operated by MORA: v1 is self-hosted only.
- Your own branding in the editor today: white-labelling is coming soon.
- Committed performance figures: not yet measured; we will publish them once measured.
- Online license activation: v1 verifies tokens offline; online activation is coming soon.
Architecture
All requests go through the proxy on port 8080. Before an editing session opens, the proxy asks the gate: within the plan limit it is let in, otherwise a notice page is shown; open sessions are never cut and saving is never blocked.
What v1 includes
in v1 Available in v1
- Compose file for the proxy, editing server, gate and DocBuilder; optional
nextcloudprofile; secret generation and smoke-test scripts. - Editing-session counting and plan limits; Vietnamese limit page; open sessions are never cut and saving is never blocked; fail-open when counting fails.
- Ed25519-signed license tokens verified offline; connection usage log every 5 minutes (CSV) for reconciliation.
O3O.Editor: 7 events, 5 methods, embed sessions, internal WOPI host, HMAC-signed callbacks, JWT HS256, SSRF protection;/o3o/demotest page in DEV mode.- DocBuilder: 11 endpoints, API keys and JWT, per-plan limits,
o3oscriptv1 for text, spreadsheets and presentations; template filling with repeating rows; text, metadata and thumbnail extraction.
coming soon Not yet available, planned
- MORA Office Online image built from source, using a plan's full connection count; public repository of MORA's changes to the MPL code; white-labelling (logo, product name, colours) for Enterprise.
- Online purchase, activation, heartbeat and revocation through office.mora.vn.
- Soft overage for Enterprise; 30-day P95 statistics; usage charts; Prometheus metrics.
- Several editing servers behind one gate; oCIS connector.
- Embed layer: dark theme, watermark, per-button visibility, save as another file, version history.
- DocBuilder: batch template filling, document comparison, charts in o3oscript, npm, PyPI, NuGet and Go SDKs, durable queue, MORA Office engine.
Plans and pricing
From 15 November 2026, MORA Office Online is included in per-user MORA plans and is no longer sold per connection. To run it on your own servers, choose MORA Self-host; editor embedding and API use are quoted to your needs. Full pricing
Included in MORA plans
MORA Personal, per user per month
- Edit Docs, Sheets, Slides and PDF in the browser and on desktop
- MORA Cloud 50 GB, Meet, Chat, basic MORA AI; up to 5 devices
- MORA Business from 10 users: Basic VND 139,000, adds MORA Mail on your domain
- Business Advanced: VND 228,000 (500 GB) · VND 378,000 (2 TB) · VND 738,000 (5 TB), includes MORA Platform
MORA Self-host
per user per month, billed every 12 months
- Minimum 50 users
- Docs, Sheets, Slides, PDF and document storage on servers you run yourself
- Mail, Meet, Chat and AI depend on the deployment and are not included by default
- Deployment, customisation and dedicated support: quoted separately
API integration
by scale and integration
- Embed the editor in your own software with a few lines of JavaScript
- DocBuilder API: convert, build and fill documents server-side
- Connect to your existing file storage
Getting started
- Request the Docker bundle (the
online/folder) by e-mail at hotro@mora.vn. Public code repository: coming soon. - In the
online/folder, create.envfor a test machine withbash scripts/gen-secrets.sh --dev(PowerShell:scripts\gen-secrets.ps1 -Dev). The script copies.env.exampleto.envand replaces everyCHANGE_MEvalue with a random string (editing-server admin password, JWT secret, callback secret, DocBuilder API keys). Production machines run it without--dev. - Build and run:
docker compose --env-file .env -f docker/compose.dev.yml up -d # add Nextcloud to test the integration docker compose --env-file .env -f docker/compose.dev.yml --profile nextcloud up -d
- Check
http://localhost:8080/o3o/status(status, plan, connections),http://localhost:8080/v1/status(DocBuilder) and the embed test pagehttp://localhost:8080/o3o/demowhenO3O_DEV_MODE=1(set by--dev). - With an Enterprise license token: set
O3O_LICENSE_TOKENor theO3O_LICENSE_FILEfile; the gate re-reads it every 60 seconds without a restart.
Full instructions, environment variables and troubleshooting are in online/README.md and in the API documentation.
Licensing and source code
The editing server is open source under the MPL 2.0. In v1, DEV mode uses the upstream image unmodified (pinned by digest, configured only through environment variables); MORA does not change the code in that image. When the MORA image built from source is released, MORA's changes to the MPL code will be published to recipients of that image as the license requires; the image and the source repository are coming soon. The gate and api.js are MORA code and talk to the editing server over HTTP and WebSocket.
MORA DocBuilder's own code is owned by MORA. The DocBuilder image ships an open-source document engine under its own licenses (mostly MPL 2.0, with parts under LGPL v3+ and other licenses); distributing the image means including the bundled license notices and telling recipients how to obtain the source. This core is a different version from the MORA Office desktop suite; the running core version is reported by GET /v1/status. Moving DocBuilder to the MORA Office core is coming soon.
Request source codeAPI documentation
Planning a deployment?
Contact us for plan advice, a 30-day trial, MORA Self-host deployment or an API integration quotation. Hotline 1800 4985.