Skip to content
islamu-ngoPublic

Latest commit

Β 

History

3,325 Commits

Folders and files

NameName
Last commit message
Last commit date
Β 
Β 
Β 
Β 
Β 
Β 
Β 
Β 
Β 
Β 
Β 
Β 
Β 
Β 
Β 
Β 
Β 
Β 
Β 
Β 
Β 
Β 
Β 
Β 
Β 
Β 
Β 
Β 
Β 
Β 
Β 
Β 
Β 
Β 
Β 
Β 
Β 
Β 
Β 
Β 
Β 
Β 
Β 
Β 
Β 
Β 
Β 
Β 
Β 
Β 
Β 
Β 
Β 
Β 
Β 
Β 
Β 
Β 
Β 
Β 
Β 
Β 
Β 
Β 
Β 
Β 
Β 
Β 
Β 
Β 
Β 
Β 
Β 
Β 
Β 
Β 
Β 
Β 
Β 
Β 
Β 
Β 
Β 
Β 
Β 
Β 
Β 
Β 
Β 
Β 
Β 
Β 
Β 
Β 
Β 
Β 
Β 
Β 
Β 
Β 
Β 
Β 
Β 
Β 

ISLAMU logo

ISLAMU Event

Self-hostable, open-source event discovery and management software for communities, organizations, and platform operators.

ISLAMU Event will power ISLAMU’s upcoming community events instance, but the software itself is purpose-agnostic, white-label, and designed to be rebranded for any event ecosystem.

🚧 Active Pre-Release Development: ISLAMU Event has no official release yet. We are actively fixing startup bugs and preparing for our very first release soon! Pre-built container images and release tags are not yet published.

GitHub Workflow Status Coverity Scan Build Status GitHub License GitHub Repo Stars GitHub Last Commit Contributors Discussions Discord Documentation Donate via Stripe

Official Docs (GitBook) Β· Roadmap Β· 5-Minute Quickstart Β· Self-Hosting Β· Developer Guide Β· Sponsor

Event List Screenshot

About ISLAMU Event

ISLAMU Event is a self-hostable event discovery and management platform for publishing, discovering, and operating events across one organization or many isolated tenants.

The public ISLAMU instance is Islamic-focused, but the software itself is purpose-agnostic, white-label, and designed to be rebranded for any event ecosystem.

✨ Who It Serves

Event Seekers

  • πŸ” Intuitive Event Discovery: Search effortlessly by keyword, date, location, category, and tags to find gatherings near you or online
  • πŸ‘¨β€πŸ‘©β€πŸ‘§β€πŸ‘¦ Culturally-Aware Filters: Filter events by age groups, family/gender arrangements, community traditions, or prayer-relative timings to find gatherings tailored to your preferences
  • 🌐 Multi-Language Sessions: View event details and attend sessions in your preferred language with localized schedules
  • πŸ“± Mobile-First Experience: Fast, responsive experience across mobile and desktop, installable directly to your home screen as an app (PWA)
  • βœ… Easy RSVP & Waitlists: Reserve your spot in seconds, select specific sessions, and automatically join waitlists for sold-out events
  • 🎟️ Clear Ticket Options: Browse free and paid events with upfront ticket tiers, live availability, and no hidden surprises
  • πŸ’³ Secure Payments: Pay for your event tickets safely directly on our platform with transparent pricing, secure checkout, and instant digital tickets β€” see Payments
  • πŸ€– AI Event Assistant: Ask questions in natural language, discover events tailored to your interests, and get quick help drafting your registrations

Event Organizers

  • πŸ“… Comprehensive Event Builder: Organize single-day workshops, multi-day conferences, or recurring programs with multi-track agendas, speaker profiles, and multi-language support
  • πŸ“Š Registration & Attendee Controls: Set capacity limits, customize registration approval workflows, manage automated waitlists, and configure public or unlisted visibility
  • πŸ‘₯ Team Collaboration: Invite co-organizers, assign granular roles (Owner, Admin, Editor, Viewer), and manage organization permissions collaboratively
  • 🧩 Custom Registration Fields & Forms: Collect attendee details with custom fields, single/multi-select questions, and reusable event templates β€” see Custom Properties
  • πŸ”” Attendee Communication & Webhooks: Keep attendees informed with templated emails, in-app notifications, and outgoing webhooks to sync with external tools β€” see In-App Notifications, Webhooks, and Email SMTP
  • πŸ“‡ Consensual Contact Sharing: Help attendees network responsibly with explicit, opt-in contact sharing that attendees can revoke at any time β€” see Ticketing & Check-In
  • 🎟️ Flexible Paid & Free Ticketing: Create multiple ticket tiers, early-bird pricing, group rates, and shared capacity pools. Draft, clone, and preview your ticket catalog before publishing β€” see Ticketing & Check-In
  • πŸ’³ Direct Payouts & Automated Financials: Sell tickets with complete peace of mind. Connect your Stripe account to receive direct payouts into your bank account with no platform intermediary holding your funds. The platform handles all attendee transactions, receipts, fee calculations, and automated refund management β€” see Paid Events & Payouts
  • πŸ“¬ Audience Growth: Automatically sync registered attendees into your mailing list or newsletter (such as Listmonk) to build lasting community engagement
  • πŸ€– AI Event Co-Pilot: Draft compelling event descriptions, generate relevant tags, and refine schedules using AI suggestions that you review and approve before publishing
  • 🌍 Broader Reach via Federation: Publish once to broadcast your events across participating federated platforms, with optional support for owning your event data directly on your personal data server (PDS via AT Protocol & Bluesky Jetstream)

Platform Owners & Self-Hosters

  • πŸ†“ 100% Free & Open Source: No feature paywalls, telemetry traps, or enterprise tiers. Licensed under AGPL-3.0-or-later
  • πŸ›‘οΈ Absolute Data Sovereignty: Self-host on your own infrastructure (Docker, Coolify, Aspire, On-Prem) with total control over user and attendee data β€” see Self-Hosting Overview
  • 🐳 Flexible Deployment Topologies: Deploy as a single lightweight container (Docker Standalone) with embedded SQLite, a split Docker Compose topology, or across Deployment Tiers
  • πŸ’Ό Multi-Tenancy: Run as a dedicated single-tenant instance or a multi-tenant platform with isolated domains and branding at runtime without code changes β€” see Multi-Tenancy
  • πŸ› οΈ White-Label Control: Fully customizable branding, domains, logos, navigation links, and policies per tenant β€” see White-Labeling & Branding
  • πŸ’³ Zero-Custody Payments & Legal Protection: Stripe Connect handles all payment processing, compliance, and payouts directly between attendees and organizers. The legal transaction is strictly between attendee and organizerβ€”the operator never touches card data (zero PCI liability) nor holds attendee funds. Operators simply supply platform legal terms (Terms of Service, privacy policy) and can disable paid ticketing entirely at any time β€” see Paid Events & Payouts
  • πŸ”§ Admin Hierarchy: Instance admins, tenant admins, and organization admins with cascading settings β€” see Admin Hierarchy and Admin Guide
  • πŸ›‘οΈ Built-in Moderation & Verification: Moderation queues, organizer verification workflows, and structured appeal paths β€” see Coop & Osprey Moderation and Authorization
  • πŸ”Œ Model Context Protocol (MCP) Server: Built-in MCP adapter at /mcp enabling AI agents and IDEs to discover public events and propose actions through authorized confirmation flows β€” see Model Context Protocol (MCP)
  • 🧠 AI-Ready Foundation: Provider-neutral AI assistant, RAG ingestion contracts, and proposal-first tooling wired through the same authorization and HAL affordance layer as the rest of the platform
  • 🌍 Decentralization & Federation: Optional event federation across remote platforms and AT-Protocol authentication for user-owned identities β€” see AT Protocol & Bluesky Jetstream
  • πŸ—„οΈ Privacy Erasure Authority: GDPR-compliant user data erasure with choice of topology: co-located inside the main database, an isolated external PostgreSQL instance, or embedded SQLite β€” see Privacy Erasure & Anti-Resurrection
  • πŸ“¬ Mailing List Integration (Listmonk): Connect a self-hosted Listmonk instance to sync attendee registrations, with independent privacy-erasure authority per tenant
  • πŸ“š Comprehensive Docs: Official hosted documentation alongside in-repository specifications covering architecture, deployment, configuration, and APIs
  • πŸ” Enterprise Security: BFF architecture, local or Cerbos authorization, environment-first secrets (optional Infisical), and HATEOAS REST API β€” see Authentication, Authorization, and Secrets Management
  • πŸ“œ Declarative Configuration Manifests & Portability: Automated Day 0 bootstrap and Day 2 configuration portability via schema-validated JSON manifests with dry-run validation, preview diffs, and rollback β€” see Configuration Manifests
  • πŸŽ›οΈ Multi-Instance & Fleet Orchestration Ready: Complete programmatic control via management APIs (/api/management/*) and integration readiness for the upcoming ISLAMU Event Control Plane fleet orchestrator

πŸš€ Deployment & Hosting Options

ISLAMU Event is architected for sovereign self-hosting across diverse hardware requirements and scales:

Topology Mode Target Use Case Step-by-Step Documentation
Tier 1: Standalone / Masjid Single container with embedded SQLite; ideal for 1 vCPU / 2 GB RAM servers. πŸ“– Docker Standalone Runbook
Tier 2: Production Multi-Service Split High-reliability split topology: API, Blazor UI, PostgreSQL, Keycloak, and Redis. πŸ“– Docker Compose Runbook
PaaS Deployment (Coolify) Self-hosted PaaS deployment behind Traefik with an external Cerbos PDP container. πŸ“– Coolify with Cerbos & Traefik
Developer Orchestration Local development and cloud-native adaptation via .NET Aspire AppHost. πŸ“– .NET Aspire & Cloud

For hardware sizing recommendations, reference architecture blueprints, and capacity planning, consult the Deployment Tiers & Sizing Guide and the master Environment Variables Reference.


🎨 Branding & Customization

ISLAMU Event is built from the ground up for sovereign white-label community use:

  • Instance Name & Domain: Configure custom instance naming, base URLs, and preferred hosts.
  • Logos, Favicons & UI Themes: Customize brand primary/secondary colors and typography β€” see White-Labeling & Branding.
  • Custom Vanity Domains: Map external domains to specific tenants with automatic TLS and routing β€” see Custom Domains & SEO.
  • Administrative Governance: Manage organizations, verification badges, and event categories β€” see Administration Guide.

πŸ›‘οΈ Enterprise Security & Compliance

Security and privacy fail closed at every layer:

  • πŸ” Authentication: OAuth 2.0 / OIDC user authentication powered by Keycloak β€” see Keycloak Authentication.
  • πŸ›‘οΈ Authorization: Fine-grained policy evaluation with runtime switching between Local RBAC and Cerbos PDP β€” see Authorization Architecture.
  • 🏒 Multi-Tenancy: Fail-closed ambient query filters guaranteeing zero cross-tenant data leakage β€” see Multi-Tenancy Architecture.
  • πŸ—„οΈ Privacy Erasure & GDPR: Anti-resurrection tombstones preventing erased users from being restored from stale backups β€” see Privacy Erasure Authority.
  • πŸ—οΈ Secrets Management: Centralized secret delivery via Environment or Infisical β€” see Secrets Management.

Roadmap

The roadmap is tracked publicly in the Roadmap Kanban View. Use it to follow planned work, vote, and comment:

Roadmap Kanban View


🀝 Contributing

There are many ways you can contribute to ISLAMU Event:

Non-Technical:

Technical:

  • πŸ’» Fix bugs & implement features
  • πŸ§ͺ Author invariant-breaker test suites
  • πŸ“Š Profile & optimize EF Core queries
  • 🎨 Enhance Blazor WebAssembly UI components

Quick Start (For Developers & Contributors)

For local development and code contribution, launch the .NET Aspire developer loop:

git clone https://github.com/islamu-ngo/Event.git
cd Event
cp .env.example .env
curl -sSL https://aspire.dev/install.sh | bash # only needed when aspire CLI is not installed
aspire run --apphost Explore.AppHost/Explore.AppHost.csproj

This automatically orchestrates PostgreSQL, Keycloak, Mailpit, Explore.API, Explore.Blazor, and the Aspire dashboard (http://localhost:18888).

For Docker-only local development:

cp .env.example .env
docker compose config
docker compose up -d postgres redis keycloak-db keycloak islamu-event-api islamu-event-ui

Bundled Keycloak starts without importing the repository sample realm. Use the setup-time operator panel to inspect and explicitly create absent realm/client resources.

Contributor Onboarding Path

  1. Review our Contribution Guidelines and Local Getting Started.
  2. Read the Developer Guide for the 5-minute mental model and coding patterns.
  3. Check the authoritative Quick Reference (Invariants), Clean Architecture Invariants, and Governance Standards.
  4. AI-assisted coding agents must strictly follow AGENTS.md and .agents/contract/intents.yaml.

✍️ Contributor License Agreement & Community Protection

All non-bot contributors must sign the ISLAMU Contributor License Agreement before a pull request can be merged. Signing is handled automatically directly in your PR with a simple comment replyβ€”see legal/CLA.md for full terms.

πŸ›‘οΈ Why We Have a CLA & Why You Can Trust It:

  • Community-First Invariant: Contributors retain ownership of their contributions. The CLA grants ISLAMU inbound rights so the non-profit can offer alternative licensing for enterprise compliance on private internal networks.
  • The Anti-SaaS Covenant: ISLAMU is bound by a strict governance commitment never to grant an alternative license permitting a third party to operate a closed-source, proprietary SaaS or cloud service.
  • Universal Parity: Any company offering ISLAMU Event as a public SaaS must do so under AGPL-3.0-or-later, guaranteeing that all SaaS improvements are shared back with the community. Your contributions will never be locked behind a proprietary vendor wall.

πŸ“š Documentation: Public Guides vs. Internal Specifications

ISLAMU Event maintains a deliberate separation between Public Adopter Documentation (operator/adopter perspective on GitBook) and Internal Engineering Specifications (developer/contributor perspective in GitHub Markdown):

🌐 1. Public Operator & Adopter Documentation (GitBook)

πŸ“– Official Hosted Portal: Visit https://islamu.gitbook.io/islamu-event for our complete public guides:


πŸ› οΈ 2. Internal Engineering Specifications (For Developers & Contributors)

For developers contributing code, architecture reviewers, and AI agents, use the authoritative in-repository specifications in docs/internal/:

Engineering Concern Authoritative In-Repository Markdown File What You Will Learn
Developer Mental Model docs/internal/DEVELOPER_GUIDE.md 5-minute onboarding, project structure, and local dev loop.
Global Project Invariants docs/internal/QUICK_REFERENCE.md Single source of truth for architectural constraints and forbidden patterns.
Clean Architecture docs/internal/ARCHITECTURE.md Domain $\to$ Application $\to$ Persistence/Infrastructure $\to$ API boundaries.
System Architecture Diagrams docs/internal/ARCHITECTURE_OVERVIEW.md C4 container diagrams, component relationships, and data flows.
Coding Patterns & Conventions docs/internal/GOVERNANCE.md Native CQS slice patterns, manual validator instantiation, and HAL affordances.
Testing Strategy docs/internal/TESTING.md TUnit conventions, test slicing (--treenode-filter), and Testcontainers lanes.
Operations & Build Verification docs/internal/OPERATIONS.md Verification policies, release gating, and build commands.
REST & HAL API Contracts docs/internal/API.md & API_COOKBOOK.md Endpoint contracts, ProblemDetails error formats, and curl examples.
Blazor WebAssembly Frontend docs/internal/BLAZOR.md & BLAZOR_DEV_WORKFLOW.md MudBlazor UI conventions, BFF session cookie proxying, and CSS isolation.
Security & Threat Model docs/internal/SECURITY-MODEL.md Fail-closed auth boundaries, token handling, and multi-tenant isolation.
Self-Hosting Technical Specs docs/internal/SELF_HOSTING.md Low-level container wiring, ports, volume configurations, and profiles.
AI Agent Contribution Contract AGENTS.md & .agents/contract/intents.yaml Contribution contract, task intents, and strict agent execution guardrails.
Full Internal Specs Index docs/internal/index.md Master sitemap cataloging all 140+ internal technical specifications.

πŸ—οΈ Technology Stack

Layer Technology
Runtime .NET 10
Architecture Clean Architecture, native CQS, Riok.Mapperly
UI Blazor WebAssembly, MudBlazor
API ASP.NET Core, REST/HAL, OpenAPI, Swagger, Scalar
Data PostgreSQL, SQLite, EF Core
Auth Keycloak OIDC/OAuth2
Authorization Cerbos PDP or local database-backed provider
Secrets Environment variables and Infisical provider abstraction
Observability Serilog, OpenTelemetry
Deployment Docker Compose, Docker Standalone, .NET Aspire
Tests TUnit, bUnit, integration and architecture tests

Community

Join the ISLAMU community on Discord and our GitHub Discussions. We follow a Code of Conduct in all our community channels.

Feel free to ask questions, report bugs, participate in discussions, share ideas, request features, or showcase. We would love to hear from you.

Give us a Star ⭐️

πŸ›‘οΈ Security Disclosure

If you discover a security vulnerability in ISLAMU Event, please report it responsibly instead of opening a public issue. We take all legitimate reports seriously and will investigate them promptly. See the Security Policy for more info.

To disclose any security issues, please email us at contact@openislamu.org.

Security fixes from forks

If you maintain a fork of ISLAMU Event and discover or fix a security vulnerability, please report it privately first using the process in our Security Policy instead of opening a public issue or public pull request before coordination.

We are grateful for security fixes from forks. To merge an exact patch into the official ISLAMU Event repository, every non-bot contributor must sign the ISLAMU Contributor License Agreement. This keeps the official codebase compatible with both the public AGPL-3.0-or-later release and ISLAMU’s alternative licensing path.

If you cannot or do not want to sign the CLA, you can still help by privately sharing the vulnerability details, affected versions, reproduction steps, and the general remediation approach. The ISLAMU maintainers may then implement an independent fix.

Contributors

Core Maintainer

Amir Akrari
Amir Akrari

I am deeply grateful to all our amazing contributors.

Contributors Image

πŸ’– Sponsors

Support ISLAMU Event's ongoing development, infrastructure, and open-source mission by becoming a financial sponsor.

ℹ️ Recognition Policy: Active tiers display ongoing monthly recurring sponsors. One-time contributions and sponsors who have stopped their monthly support are recognized under Old Sponsors.

πŸ₯‡ Gold Sponsors

No active Gold sponsors yet.

Old Sponsors

πŸ₯ˆ Silver Sponsors

No active Silver sponsors yet.

Old Sponsors

πŸ₯‰ Bronze Sponsors

No active Bronze sponsors yet.

Old Sponsors

β˜• Community Sponsors

No active Community sponsors yet.

Old Sponsors

πŸ’Ό To discuss corporate sponsorship, custom invoicing, or enterprise partnerships, email us at contact@openislamu.org.

🀝 In-Kind Supporters

Special thanks to the organizations providing free tooling, infrastructure, and licenses to support ISLAMU Event's open-source development:

Organization Contribution & Usage
GitBook logo GitBook Generously provides their Community Plan to host and power our Official Public Documentation.
Gitar logo Sonar Gitar Generously provides their Gitar Open Source Program to empower our development with AI code review: β€œGitar keeps going β€” committing fixes, diagnosing CI failures, and iterating until your pipeline is green and the PR is ready to merge.”

If your organization would like to support ISLAMU Event with in-kind tooling, infrastructure, or software licenses, please reach out to us at contact@openislamu.org.

🧰 Public-Repository Tools

We appreciate these generally available public-repository tools. They are not project-specific sponsorships.

ISLAMU Solutions

  • ISLAMU Event: Event Platform & Management System.
  • I-VSD: Islamic Value Sensitive Design: A Framework for Provider-Mediated Software Solutions

πŸ™ Acknowledgement

  • Keycloak: An Open Source Identity and Access Management Provider.
  • Cerbos: An Open Source Policy Decision Point.
  • Infisical: An Open Source Secret Management Platform.
  • MudBlazor: An Open Source Blazor UI library that simplifies the creation of beautiful websites and webapps.
  • ROOST Coop: An Open Source Review and Moderation Platform.
  • ROOST Osprey: An Open Source Investigation and Rules Engine.
  • Svix: An Open Source Webhooks Service.
  • Penpot: An Open Source Design Tool.
  • Plane: An Open Source Project Management Platform that unifies projects, knowledge and agents with all-in-one workspace: projects, wiki, and AI.
  • Coolify: An Open Source Platform as a Service, alternative to Vercel, Heroku, Netlify, and Railway for easy deploying to your own servers.
  • Weblate: An Open Source Translation Management Platform.
  • Kener: An Open Source Status Page.
  • SQLite: The database used by the standalone deployment.
  • PostgreSQL: An optional database for larger deployments.
  • Redis: Optional distributed caching.
  • RabbitMQ: Optional messaging for email dispatch.
  • MinIO: Optional S3-compatible object storage.
  • Formbricks: Optional surveys and feedback collection.

Open-Source Libraries & Dependencies

Our codebase is enriched by dozens of community-crafted .NET libraries. For the complete, centrally managed dependency list and version pins, see Directory.Packages.props.

A heartfelt thank you to every open-source author and maintainer whose work (direct or transitive) helps make this project possible.

Inspiration (UI/...)

  • Luma: A Modern Event Management & Discovery Platform
  • Smoke Signals: An Event & RSVP Management and Discovery Web Application built on top of ATProtocol.
  • Mangadex: A Manga Discovery Platform with advanced filtering and multi-language support.
  • Plane: An Open Source Project Management Platform that unifies projects, knowledge and agents with all-in-one workspace: projects, wiki, and AI.
  • Hi.Events: An Open Source Event Ticketing and Management Platform

🌱 Sustainability

ISLAMU is built by one person β€” Amir Akrari β€” entirely on personal free time and personal funds.

ISLAMU (ASBL en formation) (Association Sans But Lucratif β€” a non-profit association in formation in Belgium) is being established as the operational and legal steward of all ISLAMU open-source projects and charitable activities. Once formally registered with legal personality, ISLAMU ASBL will assume full legal stewardship.

How ISLAMU sustains itself

ISLAMU will not offer its open-source software as a hosted SaaS. Instead, sustainability is built on:

  • Fundraising & Grants: Crowdfunding campaigns, foundation grants, and public-interest funding for open-source digital infrastructure
  • Sponsorships: Ranked sponsorship tiers β€” sponsors receive recognition and visibility; every euro goes back into the non-profit
  • Official Partnerships & Fleet Tooling: Organizations that want to offer ISLAMU software as a hosted service can become Official ISLAMU Partners. Partners are vetted, listed on the ISLAMU website, and actively recommended and marketed by ISLAMU. Official Partners receive access to ISLAMU Event Control Plane (our standalone fleet orchestrator that bridges multiple ISLAMU Event instances with PaaS engines like Coolify for automated provisioning, SLA management, and backups). ISLAMU does not compete with its partners by running a commercial SaaS; we empower our partners with tooling and referrals
  • Consultation & Support β€” professional consulting around ISLAMU software deployment, customization, and integration

If you are a company or institution that wants to support this work, reach out at contact@openislamu.org or start a conversation in our Discord.

πŸ“ž Contact

For any question or problem reporting, please consider opening a new issue or send an email to contact@openislamu.org or create a new post in our Discord Server.

Privacy Policy

You can find details here.

πŸ“„ License & Ecosystem Architecture

This project is licensed under the terms of GNU AGPL-3.0-or-later.

🌐 The Three-Pillar Ecosystem

ISLAMU Event operates on a transparent three-pillar model designed for universal community parity and sustainable open-source governance:

  1. Community Commons (AGPL-3.0-or-later): 100% Free & Open Source for everyone. Any organization or hoster can run a SaaS or self-host under AGPLv3. All SaaS modifications must be published openly, ensuring complete community parity.
  2. Enterprise Internal-Use License (Anti-SaaS): For enterprises whose internal compliance policies ban AGPL copyleft on private internal infrastructure. This license waives Section 13 network copyleft for private on-premises/VPC deployments and internal corporate events, while strictly forbidding external SaaS or commercial cloud hosting. Paid for commercial corporations (funding security audits and maintainers); gratis ($0) for verified non-profits and educational institutions.
  3. Official Partner Program: For certified agencies, hosters, and integrators. Partners operate on the exact same 100% AGPLv3 codebase (no proprietary code privilege). Commercial value is generated through quality certification, trust branding, and official directory listings.

For the full ethical and strategic design analysis, see the I-VSD Strategy Review.

Standalone Core And Optional Services

The minimum operational deployment is the single Event.Standalone image: the ISLAMU Event API and Blazor BFF/UI run in one process with SQLite persistence. Application, Data Protection, and embedded privacy-erasure migrations run in that process before it accepts traffic. PostgreSQL, SQL Server, MariaDB, MySQL, Redis, Keycloak, Cerbos, MinIO/S3, SMTP/Mailpit, Svix, Weblate, Formbricks, Coop, Osprey, AI providers, federation services, and external observability backends are optional capabilities, not requirements of the standalone core.

The AGPL-3.0-or-later license and any alternative license offered by ISLAMU apply only to material that ISLAMU owns or is authorized to license. Third-party libraries, container images, services, datasets, fonts, and other assets retain their respective licenses, public-domain status, and other applicable terms. Including an optional integration or deployment manifest in this repository does not relicense that third-party material. See the Self-Hosting Technical Specs and release dependency policy.