Open source business applications

Moqui Ecosystem

A modern architecture and a full REST API for organizations that want to own their data and their code — framework, reusable business artifacts, and production applications.

Who it is for

One ecosystem, three ways in

Use the applications, hire a service provider to customize them, or build on the framework and artifacts yourself.

End-user organizations

Custom software from existing-system augmentation to complete end-to-end systems. Take back your systems: own your data, own your code.

Service providers

Consultants and system integrators get tools and reusable artifacts to efficiently build whatever a client needs — and a directory to be found.

Contributors & vendors

A reliable, flexible foundation so you can focus on differentiating features. Moderated repositories, public-domain license, and extensive docs.

Why Moqui

Less code, more of the business

  • Low code: efficient tools and existing artifacts mean less to build, maintain, and support. One large project replaced over a million lines of code with less than 100k.
  • REST APIs to build and to consume, full-text search and analytics, managed messaging, and runtime authorization with automatic query filtering.
  • Multi-instance provisioning for SaaS (Docker and MySQL included; other hosts via service interfaces).
  • Deploy as a standalone executable or a WAR, on VMs, containers, on-prem, or private cloud.

Latest releases

Always the current GitHub release — versions are not copied here so they do not go stale.

License

Public domain, on purpose

Moqui is free and open source software, released in the public domain. To make that hold where public domain is not recognized, the projects use the Creative Commons CC0 1.0 Universal Public Domain Dedication.

Because CC0 does not cover patents, the ecosystem also uses a Grant of Patent License adapted from Apache License 2.0. See LICENSE and AUTHORS.

How the project is run

Moderated, not a free-for-all

A small group of moderators review every change to the official repositories. Users, sponsors, and contributors get a code base that stays aligned with the design instead of decaying from convenience commits.

The normal way to get a change in is to work with a moderator — implement it together, or review a patch, revise, and commit. See the Community documentation for collaboration infrastructure.