La Biblia de Nebula 3 (guía 2.0)

Alguien escribió:

Rules are very simple:

A)

- 3rd party developers could sell libraries in the same way they were doing in the past. Nothing changed. Previous rules are valid for old developers. Basically all developers who joined our betatesting program before 1 january 2014 can use tools created till that date, nat 1.3.609 for developers. In the previous model we were not asking royalties or any form of payment

- those libraries will be available also in nebula4, because nebula4 will be backward compatible

- they could skin those libraries in simple way, more or less like they are doing today. Those libraries are based on old engines, working on single instances. There were several updates they can take advantage of, for example new envelope followers, faster program rate and so on. But basically they are using old tools, created when our costs were almost zero and we had zero competition from their work

B)

- for old developers AND new developers we started a new 3rd party developers program with new rules/options and a new business model

- basically if they want access tools created after 1 january 2014 they should join our annual workshop

- they should sign a nda agreement

- they access new tools, very powerful. One of them is Nat4.

- they access more or less tools create 1 year back, or even latest tools if there is a good feeling between acustica and them. Basically we need developers who are using tools wthout creating competition on the things we released recently paying directly for their development. I think it is reasonable: if I create a tech which I paid 70K, I need to recover costs before someone else becomes a competitor using the same tools I paid for. Otherwise we need to share costs.

- all new things they learn in those workshops are covered by the nda agreement, still keeping the old model when they want to release a nebula 3 library

- if they want to release a nebula4 library (and here I mean a skinned multi-instance acqua library) they should sign a contract, where basically they agree to pay a royalty, which is more or less 30% of gross. We support bugs and users. We support copy protection. We are following the itunes/apple model.

- nebula4 libraries could be translated to acqua plug-in if there is an agreement on the specific item on both sides.

- even signign this contract previous rules will be valid: so they could sell nebula3 libraries from their site still not paying anything, and new acqua libraries paying the royalty

This royalty covers a lot of hidden costs: our development costs, our support and obviously the competition we have from their libraries! for example if they release a pultec library I stop selling purple, so I need obviously a business model which works. It is true that nebula platform partially pays several developements (basically if they release a product we sell more nebula plugins), but it is not enough for covering all possible costs on our side.

C)
- soon there will be an evolution of model B) with more advantages on the customer side, and a good forecast of growth, more options. No, not a boring subscription.


Hope it helps. We try to be very straight on all points and very clear on our requirements, because this is the only way for a constructive discussion about the whole business model with both 3rd party and end users.

Musicality escribió:

Yo en el tema de la version final no me preocuparía mucho, debería funcionar igual o mejor, y a malas siempre tienes la opción de hacer un reembolso en 30 días.