Price System Emoluments
Libre Goods and Services
As in speech, not beer. I'm only selling my own work product and services albeit built on much FOSS. Making clear that I built this myself is the distinguishing characteristic versus the prevailing economic order, whence the title of this page. Participation outside my owned domains (e.g. @ enwiki are/were public service.
Consumer
Capitation class based pricing doesn't involve developer or operations support and resources are divided proportionally to all members of a clsss.
tl:dr
tl:dr[AK] apps have base free versions with in-additional services tiered by captitation class which can be paid at desired level in-app. GT2 and its subsequent development as a personal carbon domain is typical, the model for the product line as tl:dr[GT2] followed by tl:dr[TASKPM] for personal task management and others.
DCP/MCP Access and Provisioning
Some service is provided free to authenticated and even anonymous users but in general, computing services resource allocation is calculated based on capitation class of the user.
Name Services (.dom TLD)
A range of DNS related service are available to AKPERSONs, from free end domain name mgt to contracted registry/registrar functions, visit the page for details.
Names allocated in the .dom space of my alt-root are covered by entitlement level, but operators of other namespaces set their own policiesDeveloper/Operator
The Rate Chart has current rates for products and services which involve IP development and out-of-class allocation of resources.
Operators
"DevOps" generally refers to users that have admin privileges within a bounded scope and the scope determines whether a developer or an operator.
Developers
Generally, Developer or greater entitlement required for access to my curated/changed sources which are POSS¹ not FOSS, with any FOSS sources in my github account. Conventional code such as php, python, and haskell of DCMS is generally accessible for token entitlement, the KEE environment requires F class and some portions of its sources are not published.
¹ Proprietary, i.e. © juan@acm.org , Open Source SoftwareDocumentation
Versions in the wild are infrequently updated, The current versions are within the authentication perimeter.