Comments? Questions? Get Involved? Join the Forum

Moqui Ecosystem

open source business applications with modern architecture and full rest api

Framework

Moqui

Artifacts

Mantle

Applications

Apps
Demo DL Docs

Moquiis 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

LatestReleases

GitHub.com SourceForge.net

Ecosystem features

Cost Effective

Advanced Tools

Applications

Multi-Instance

Cloud Computing

Low code: less code, less cost. Less code translates to less development, maintenance, and support. The efficient and flexible Moqui Framework tools dramatically reduce your code size and complexity. The existing business artifacts (data model, services, screens/forms, integrations, etc) mean you have less to build.

How much less code? In one large project over a million lines of code was replaced with less than 100k.

The difficult made easy. Moqui Framework uses many of the best open source Java libraries plus a set of innovative tools for persistence, logic, user interfaces, and integration... all designed to work together OOTB to make your life easier.

Need to build a REST API? Easy. Need to use a REST or other API? Easy.

Need to index database records on the fly for full text search or analytics? Easy.

Need to build an integration with managed message production and consumption? Easy.

Need runtime configuration of authorization for screens, services, entities and even automatic query filtering? Easy.

Existing applications to use or customize. The existing open source applications give you a starting point for your custom or commercial applications. They are not just useful as-is but also provides hundreds of examples of how to build different UI elements and use the generic business artifacts.

Need Saas? No problem. The multi-instance features in Moqui Framework make it easy to offer your Software as a Service. With provisioning services in Moqui and subscription products in Mantle it is easy to setup an ecommerce and self-service web site for access to your software. Each instance runs in its own container or VM and with its own database. Provisioning services are included for Docker and MySQL. There are service interfaces you can implement for any host environment or database.

Easy to deploy. Applications built on Moqui Framework can be distributed as a standalone executable archive or a standard WAR file (with runtime configuration and add-ons separate or embedded). This makes it easy to deploy on virtual machines, container based infrastructure, on-premise and in private clouds. For large deployments Moqui supports session replication, distributed caching, and much more to scale up application server pools.

Open SourceLicense

CC0

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)

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.

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