Definition
Digital inequality refers to the systemic disparities in access to digital technologies, internet connectivity, digital literacy, and the ability to meaningfully participate in and benefit from the digital economy and society. Unlike the simpler concept of the "digital divide" -- which originally described binary access/no-access distinctions -- digital inequality encompasses a spectrum of disadvantages including quality of access (bandwidth, reliability, device capability), skills and literacy gaps, affordability barriers, linguistic and cultural exclusion, geographic disparities, and the compounding effects of proprietary vendor lock-in that concentrates technological capability in the hands of those who can afford commercial licenses.
In the context of the Prismatic Platform, digital inequality is addressed directly through the platform's open-source commitment, the GHL license, the community-over-corporation philosophy, and the deliberate decision to build enterprise-grade security intelligence, OSINT, and compliance tooling as freely available open-source software rather than proprietary SaaS products.
Overview
Digital inequality is one of the defining challenges of the 21st century. The International Telecommunication Union (ITU) reports that approximately 2.7 billion people remain offline, and among those who are connected, vast disparities exist in the quality, affordability, and usefulness of their access. These disparities correlate strongly with existing socioeconomic inequalities -- income, education, geography, gender, age, and disability -- creating feedback loops that amplify disadvantage.
The technology industry itself contributes to digital inequality through several mechanisms:
Proprietary Lock-In: Enterprise software vendors charge thousands to millions of dollars for security, compliance, and intelligence tools that are essential for operating in regulated industries. Organizations that cannot afford these tools face heightened security risks, compliance gaps, and competitive disadvantages. This creates a two-tier system where well-funded enterprises have access to sophisticated tooling while smaller organizations, nonprofits, educational institutions, and developing-world businesses operate with inadequate protection.
Knowledge Gatekeeping: Technical knowledge is frequently locked behind paywalls, proprietary certifications, and closed ecosystems. When security research, threat intelligence, and best practices are only available to paying customers, the broader community is left more vulnerable.
Algorithmic Exclusion: AI and machine learning systems trained on biased data can perpetuate and amplify existing inequalities. Hiring algorithms, credit scoring, content recommendation, and risk assessment systems can systematically disadvantage underrepresented groups.
Infrastructure Concentration: Cloud computing, SaaS platforms, and digital infrastructure are concentrated among a small number of large providers. This concentration creates single points of failure, vendor dependency, and pricing power that disproportionately affects smaller organizations.
Language and Cultural Barriers: Most technology documentation, developer tools, and educational resources are available primarily in English, creating barriers for the roughly 80% of the world's population that does not speak English as a primary language.
The open-source movement represents the most significant countervailing force against digital inequality in technology. By making source code freely available, open-source projects democratize access to technology capabilities that would otherwise be locked behind commercial licenses. The Prismatic Platform embodies this principle by providing enterprise-grade security intelligence, OSINT capabilities, compliance tooling, and quality infrastructure as open-source software.
Technical Details
The Architecture of Technological Exclusion
Proprietary software creates inequality through several technical mechanisms:
API Restrictions: Commercial platforms expose limited functionality through free tiers while reserving critical capabilities for paid plans. Rate limiting, feature gating, and data export restrictions create dependency and prevent organizations from building on top of these platforms without ongoing payment.
Data Format Lock-In: Proprietary data formats prevent users from migrating between platforms or accessing their own data without the vendor's software. This creates switching costs that effectively trap users in ecosystems regardless of price increases or quality degradation.
Closed Protocols: Proprietary communication and integration protocols prevent interoperability between systems, forcing organizations to purchase all components from a single vendor or pay integration premiums.
Open-Source as Equalizer
The Prismatic Platform addresses these exclusion mechanisms through deliberate architectural decisions:
defmodule Prismatic.Platform.Principles do
@moduledoc """
Core principles governing the Prismatic Platform's approach
to reducing digital inequality through open-source technology.
Every architectural decision is evaluated against these principles
to ensure the platform remains accessible, open, and equitable.
"""
@type principle :: %{
name: String.t(),
description: String.t(),
enforcement: :hard | :soft,
violations: non_neg_integer()
}
@principles [
%{
name: "Open Source First",
description: "All core functionality is available under the GHL open-source license",
enforcement: :hard,
violations: 0
},
%{
name: "No Feature Gating",
description: "Security, compliance, and intelligence features are not locked behind paid tiers",
enforcement: :hard,
violations: 0
},
%{
name: "Open Data Formats",
description: "All data is stored in open, documented formats with full export capability",
enforcement: :hard,
violations: 0
},
%{
name: "Standard Protocols",
description: "All integrations use open standards (REST, OpenAPI, WebSocket) over proprietary protocols",
enforcement: :hard,
violations: 0
},
%{
name: "Self-Hostable",
description: "The entire platform can be self-hosted without vendor dependency",
enforcement: :hard,
violations: 0
},
%{
name: "Comprehensive Documentation",
description: "All features are documented in freely accessible CLAUDE.md and public documentation",
enforcement: :soft,
violations: 0
}
]
@spec all_principles() :: [principle()]
def all_principles, do: @principles
@spec compliance_score() :: float()
def compliance_score do
total = length(@principles)
compliant = Enum.count(@principles, &(&1.violations == 0))
compliant / total * 100.0
end
@spec hard_violations() :: [principle()]
def hard_violations do
Enum.filter(@principles, &(&1.enforcement == :hard and &1.violations > 0))
end
endAccessibility Architecture
The platform implements technical accessibility measures that reduce barriers to adoption:
defmodule PrismaticWeb.Accessibility do
@moduledoc """
Accessibility infrastructure ensuring the platform's web interfaces
are usable by developers and operators regardless of ability.
Implements WCAG 2.1 AA compliance across all LiveView components
with automated testing via axe-core integration.
"""
@type audit_result :: %{
violations: [violation()],
passes: non_neg_integer(),
incomplete: non_neg_integer(),
score: float()
}
@type violation :: %{
id: String.t(),
impact: :critical | :serious | :moderate | :minor,
description: String.t(),
nodes: [String.t()]
}
@spec audit_page(String.t()) :: {:ok, audit_result()} | {:error, term()}
def audit_page(url) when is_binary(url) do
with {:ok, page} <- fetch_rendered_page(url),
{:ok, results} <- run_axe_audit(page) do
{:ok, compile_results(results)}
end
end
@spec meets_wcag_aa?(audit_result()) :: boolean()
def meets_wcag_aa?(%{violations: violations}) do
critical_or_serious = Enum.filter(violations, &(&1.impact in [:critical, :serious]))
Enum.empty?(critical_or_serious)
end
@spec fetch_rendered_page(String.t()) :: {:ok, String.t()} | {:error, term()}
defp fetch_rendered_page(_url), do: {:ok, ""}
@spec run_axe_audit(String.t()) :: {:ok, map()} | {:error, term()}
defp run_axe_audit(_page), do: {:ok, %{}}
@spec compile_results(map()) :: audit_result()
defp compile_results(_results) do
%{violations: [], passes: 0, incomplete: 0, score: 100.0}
end
endDocumentation Accessibility
The Prismatic Platform's documentation strategy directly addresses knowledge gatekeeping by providing comprehensive, freely accessible documentation at every level:
- Root CLAUDE.md: 500+ lines covering platform architecture, conventions, commands, and quality standards
- Application CLAUDE.md: Every one of 115 umbrella applications has its own documentation
- Promo Site: 1,873 markdown files across 18 sections providing public documentation
- Glossary: 200+ terms with cross-references, code examples, and learning paths
- AIAD Specifications: 530 agent definitions and 225 command specifications are publicly documented
Implementation in Prismatic Platform
The Prismatic Platform's approach to digital inequality is not merely philosophical -- it is encoded in architectural decisions, licensing choices, and platform capabilities.
GHL License
The platform is released under the GHL (GitHub License) open-source license, which ensures that all platform functionality remains freely available. Unlike "open core" models where critical features are reserved for commercial editions, the Prismatic Platform's GHL license covers the entire platform including security intelligence, OSINT capabilities, compliance tooling, and enterprise-grade quality infrastructure.
Enterprise Capabilities Without Enterprise Pricing
The platform provides capabilities that typically require expensive commercial licenses:
- Security Ratings (A-F): Comparable to BitSight, SecurityScorecard ($25K-500K/year commercial pricing)
- OSINT Intelligence: 120 data source adapters comparable to Maltego, SpiderFoot ($5K-50K/year)
- Compliance Assessment: NIS2, ZKB, SOC 2 mapping comparable to Vanta, Drata ($10K-100K/year)
- Attack Surface Management: Comparable to Censys, Shodan Enterprise ($10K-100K/year)
- Quality Infrastructure: 225 automated commands comparable to SonarQube Enterprise ($15K-150K/year)
Self-Hosting First
The platform is designed for self-hosting from day one. All dependencies (PostgreSQL, Redis, Meilisearch, KuzuDB) are open-source, and the deployment infrastructure uses standard Docker containers deployable to any cloud provider or on-premises server. This eliminates vendor lock-in and allows organizations in any geography or economic context to run the full platform on their own infrastructure.
Community-Over-Corporation
The platform's community-over-corporation philosophy prioritizes community benefit over corporate profit. Decisions about feature development, licensing, and platform direction are made with the explicit goal of maximizing access and minimizing barriers to adoption.
Comparison with Alternatives
| Approach | Accessibility | Sustainability | Effectiveness |
|---|---|---|---|
| Proprietary SaaS | Gated by pricing tiers | Venture capital driven | High quality but exclusive |
| Freemium/Open Core | Limited free tier, critical features paid | Conversion-driven | Creates dependency on paid features |
| Community Open Source | Fully accessible | Volunteer-dependent, fragile | Variable quality, slow development |
| Corporate Open Source | Accessible but subject to relicensing | Corporate sponsor dependent | High quality but risk of rug-pull |
| Prismatic Model | Fully accessible, self-hostable | Creator-driven with community governance | Enterprise-grade, fully open |
Best Practices
-
Default to Open: Release all functionality under open-source licenses. Reserve no critical features for commercial tiers. If functionality is essential for security or compliance, it must be freely available.
-
Comprehensive Documentation: Invest heavily in documentation that is freely accessible, clearly written, and regularly maintained. Documentation is the primary mechanism through which open-source projects bridge knowledge gaps.
-
Standard Protocols and Formats: Use open standards (REST, OpenAPI, JSON, CSV) for all interfaces and data formats. Proprietary formats create lock-in that disproportionately affects organizations without resources to build custom integrations.
-
Self-Hosting Support: Design for self-hosting as the primary deployment model. Cloud hosting should be an option, not a requirement. Self-hosting eliminates recurring costs and vendor dependency.
-
Accessible Interfaces: Build interfaces that meet WCAG 2.1 AA accessibility standards. Digital inequality includes disability-related access barriers that compound with economic and geographic barriers.
-
Multilingual Readiness: Design systems with internationalization (i18n) support from the start. Even if initial content is English-only, the architecture should support future localization without redesign.
-
Low System Requirements: Optimize for performance on modest hardware. Not every user has access to high-end workstations or powerful cloud instances. The Prismatic Platform's use of BEAM VM provides excellent performance on commodity hardware.
-
Transparent Governance: Maintain transparent decision-making processes for platform direction. Community ownership is undermined when governance is opaque or concentrated.
Common Pitfalls
-
Open-Source Washing: Releasing software as "open source" while reserving essential functionality for commercial editions. This "open core" model uses open-source branding to attract users while maintaining proprietary gatekeeping of critical capabilities.
-
License Rug-Pulls: Companies that build community around open-source projects and then change to restrictive licenses (Redis, Elasticsearch, HashiCorp). This erodes trust and harms organizations that built on the open-source version.
-
Documentation Neglect: Releasing code as open source without investing in documentation, examples, and onboarding materials. Code without documentation is theoretically accessible but practically unusable.
-
Ignoring Non-Technical Barriers: Focusing solely on code accessibility while ignoring economic (hosting costs), linguistic (English-only docs), cultural (Western-centric assumptions), and educational (assumed prerequisites) barriers.
-
Unsustainable Models: Building open-source projects on volunteer labor alone without establishing sustainable funding models. Burnout and abandonment of critical open-source projects creates new forms of digital inequality when dependent organizations lose maintained tooling.
-
Token Accessibility: Adding accessibility features as afterthoughts (alt text, ARIA labels) without fundamentally designing for inclusive access from the architecture level.
-
Complexity as Barrier: Building powerful but overly complex systems that require expert-level knowledge to deploy and operate. Complexity creates de facto access barriers even when the code is freely available.
Use Cases
Democratizing Security Intelligence
Small and medium enterprises, nonprofits, and educational institutions face the same cybersecurity threats as large enterprises but lack budgets for commercial security platforms. The Prismatic Platform's Prismatic Perimeter provides enterprise-grade security ratings, attack surface management, and compliance assessment at zero licensing cost.
Open OSINT Tooling
Open-source intelligence gathering capabilities are critical for journalism, human rights research, academic investigation, and law enforcement in resource-constrained jurisdictions. The platform's 120 OSINT source adapters provide capabilities comparable to commercial tools costing tens of thousands of dollars annually.
Educational Access
Universities and coding bootcamps can use the full Prismatic Platform for teaching software engineering, security operations, and platform architecture without licensing restrictions. Students gain experience with production-grade tooling rather than simplified educational versions.
Developing World Technology Transfer
Organizations in developing economies can deploy the full platform stack on locally hosted infrastructure, building indigenous technology capability without creating dependency on Western cloud providers or SaaS vendors.
Compliance for Small Organizations
Small businesses subject to NIS2, ZKB, or similar regulations can assess and demonstrate compliance using the platform's automated compliance assessment rather than hiring expensive compliance consultants or purchasing commercial GRC (Governance, Risk, Compliance) platforms.
Related Concepts
- Open Source -- Software development model where source code is freely available for use, modification, and distribution
- Community Building -- The practice of developing engaged communities around shared interests and goals
- Community Over Corporation -- Philosophy prioritizing community benefit over corporate profit in technology decisions
- Community Ownership -- Governance model where the community collectively stewards technology direction
- Share Openly -- Principle of making knowledge, code, and research freely available
- Collaborative Development -- Development practices that enable distributed contribution
- Complete Transparency -- Principle of full visibility into platform decisions, code, and governance
- Sustainable Funding Models -- Economic models that sustain open-source development without compromising access
- Developer Community -- The community of developers who build on and contribute to the platform
- Collective Progress -- Advancement achieved through collaborative rather than competitive effort
See Also
- Transparency Builds Trust -- The relationship between openness and community trust
- Developer Portal -- The platform's freely accessible developer documentation
- Compliance Framework -- Automated compliance assessment available to all users
- Quality Gates -- Enterprise-grade quality infrastructure provided as open source
- Prismatic Perimeter -- Free attack surface management competing with commercial vendors
Connect & Contribute
Created by Tomáš Korcak (korczis) | Open Source under GHL