open source business applications with modern architecture and full rest api

Moqui is for

End-user organizations who need custom software, from existing system
augmentation to complete end-to-end systems; take back your systems: own
your data, own your code

Commercial software vendors looking for a reliable and flexible foundation,
allowing focus on differentiating features

Custom software consultants and system integrators who need tools and
reusable artifacts to efficiently build anything a client might want

Developers, architects, designers, and analysts tired of reinventing the
wheel and spending months or years getting version 1.0 out the door


Open Source License
Moqui is free and open source software, released in the public domain.

To firmly establish this and to clarify terms in jurisdictions where public domain status is not recognized, Moqui uses the Creative Commons CC0 1.0 Universal Public Domain Dedication.

Because CC0 1.0 does not cover patent issues, the Moqui Ecosystem projects also use a Grant of Patent License adapted from Apache License 2.0. See the full details in the LICENSE and AUTHORS files.

Resource Model

  • Model

    To maintain a high level of quality and provide for long-term sustainable maintenance Moqui is operated using a professionally moderated code base model. This model is based on free-market principles and takes in account the motivations and needs of all parties involved:

    • user: any user of the software (developer, end-user, etc)
    • sponsor: anyone who backs new features and changes to the software
    • contributor: developer who contributes code and then collaborates with (or hires) a moderator to make it part of a project
    • moderator: developer with commit (push) access to the official code repositories and who personally works on the design, development, and maintenance of the software (intentionally small group)
  • Code Review

    No changes go into the official code repository without detailed personal review by one of the moderators. It is common for users of software to want certain things to be different, or new things to be added. Under this model the normal way to get this done is to work with a moderator to either implement the desired changes, or review a patch from the contributor, make revisions as needed, and then commit the changes.

  • Benefits

    Under this model:

    • users get a piece of software that is well thought out and thoroughly reviewed
    • users save time wasted by meaningless changes causing them problems
    • users don't have to worry about bad changes being committed without thorough review
    • users can count on software that will be around for a long time
    • contributors don't wait endlessly for feedback or worry about contributions being ignored
    • contributors can count on detailed feedback and, as needed, discussion and collaboration to get the best possible change committed, or a good explanation of why it won't be
    • sponsors enjoy fast response times to requests for new features or other changes
    • the software stays aligned with design goals
    • the software does not suffer from decay over many years of life as random people scratch random itches or commit for convenience based on requirements for particular projects