Jeff Karau

Without using QP, I don't believe we could have delivered on our given schedule dates with the same level of quality."

Jeff Karau, Sr. Software Engineer, General Dynamics C4 Systems

Henrik Bohre

...After trying out a couple of CASE tools we came to the conclusion that expensive round-trip-engineering UML tools were cumbersome and did not fit our way of working. However, the innovative QP way to map UML state machines to C/C++ code was exactly what we were looking for..."

Henrik Bohre, Embedded Systems Consultant, GotCom AB, Göteborg, Sweden

Michael_Barr

I'm speaking from first-hand experience when I say this is really good stuff. I just hope others will recognize that and we can get past the old main+ISR vs. RTOS dilemma for a large variety of applications."

Michael Barr, President Netrino and former editor-in-chief of the ESP magazine

Haitham Hindi

Practical Statecharts in C/C++ has been an indispensible reference for my embedded systems work. The clear and succinct conceptual and software framework, along with the immediately usable code enabled us to get a working prototype of our control system in a few weeks."

Dr. Haitham Hindi, Palo Alto Research Center (PARC)

Paul Montgomery

...QP has been adopted accross the company and is used in all our products on a variety of OS platforms..."

Dr. Paul Montgomery, Director of Engineering, Novariant, Fremont CA

Stratos Product Development

We're glad to keep giving Quantum Leaps our business. QP has been really valuable for us—we've had a great experience working with Quantum Leaps frameworks and tools. It's been a big help in terms of delivering high-quality software within our clients' budgets, so thank you!"

Jason Machacek, Software Engineer, Stratos Product Development LLC, Seattle WA

EIM Controls, Inc.

I used the traditional RTOS approach for about 10 years. With the real-time debug log of QSPY and the ability to see what is going on in the logic flow, the code is very easy to debug and modify. It makes the code very modular and deterministic... You end up talking about the codes logic flow, and not the semantics of the software. QP is a great product."

Paul Walker, Software Engineer, EIM Controls, Inc.

Apple Computer, Inc.

I recently rewrote a major piece of code to utilise the QP framework and it has worked wonders. My previous code used a more traditional state machine and had quickly evolved into spaghetti code. The hierarchical state machine approach made the new code smaller, more robust, and much easier to maintain and extend."

Bob Bradley, Apple Computer, Inc., from Amazon.com review

Honeywell International

Quantum Leaps software has revolutionized not just the way we write our software, but the way we approach our design. It is intuitive, easy to implement and comes in an incredibly small package. If you're in the 8-bit world, you need this software!"

Chad Koster, Software Engineer, Honeywell

Rich Wooley

Simply put, designing sofware using the QP framework lets you code the way you think..."

Rich Wooley, Sofware Engineer, Nipro Diabetes Systems, Florida

more user stories

Frequently Asked Questions about Licensing

What is QP™ frameworks licensing model?

Quantum Leaps uses the popular dual licensing strategy for the QP™ frameworks. Duality means here that both the open software distribution mechanism and traditional software product business are combined.

The licenses we use for the QP™ frameworks are: GNU General Public License version 3 (GPL) and a set of Quantum Leaps proprietary commercial licenses.

Dual licensing of the QP™ frameworks provides open access to our technology both for the GPL community and for other developers or companies that cannot use the GPL. Please refer to section Licensing Overview for more information.

Can I use QP™ frameworks even though my company's policy forbids open source?

Absolutely. You can apply for a traditional, closed-source commercial license. All Quantum Leaps commercial licenses expressly supercede the open source GPL license. When you are using the software under a commercal license, your use has nothing to do with open source and you don't violate your no-open-source policy.

What is the legal foundation behind the dual licensing model?

The legal requirement for dual licensing is the ownership of the copyrights to the licensed software. According to the copyright law, the owner of the copyright can license his or her intellectual property any number of times. Distributors of proprietary software do that all the time when they grant discounts to favored customers, issue blanket licenses for unlimited copies to large corporations, and apply shrink-wrap licenses to copies sold in stores [Rosen 04].

From the legal standpoint, GPL is no different from any other license and does not preclude other distribution strategies. The authors of the GPL recognize that fact through the following sentence in Section 7: "...it is up to the author/donor to decide if he or she is willing to distribute software through any other system..."

Is Quantum Leaps dual license policy still "open source"?

Absolutely, as long as your software is 100-percent GPL-compliant open source, Quantum Leaps is 100-percent GPL-compliant open source vendor that is indistinguishable from any other "pure" open source providers.

The commercial side of our business is a way of attracting new customers by offering them a choice to extend the use of our software beyond the limits of the GPL. Commercial licensing options reach out to customers that otherwise would not be able to use Quantum Leaps solutions at all.

Are other companies using the dual licensing business model?

Yes, the dual licensing business model is becoming increasingly popular among open source companies as it paves the way for long-term financial viability. Other companies that offer dual licensing include MySQL, Trolltech, Sleepycat, RealNetworks' Helix project, OpenOffice.org, Digium, OSAF, MandrakeSoft, Technical Pursuit Transvirtual Technologies, and others.

How do I know which license to use?

The overall guiding principle of dual licensing is one of fair exchange or quid pro quo which means "something for something". So if your software is 100 percent open source and GPL-compatible, we encourage you to use the GPL-version of Quantum Leaps software. For all other users, we recommend that you purchase one of our commercial licenses.

Linux™ applications are not ordinarily considered a GPL derivative. Why then QP™ applications are?

Indeed, past accepted use demonstrates that in the case of Linux™, any application that runs in the User Space is not ordinarily considered a GPL derivative, (provided it uses standard system calls). However, statically linked binaries that run in the Kernel Space are presumed to be Linux™ derivatives. Moreover, binary-only distributions running in either the User Space or the Kernel Space could still be considered GPL derived works. (See the online article "Linux GPL Derivatives in a Nutshell")

In contrast to Linux™, applications based on the QP™ frameworks are always statically linked with the QP™ library. Therefore, QP™ itself must be considered an inseparable "part of a whole". GPL Section 2 clearly prescribes that in this case "the distribution of the whole must be on the terms of this [GPL] License". (For more information on our guidelines for distributing application software please refer to our "Open Source Licensing" section.)

Do I get the same QP™ frameworks under either license?

Yes. All Quantum Leaps products are identical under either the GPL license or the commercial licenses. This is the only way compatible with the open source mission, as described by Richard Stallman in his article On Selling Exceptions to the GNU GPL. Specifically to this question, Richard Stallman explains:

We must distinguish the practice of selling exceptions from something crucially different: proprietary extensions or proprietary versions of a free program. These two activities, even if practiced simultaneously by one company, are different issues. In selling exceptions, the same code that the exception applies to is available to the general public as free software. An extension or a modified version that is only available under a proprietary license is proprietary software, pure and simple, and no better than any other proprietary software.

How much does a commercial QP™ license cost?

At Quantum Leaps we are as open with pricing as we are open with respect to our source code. The complete price list for our commercial licenses and support contracts is available from the "Commercial Licensing" section of this web site.

Can I evaluate QP™ frameworks under the GPL even though I have commercial use in mind?

Yes, you can use the GPL version for evaluation as long as you don't distribute Quantum Leaps software or any derivative works based upon it in any way. In this respect, evaluating dual-licensed software delivers a large advantage over highly supervised trial licensing practices still so common in the embedded systems marketplace.

Obviously, when you decide to distribute any portion of our software or any derivative works based on it, you go beyond the GPL limits and therefore you should purchase one of our commercial licenses.

How can I contribute to QP™ frameworks?

Even though QP™ frameworks are open source, no third-party contributions are accepted into the QP source code. This is necessary to be sure about the provenance of the code and to be able to offer the "warranty of provenance" to the commercial customers, which is central for practicing the dual-licensing business model. The open source community contributes by performing "massive parallel testing" and then reporting bugs, usability issues, new insights, and feature requests. Please see the Free Support Forum, QP/QM bug Tracker, and QP/QM Feature Requests.

Can Quantum Leaps ever take away the code?

The simple answer is no. Even if circumstances beyond our control prevent Quantum Leaps from producing new open source editions the QP™ frameworks once released under the GPL belong forever to the open source community.

Last updated: January 10, 2014