Self-hostable, open-source event discovery and management software for communities, organizations, and platform operators.
ISLAMU Event powers ISLAMU’s Islamic events instance, but the software itself is purpose-agnostic, white-label, and designed to be rebranded for any event ecosystem.
Pre-1.0 notice: ISLAMU Event is still before v1. Breaking changes may happen between releases. We avoid data-loss-class breaks where possible, but configuration changes may be required.
ISLAMU Islamic Events Instance · Quick Start · Docs · Roadmap
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 and designed to be rebranded for any event ecosystem.
It is built as a white-label platform engine: the hosted ISLAMU instance focuses on Islamic events, while the software is purpose-agnostic and designed to be rebranded for any event ecosystem.
- 🔍 Advanced Discovery: Event search with title, dates, location, categories, tags, and paging filters
- 👨👩👧👦 Cultural Intelligence: Culturally-Aware Filters for Age ranges, gender segregation modes, madhab targeting, prayer-relative timing (for instances that enable these modules)
- 🌐 Multi-Language Support: Event sessions with multiple language options
- 📱 PWA & Responsive Design: Mobile-friendly Blazor UI with MudBlazor components
- ✅ RSVP & Registration: Waitlists, approval workflows, registration limits per session
- 📅 Signle & Multi-Session Events: Conferences, seminars, recurring programs with speakers, agendas, and language variants
- 📊 Flexible Publishing: Manage registrations, waitlists, approval workflows, capacity limits, and event visibility.
- 👥 Member Management: Invite members, assign roles (Owner, Admin, Editor, Viewer), track permissions
- 🎯 Modular Event Types: Data Modeling: custom fields, event aspects, event templates...
- 🐳 Deployment: Docker ready
- 💼 Multi-Tenancy: Switch between single-tenant and SaaS modes at runtime without code changes
- 🛠️ White-Label Control: Custom branding, domains, logos, navigation links, policies per tenant
- 🔧 Admin Hierarchy: Instance admins, tenant admins, and organization admins with cascading settings
- 🌍 Federation Foundation: ATProto-oriented models and outbound sync plumbing exist, while public ActivityPub and ATProto server endpoints remain roadmap work
- 📚 Comprehensive Docs: Architecture, deployment, configuration, troubleshooting, and API reference
- 🔐 Enterprise Security: BFF pattern, Cerbos authorization, Infisical secrets, HATEOAS REST API
This platform is designed to be flexible and self-hostable for any organization.
- Single-Instance Mode: One organization or community per deployment
- Multi-Tenant SaaS Mode: Multiple isolated tenants with custom domains and branding
See Operations Guide for full deployment details and examples.
ISLAMU Event is built for white-label use:
- Change instance name and domain
- Customize logos, colors, and UI
- Define your own categories, tags, and policies
- Decide who can publish events and how verification works
See Configuration Guide for full customization options.
We treat security as a first-class citizen, not an afterthought.
- 🔐 Authentication: OAuth 2.0/OIDC via Keycloak
- 🛡️ Authorization: Runtime provider switching via system setting (Cerbos PDP or local DB-backed provider), with optional tenant BYO Cerbos
- Tenant Isolation: API-authoritative tenant resolution with EF Core global query filters for tenant-scoped data
- 🔍 Input Validation: FluentValidation + ASP.NET Core model binding
- 🚫 Data Integrity: Parameterized EF Core queries to eliminate SQL injection
- 🗝️ Secret Management: Environment-first secret loading with optional Infisical compatibility
- Observability: OpenTelemetry + structured logging with Serilog
- 🔒 HTTPS Hardening: HTTPS redirection and production HSTS support
- 🌐 CORS: Configurable origin whitelist
- ⏱️ Rate Limiting: ASP.NET Core middleware
ISLAMU Event is used by:
Using ISLAMU Event and want to add your project/organization to this list? Open a pull request!
The roadmap is tracked publicly in the Roadmap Kanban View. Use it to follow planned work, vote, comment,
There are many ways you can contribute to ISLAMU Event:
Non-Technical:
- 🐛 Report bugs
- 💡 Suggest features
- 📖 Improve documentation
- 🌐 Translate UI/docs
- 📣 Spread the word
Technical:
- 💻 Fix bugs
- ✨ Implement features
- 🧪 Write tests
- 📊 Improve performance
- 🎨 Enhance UI/UX
Start with Contributing. Code contributors should also read Governance, Quick Reference, and Architecture.
AI-assisted contributors should follow AGENTS.md.
Please read Contribution Guidelines for details on the process for submitting pull requests to us.
Before your pull request can be reviewed or merged, every non-bot contributor must sign the ISLAMU Contributor License Agreement. Signing is done in-PR: a bot posts instructions when the PR opens, and you reply with the exact sign phrase. The signature is recorded in signatures/v1/cla.json together with your GitHub username, user ID, pull request number, signing comment ID, and timestamp. See the CLA document for the current version and the full legal text.
The README is the entrypoint for new readers. docs/index.md is the full documentation map once you know the area you need.
| Reader | Best first page | Use when |
|---|---|---|
| Evaluator | Project, Architecture, Security Model | You want product scope, status, and architecture context. |
| Local developer | Getting Started, Testing, Troubleshooting | You want to build, run, and validate the app locally. |
| Self-hoster/operator | Self-Hosting, Configuration, Operations, Backup/Restore/Upgrade | You want Docker Compose, infrastructure, secrets, health checks, and upgrades. |
| Contributor | First Contribution, Contributing, Quick Reference | You want the shortest safe path to a docs-only or small-bug PR. |
| API integrator | API Cookbook, API Reference, API Changelog | You want task-first API examples before the full API reference. |
| Frontend contributor | Blazor | You want client architecture, render policies, and UI conventions. |
| AI-assisted contributor | AGENTS.md, Contract Intents, Quick Reference | You need the repository contribution contract and required context-loading rules. |
For the complete documentation inventory, use docs/index.md. If a page gives task steps and another page gives exact keys/contracts, treat the task page as the workflow and the reference page as the source of truth.
| Layer | Technology |
|---|---|
| Runtime | .NET 10 |
| Architecture | Clean Architecture, CQRS, MediatR |
| UI | Blazor, MudBlazor |
| API | ASP.NET Core, REST/HAL, OpenAPI, Swagger, Scalar |
| Data | PostgreSQL, EF Core |
| Auth | Keycloak OIDC/OAuth2 |
| Authorization | Cerbos or local provider |
| Secrets | Environment variables and Infisical-compatible provider abstraction |
| Observability | Serilog, OpenTelemetry |
| Deployment | Docker Compose, .NET Aspire for development |
| Tests | TUnit, bUnit, integration and architecture tests |
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 ⭐️
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.
| Amir Akrari |
|---|
 |
  |
I am deeply grateful to all our amazing contributors.
- Keycloak: An Open Source Identity and Access Management Provider.
- Cerbos: An Open Source Policy Decision Point.
- Svix: An Open Source Webhooks Service.
- Infisical: An Open Source Secret Management Platform.
- MudBlazor: An Open Source Blazor UI library that simplifies the creation of beautiful websites and webapps.
- 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.
- Kener: An Open Source Status Page.
- 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.
- ISLAMU Event: Event Platform & Management System.
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.
You can find details here.
This project is licensed under the terms of GNU AGPL v3.
ISLAMU Event inbound contributions are governed by the ISLAMU Contributor License Agreement (CLA). Every non-bot contributor must sign the CLA before a pull request can be merged.
Why a CLA alongside AGPL v3? ISLAMU Event itself remains AGPL v3 — that license does not change. The CLA gives ISLAMU nonprofit (and the ISLAMU Event maintainer of record, Amir Akrari) the ability to also offer ISLAMU Event under alternative terms for organizations and deployers that cannot use AGPL v3 due to compliance, procurement, or sector-specific licensing constraints. The goal is to remove adoption barriers so ISLAMU Event can reach any audience — humanitarian, public-sector, nonprofit, or enterprise — without forcing adopters to accept terms they are not permitted to use.
The CLA is versioned. The current version and full legal text live in docs/legal/CLA.md. Signed contributor records (who, when, CLA version, pull request, comment) are stored in signatures/v1/cla.json on the develop branch and are committed automatically by the CLA workflow.
