APEASE is an acronym for Agreement, Partners, Executives, and Software Engineers.
From all seminal innovations cloudyBoss has brought to market over the past decade, its APEASE licensing, away from both proprietary and open source ones, grows from strength to strength and remains one of its quintessential cornerstones. Since inception, cloudyBoss has always focused on market needs and dynamics more than capital injections, attaching more importance to its journey, goals/destination rather than celebrating the few “petrol station refills” required to get there, i.e. real high-value digital and hybrid assets, as well as wide-scope industry ecosystem projects rather than, mostly elusive conventional investors’ validations. Its self-funding APEASE modus operandi, applied to all core assets, has strengthened cloudyBoss in this path.
Historically, APEASE emerged out of necessity, as a solution to a specific contractual problem affecting the cloudyBoss ecosystem, i.e. the multiplication of overlapping relationship types between ecosystem nodes. This specific issue, affecting around 30% of partners, was flagged as a potential governance risk due to the multiplication of contracts between cloudyBoss group and same partners, each contract covering a specific relationship type. This type of situation was flagged for its potential to create cross-contract conflicts and nullifying risks. Along the way, and aside from its practical necessity-driven inception, cloudyBoss became in 2008 (and still is to this day) the only organization to successfully tokenize code via its APEASE model, and neutralize the devastating impacts on software quality, derived from the ghost-writing plagues underpinning proprietary software licensing, and the free-riding house of cards upon which open source is built.
While APEASE initially aimed to address and successfully tackled the code quality root problem crippling the IT industry, outcomes from its application have broadened way beyond coded assets only, extending to content and executive actions. APEASE code tokenization principles (both a modern tokenized version of the risk-diluting original Dutch corporate model, as well as one inspired by, and derived from the music and publishing industries) are essential to cloudyBoss elastic architecture and extend today to content and all functional asset classes.
Most importantly, APEASE has put cloudyBoss in an enviable position as one of the rare organizations that have organically achieved a 50/50 engineering gender balance, while scoring a very high engineering retention rate at 5+ years vs 18 months (and imploding) for the rest of the IT industry. Such engineering longevity and high levels of code ownership cement with clients cloudyBoss guarantee of, and assurance in the highest possible levels of product and services quality and excellence. cloudyBoss APEASE licensing model has also disrupted conventional start-up and scale-up venture funding mechanisms, expanding beyond its ecosystem boundaries, promoting it to clients and partners as a key tool to achieve fast and resilient ecosystem scale-up, maximizing the outcome of smarter sweat equity, and refocussing entrepreneurs in creating sustainable top and bottom line revenues, rather than wasting precious time in elusive capital raising, via structured and short-termistic business intelligence leakages.
The best way to understand how APEASE works is to compare it to the royalty-based business models applied in the music and publishing industries: with APEASE, software engineers code once, however receive royalties on assets they’ve coded for their entire lifecycle, similarly to authors or song-writers. Software engineers also own the rights to such assets and can trade them. This asset ownership is additional to APEASE partners benefits under CSOP (cloudyBoss Stock Option Program) which provides first-generation engineers (original non-traded asset creators) with additional benefits in the form of stock options in the cloudyBoss inner core group of companies.
This simple model ensures greater levels of “code ownership”, enhances overall code quality, therefore strengthens cB stack in terms of features, performance, quality, and security, which recursively boosts the entire ecosystem and accelerates the reaching of its core vision, mission and goals.
APEASE principles are discussed in this video interview between 5:44 and 10:30.