Open-Core Strategy
Open where trust matters. Commercial where scale matters.
AEGIS is designed around an open-core model: transparent safety logic and developer tooling at the core, with commercial hosted services for monitoring, analytics, policy management, and enterprise scale.
Why Open Source
Trust requires transparency.
Safety infrastructure requires trust. By making the core detection and policy engine open for inspection, AEGIS can support public review, community contributions, security audits, and developer adoption.
Transparency
Public review of detection logic and policy rules.
Adoption
Developers trust systems they can inspect and integrate freely.
Sustainability
Commercial services fund continued open-core development.
Open Source
What will be open.
The following components are designed to be publicly available, auditable, and open for community contribution.
Core policy engine
The foundational detection and scoring logic, open for review and contribution.
Risk scoring logic
The multi-signal risk computation engine.
Safety taxonomy
The harm category definitions and classification system.
Developer SDK foundations
Core SDK interfaces and integration scaffolding.
Example integrations
Reference implementations for common use cases.
Documentation
Public documentation for all open components.
Commercial Layer
Where scale and enterprise readiness live.
Commercial services provide the sustainability that allows the open-core to remain maintained and expanded. They are opt-in and clearly separated from the open components.
Repository Roadmap
Planned public repositories.
AEGIS will progressively open repositories as development matures. Phase 1 is the initial public release.
Core safety engine, policy rules, risk scoring, and explainability.
JavaScript SDK for website and web application integration.
Browser protection extension for family-safe ad moderation.
Public marketing and developer website.
Android and iOS SDKs.
Hosted API services.
Dashboard for developers, organizations, and enterprise users.
Model training, evaluation, and packaging.
Threat intelligence feeds and harmful ad indicators.
Developer and product documentation.
Community
Contributing to AEGIS.
AEGIS aims to build a contributor community grounded in responsible practices and shared principles.
Responsible disclosure
Security vulnerabilities are handled through a clear responsible disclosure process.
Privacy-first defaults
All contributions are evaluated against privacy-first design principles.
Transparent policies
Moderation categories, detection rules, and policies are publicly documented.
Clear contribution guidelines
Contributors receive clear guidance on scope, review, and code standards.
Inclusive community
AEGIS is committed to building a welcoming environment for contributors of all backgrounds.
Safety without surveillance
Community contributions must align with user-first, non-surveillance principles.
Help build open safety infrastructure for the internet.
Follow the project, contribute to early repositories, or join the waitlist to stay updated as AEGIS development progresses.