74 components. 72 open source allies.
Infinite combinations.

74 NinoTech components provide the substantial base. 72 curated open source projects extend into domain-specific depths. A Bayesian scoring engine works the same for dental reliability, polluter accountability, and ROSCA contributions. The assembly is the product.

The universal stack

Across 69 researched use cases — with 72 open source projects now cataloged as extensions —, four components appear in 80%+ of viable deployments. This is the platform thesis: federation + zero-cost backend + multilingual content + privacy-preserving aggregation constitutes a universal architecture for the world's cooperative, community-based, and sovereignty-oriented organizations.

58
of 69 use cases
Federation Protocol
52
of 69 use cases
Sheets Backend
45
of 69 use cases
k-Anonymity
40
of 69 use cases
CEFR Multilingual

Why federation is the moat

Every civic sector is structurally federated. Tribes won't cede sovereignty. Mutual aid groups resist hierarchy. P&A agencies operate independently by statute. Library systems have separate governance. 75,000 PTOs share nothing. No competing platform — not Unite Us, not Watermark, not LegalServer, not Geographic Solutions — offers federation as a first-class architectural primitive. They're all centralized. This architecture is the only one that matches how the civic sector actually works.

Why $7/year changes the conversation

Competitors charge $10,000–$500,000 per year in perpetuity. NinoTech front-loads cost and eliminates recurring dependency. Static HTML + Google Sheets + Cloudflare Workers. No servers to maintain. No licenses to renew. No vendor to negotiate with. For grant-funded organizations facing sustainability requirements, this distinction is decisive — the technology outlives the grant.

N→B→F: the scaffold underneath

Normal → Broken → Fix. How does this system function? Where is the breakdown? What addresses it? This diagnostic reasoning architecture originated in clinical medicine and has been validated across 12+ domains. It is not a biology tool. It is not a civic tool. It is a reasoning tool. Content changes; the scaffold does not. That's why 74 components built for specific contexts recombine for contexts they were never designed for — the reasoning pattern is universal.

How the components bundle into products

The 74-component library is the substrate. Products are curated bundles for specific audiences. The flagship bundle is the NinoTech CC Suite — community college institutional infrastructure — which contains five complementary components sharing the same scaffold, the same Sheets backend, the same federation protocol, and the same data-portability commitment.

01
Governance
Admin Eval
02
Learning outcomes
Assessment Hub
03
Honors programming
Honors Hub
04
Classroom pilot tooling
Session Guides · QuizPrep · PSA
05
Civic engagement (joining at full production)
CommUnity OS

Components outside the CC suite — Sonrisa (dental hygiene PWA), NinoCare (dental clinic compliance), standalone civic and legal deployments — are other bundles of the same library. A community college institution typically deploys the NinoTech CC Suite. A dental practice deploys Sonrisa plus NinoCare. A tenant union deploys dispute-letter + accountability components from CommUnity OS. The bundle is the product; the components are the inventory. NinoTech LLC is the parent entity; the CC Suite is the flagship bundle.