Apache POI VS documents4j

Apache POI’s business model is inherently collaborative. The development process is open, with contributions published on its GitHub repository. Developers worldwide contribute code, documentation, and insights to ensure that Apache POI remains responsive to the ever-changing needs of technology. The openness fosters a level of trust and engagement that traditional proprietary software often lacks. One of the key enabling factors behind Apache POI's sustained success is its funding strategy. The project benefits from both large-scale corporate sponsorship and grassroots community contributions. Many enterprises depend on Apache POI for their mission-critical operations, and their financial backing is a testament to the tool’s reliability and value. Additionally, the open source community has embraced newer funding models, such as those involving token-based incentives seen on platforms discussing tokenizing open source licenses. The practical impact of these funding models is substantial. Transparent financial records and regular community engagement sessions reinforce the project’s accountability and vision. This, in turn, builds up confidence among sponsors and users, ensuring that Apache POI remains a driving force in the open source ecosystem.

Even ASF does not use Maven to build some of its projects anymore: Beam, Groovy, Lucene, Geode, POI, and Solr are not built with Maven. Those are not the most popular ASF projects, I know, but still, it is something.

Take a look at https://documents4j.com. I'm not sure if it checks all your boxes. I have never set it up my self, but know it to be reliable in a production environment.