> For the complete documentation index, see [llms.txt](https://islamu.gitbook.io/islamu-event/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://islamu.gitbook.io/islamu-event/documentation/readme/getting-started/why-islamu-event.md). # Why ISLAMU Event? Evaluate the platform’s purpose, scope, maturity, and operating model. ISLAMU Event is a self-hostable event platform for communities and organizations that need explicit control over deployment, durable data, identity, authorization, payments, admission, moderation, and federation. *** ## What the Platform Brings Together The product covers public event discovery, organizer administration, [registration and waitlists](/islamu-event/documentation/readme/events-and-ticketing/ticketing-and-check-in.md), [modular event aspects](/islamu-event/documentation/readme/events-and-ticketing/modular-event-aspects.md), [organizer-direct payments and refunds](/islamu-event/documentation/readme/events-and-ticketing/paid-events-and-payouts.md), [durable email notifications](/islamu-event/documentation/readme/communications-and-notifications/email-smtp.md), [outgoing webhooks](/islamu-event/documentation/readme/integrations-and-ai/webhooks.md), [custom registration forms](/islamu-event/documentation/readme/events-and-ticketing/custom-properties.md), [Model Context Protocol (MCP)](/islamu-event/documentation/readme/integrations-and-ai/mcp.md), [local or S3 storage](/islamu-event/documentation/readme/integrations-and-ai/storage.md), and selective [AT Protocol federation](/islamu-event/documentation/readme/federation-and-open-protocols/at-protocol-and-bluesky-jetstream.md). These capabilities remain strictly bounded: * Enabling an integration does not silently grant it identity, authorization, payment, or moderation authority. * Browser returns are not payment truth (see [Paid Events & Payouts](/islamu-event/documentation/readme/events-and-ticketing/paid-events-and-payouts.md)). * Realtime transports are not notification truth. * External moderation signals (such as [Coop & Osprey](/islamu-event/documentation/readme/integrations-and-ai/coop-and-osprey.md)) do not replace local administrative decisions. *** ## Core Architectural Principles * **Deployment Control:** Choose the documented [Docker Standalone](/islamu-event/documentation/readme/self-hosting/docker-standalone.md) or [Docker Compose](/islamu-event/documentation/readme/self-hosting/docker-compose.md) topology and own your infrastructure. * **Fail-Closed Authority:** [Keycloak Authentication](/islamu-event/documentation/readme/security-and-identity/authentication.md), the selected [Authorization Provider](/islamu-event/documentation/readme/security-and-identity/authorization.md), tenant resolution, and [Secret Providers](/islamu-event/documentation/readme/configuration-and-operations/secrets.md) do not silently fall back to weaker paths. * **Durable Workflows:** Transactional outboxes and idempotent intake protect external effects such as email, webhooks, payments, and federation. * **Discoverable Permissions:** [HAL links](/islamu-event/documentation/readme/security-and-identity/authorization.md#the-golden-rule-of-client-ui-affordances) tell clients which actions are currently allowed for a resource. * **Explicit Limits:** Unsupported deployment modes, protocol surfaces, and provider responsibilities are documented rather than implied. *** ## Maturity & Operational Responsibility ISLAMU Event is in active pre-release development with no official release yet. We are actively squashing bugs and preparing for our initial release. Breaking changes happen freely during this pre-release phase to refine the architecture. Published releases, pre-built container images, and stable upgrade paths will begin with our first release. Self-hosting transfers operational responsibility to the operator. You must assess TLS, DNS, identity-provider hardening, authorization policy, secrets, backups, incident response, retention, data residency, accessibility, and provider agreements for your deployment. Product documentation describes implemented behavior; it is not a compliance, security, accessibility, or religious certification. *** ## Related Guides & Next Steps * [**5-Minute Quickstart**](/islamu-event/documentation/readme/getting-started/5-minute-quickstart.md) — Spin up an evaluation instance locally using Docker. * [**Architecture & Request Flows**](/islamu-event/documentation/readme/getting-started/architecture-and-request-flows.md) — Trace HTTP requests from the browser-facing service through authorized operations to storage. * [**Deployment Tiers & Sizing**](/islamu-event/documentation/readme/self-hosting/deployment-tiers.md) — Review hardware requirements and deployment topologies. * [**Clean-Room IP & Licensing**](/islamu-event/documentation/readme/contributing/clean-room-ip-and-licensing.md) — Understand our open-source IP stewardship and governance. --- # Agent Instructions This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com. ## Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter: ``` GET https://islamu.gitbook.io/islamu-event/documentation/readme/getting-started/why-islamu-event.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.