O2OA: replace the bundled H2 database before anything reaches production
Open-source OA (office automation) system - a Gitee GVP project, Java-based enterprise OA platform with collaborative office and workflow features. Supports the domestic Kylin OS and domestic databases (DM, Kingbase), for government and defense-industry informatization OA use.
At a glance
- What is it?
- o2oa/o2oa is an AGPL-3.0 office automation and low-code platform built on a JavaEE distributed architecture, with a process engine plus form and page customization. Its own documentation tells you the bundled in-memory database is for demos only, that commercial use needs a separate license, and that the build runs on three different toolchains.
- Who is it for?
- Adopt O2OA if your organization needs process driven office software on domestic infrastructure, including 麒麟 operating systems and 达梦 or 人大金仓 databases, and can staff the Java and JavaScript sides. Do not put the bundled H2 database into production, and settle the licensing question in writing first, because the README routes resale and commercial projects to a paid license from the vendor.
- Can I use it commercially?
- Yes, with strict conditions. AGPL-3.0 is a network copyleft licence: if people use a modified version over a network, for example as a hosted service, you must offer them its source code under the same licence.
- Is it still maintained?
- Yes. The repository last received commits 2 days ago.
- What is it written in?
- Mainly JavaScript, according to GitHub's language statistics.
Answers come from the project's GitHub data, last synced on November 15, 2026, and from our analysis. They are not legal advice.
Star history
- o2oa/o2oa4,718 ★ · +38
| Repository | 2026-09-23 | 2026-11-15 |
|---|---|---|
| o2oa/o2oa | 4.7k | 4.7k |
38 Stars in the last 53 days, measured from the daily GitHub snapshot. Compare with other projects
Editorial analysis
Ports 80, 20020 and 20030 are the whole first-run contract
The quick start is a prebuilt zip named after its build timestamp, three open ports, and one script. On Windows you download o2server.yyyyMMddHHmmss_windows.zip, unpack it anywhere, open ports 80, 20020 and 20030, then double click start_windows.bat inside the o2server folder and wait while the services come up before opening http://127.0.0.1. Linux takes the same shape with a shell script:
unzip o2server. syyyMMddHHmmss linux.zip
cd o2server. yyyMMddHHmmss_linux
cd o2server
./start.linux.shBoth instructions end at http://127.0.0.1, so nothing about hostnames, TLS or a reverse proxy is covered here. The target platforms are enumerated in the only fenced block on the page: Windows 64Bit, Linux 64Bit[CentOS, RedHat, Ubuntu等], MacOS, AIX, Raspberrypi(树莓派), ARM_Linux, MIPS_Linux, UOS, 麒麟等国产操作系统.
The bundled H2 database is a demo database
The clearest warning in the documentation is about data. O2OA ships with H2, an embedded in-memory database, and the documentation is explicit that it suits development environments and feature demonstrations rather than a real deployment. For production the recommendation is a commercial grade engine instead, naming Mysql8, Oracle12C and SQLServer 2012 as examples. Two consequences for a reader planning an installation. First, the demo you evaluate in a browser and the system you run in production are different systems as far as storage goes, so the evaluation tells you nothing about database behaviour. Second, the documentation also suggests turning on O2OA's periodic backup and restore capability, which means data safety depends on a configuration choice you make rather than a default that is on for you.
gulp, Maven and Ant all sit in the same tree
The repository carries three build systems, which tells you how the project grew. At the root there is a gulpfile.js, a build.xml for Ant, and a package.json whose scripts hand work off to gulp on one side and to Maven inside o2server on the other:
"build_server": "gulp build_server",
"build_server_script": "cd o2server && mvn clean && mvn install",
"build_server_deploy": "cd o2server && mvn clean && mvn deploy",
"build_web": "gulp build_web",
"build_api_version": "jsdoc -c o2web/jsdoc.conf.json -q version=${VAPI}",
"build_api": "gulp build_api",
"build_historyJson": "gulp build_historyJson",
"build_parallel": "npm run build_server && npm run build_web && npm run build_api"The front end is a separate top level directory, o2web, and there are also o2android and o2ios directories for mobile clients plus a welcome directory. So a full build means a Java server compiled by Maven, a web front end compiled by gulp, and API documentation generated by jsdoc from a configuration file inside o2web. Anyone budgeting a build pipeline should assume a Java toolchain and a Node toolchain, not one.
Every target platform is a separate gulp environment flag
The scripts are named per operating system, and each one passes a different environment value to the same gulp task:
"preperation:win": "gulp preperation --e windows_java11",
"preperation:linux": "gulp preperation --e linux_java11",
"preperation:aix": "gulp preperation --e aix_java11",
"preperation:arm": "gulp preperation --e arm_java11",
"preperation:macosx64": "gulp preperation --e macosx64_java11",
"preperation:macosarm": "gulp preperation --e macosarm_java11",
"preperation:mips": "gulp preperation --e mips_java11",
"preperation:rpi": "gulp preperation --e raspi_java11",
"preperation:sw": "gulp preperation --e sw_java11"Read the Raspberry Pi line twice. The npm script is called preperation:rpi while the environment value it passes is raspi, so the name you would guess from the script list is not the value gulp receives. The task name itself is misspelled as preperation in every script, which is harmless. A matching deploy family repeats the same shape with gulp deploy --e windows, linux, aix, arm, macosx64, macosarm, mips, raspi and sw, so the platform list is duplicated across two script blocks.
AGPL covers the code, commercial use is a separate conversation
The repository license is AGPL-3.0, and the documentation adds a usage distinction on top of it. Internal research, and companies building an internal office system on the platform without distributing a closed version and without using it in a commercial project, are described as carrying no infringement risk. Reselling, distributing closed source, or using the platform as part of a commercial project is directed to contact the vendor, 浙江兰德纵横网络技术股份有限公司, to buy a commercial license, with the commercial license and support service page at https://www.o2oa.net/service/gs.html. The name and the logo are registered trademarks of the same company. For a reader this is the sharpest edge in the project: the code is open, the trademark is not, and a commercial deployment is a sales conversation rather than a self service decision.
No GitHub releases, so the version lives in package.json
There are no published releases on the repository, and the default branch is develop rather than main. The root package.json reads "name": "o2oa" and "version": "4.0.3763". That leaves changelog.md at the repository root as the record of what changed, so a reader tracking versions has one file to watch and no tags to compare. The last push to the repository was on 2026-11-02, and the project is not archived, which is a weaker signal than a release history. The deployment knowledge follows the same pattern: the platform handbook, the source build tutorial and separate Windows and Linux server deployment guides all live on the o2oa.net site, not in the repository.
The platform is maintained by a commercial vendor
O2OA is described as 100 percent open source, yet it is established and maintained by a single company rather than a foundation, and the same page carries that company's commercial profile. 浙江兰德纵横网络技术股份有限公司 was founded in 1999, is a Zhejiang high technology enterprise, and the page cites ISO9001:2008 certification, national system integration grade three and CMI grade three, more than 600 employees and offices across Chinese provincial capitals. It also lists telecom carriers among past customers. Practical reading for an evaluator: the governance is a vendor's, the support channel is a commercial one, and the community resources are a forum at forum.o2oa.net plus the vendor's project page on oschina.net. Enterprise capability is real, but so is the dependency on one company's roadmap.
Editorial conclusion
Adopt O2OA if your organization needs process driven office software on domestic infrastructure, including 麒麟 operating systems and 达梦 or 人大金仓 databases, and can staff the Java and JavaScript sides. Do not put the bundled H2 database into production, and settle the licensing question in writing first, because the README routes resale and commercial projects to a paid license from the vendor.
Frequently asked questions
What is O2OA used for?
O2OA is an enterprise office automation and collaborative work platform built on a distributed JavaEE architecture, offering a process engine, form customization, page customization and business data services with cross platform mobile office. Its description also names domestic support, including 麒麟 operating systems and the 达梦 and 人大金仓 databases.
How do I start the O2OA server on Linux?
Download o2server.yyyyMMddHHmmss_linux.zip, make sure ports 80, 20020 and 20030 are open on the server, unzip the package, cd into the extracted folder and then into o2server, and run ./start.linux.sh. Once the services finish starting, open http://127.0.0.1 in a browser.
Can I run O2OA with the database it ships with?
Not for production. The bundled H2 is an embedded in-memory database that the documentation calls suitable for development and demonstration environments only, and it recommends commercial engines such as Mysql8, Oracle12C or SQLServer 2012 instead. It also suggests enabling the platform's periodic backup and restore capability.
Can I use O2OA in a commercial product?
The code is under AGPL-3.0, and the documentation says resale, closed source distribution, or use as part of a commercial project requires buying a commercial license from 浙江兰德纵横网络技术股份有限公司. The commercial license and support service page is https://www.o2oa.net/service/gs.html.
Official sources
Add this badge to your README
If you maintain this project, the badge below links readers to this analysis and shows its maintenance status from the daily GitHub snapshot. Paste the markdown into your README; add ?metric=license or ?metric=stars to the image URL for a different field.
[](https://hysenlabs.com/projects/o2oa-o2oa)Star history chart for your README
[](https://hysenlabs.com/projects/o2oa-o2oa)Was this useful?