FaithOps | Church and Mosque Management Flutter Member App With Laravel Script

The system a congregation actually runs on

The Faith Ops is a system of record, not a brochure site. Members, households, attendance, groups, ministries, serving schedules, giving, events, sermons, prayer requests, pastoral care and certificates live in one Laravel admin, with a multi-tenant platform panel above it so a single deployment serves many congregations.

It is built church first. It also ships the masjid as a first-class citizen rather than an afterthought, which no other congregation system on this marketplace does: a parish gets the liturgical calendar, the missal and reading plans, a mosque gets prayer times, qibla, the Hijri calendar and zakat. Each congregation sees only its own tradition, chosen from a settings screen, and an interfaith organization can enable both.

What you get

• A Laravel backend. A custom organization admin for the church office, a platform panel for whoever runs the deployment, and a documented REST API that the mobile app consumes.
• People and attendance. Members, households, groups, ministries, leadership and serving schedules, with attendance per gathering, pastoral care notes, and baptism and marriage certificates.
• Giving that reconciles. One-off and recurring gifts through the congregation’s own payment provider, with funds, appeals, year-end statements and Gift Aid.
• A public site per congregation with service times, sermons, events, giving and editable privacy, terms and giving policies. Pages are edited from the admin, so there is no second CMS to run.
• A Flutter member app, included in the download. Announcements, giving, events, scripture and the complete Qur’an readable offline, prayer times computed on the device, qibla, tasbih and a share-card composer.
• Two faiths, cleanly separated. One deployment-wide switch decides whether the platform serves both traditions or only one, and every screen, search result and API route follows it.
• A grounded AI assistant. Answers are drawn from the organization’s own library passages with citations, and it is provider-neutral, so the buyer chooses the model.
• Live streaming and a sermon library, with per-organization channels and an announcement slot the congregation controls.
• A web installer. Requirements check, database, license, administrator, done. No file editing and no terminal.

The member app

Every congregation gets its own site

See every screen.

Live demo

Demo: https://faithops.foundrcode.com

• Church admin: pastor@cornerstone-atlanta.faithops.app / password
• Mosque admin: imam@manchester-central-masjid.faithops.app / password
• Platform admin: platform@faithops.app / password

The Android build of the member app is on the demo landing page under Get the app.

Requirements

• PHP 8.3 or newer, MySQL or MariaDB, and Composer.
• Shared hosting is enough. The installer checks every extension it needs and tells you what is missing before it writes anything.
• Flutter on the current stable channel, only if you want to build the member app. The backend, the admin and the public sites run without it.

Third party services and costs

The platform runs on the bundled demo data with zero third-party accounts. Only the core install is required. Everything below is optional, each is a separate sign-up, and all fees are billed by that provider under your own account and are not included in the item price.

• Payments (Stripe, Paystack, Flutterwave) for real giving. Leave the keys blank and the giving form is not offered.
• Push notifications (Firebase Cloud Messaging) for announcements. Without it, announcements are still recorded and readable in the app.
• Email for sign-up and password-reset codes. Any SMTP server works; an API provider is optional.
• An AI provider for the assistant. The assistant hides itself when no key is present, and every congregation has a monthly answer allowance set by its plan so one of them cannot run up your bill.
• AdMob, if you want to run ads in the app. Your account, across every congregation, switched off until you turn it on.

Scripture, Qur’an and hadith text is imported from free public sources with a bundled command. Nothing about the core product depends on a paid service.

Running it as a service

• Congregations sign themselves up at /register. Choose whether sign-ups are closed, reviewed by you before anything is created, or open. Approving one creates the organization, its owner account and its public website in a single step.
• Plans decide what they get — the member cap, the monthly AI allowance, which faith modules they may switch on, and whether they see ads at all. You create the plans and set every one of those from the panel.
• Congregations pay you by card through your own Stripe account. Paste one secret key and the panel creates the products, the prices and the webhook for you — there is nothing to set up in the Stripe dashboard.
• Full billing, not a placeholder — upgrade and downgrade, invoice history, a grace period on a failed card, and emails for a trial ending, a payment failing and a receipt. Leave Stripe unconfigured and the same screen takes plan requests by email instead.
• Ads and AI are metered per congregation, so you can see which tenant costs what and price accordingly.

Support

Documentation ships in the package as a single HTML file with a sidebar, covering installation, configuration, rebranding, the API and troubleshooting. Every configuration step states what success looks like.