For Catholic parishes
Families, ministries, formation, the Mass schedule, the bulletin list and your website, all running off one record. Built for Catholic parishes, not a church CRM wearing a Catholic hat.
In beta. We are taking a handful of parishes now.
Why we built it
One database for households. Another for religious education. A mail tool nobody has the password to. A website a volunteer built in 2014. A signup sheet in the vestibule. Three people are holding all of it together by re-typing the same family into four places, and every one of those places disagrees with the others.
The record underneath
Parishes think in families, so the record does too. Open one household and you have got everybody in it, what they give, what they serve in, what sacraments are on file and what the staff need to remember about them. The grandmother living upstairs is a member of the family, not a duplicate contact you clean up later.
Every parishioner has their own record: what they have given, which ministries they lead or serve in, which sacraments are on file, what formation they have completed, and every change anyone has made.
A background scan compares names, addresses and households and pulls out the pairs worth a second look. Then AI reads each pair and tells you what it is actually seeing: same street, a married name, a transposed birthday, a nickname nobody standardized. It scores how confident it is and recommends merge, keep separate, or take a closer look.
A person still makes the call, and the merge is a real merge rather than a delete. Twenty years of imports stop compounding, and the list stays clean enough that your staff actually trust it.
Heartbeat
Be honest: nobody knows how many of those families still live in the state. People move, marry, bury a parent and drift, and none of it reaches the office. So the list rots, quietly, until the staff stop trusting it and go back to the one they keep in a drawer.
Heartbeat ends that in three steps, and not one of them is a phone tree.
Watch the answers land live, then call the eleven people who never replied instead of all six hundred. Every record gets stamped with the day you last heard from them, so next spring you run it again and your roster never drifts for long.
What it does
Register a family once and they are already in formation, on the roster, on the mailing list and in the directory. No CSV, no import wizard, no Tuesday afternoon spent reconciling two systems that were supposed to talk to each other.
Households, not contacts. Sacramental records, relationships that cross households, and AI-assisted duplicate detection with a real merge.
Two-level groups with leaders and co-leaders, rosters, prerequisites, and join requests that route to the right person.
Programs, sessions, catechists, enrollment and attendance. OCIA, sacramental prep and K-12 in one place.
Mass times, liturgical season, ministry meetings and formation sessions in one view your staff and parishioners both see.
Rooms and grounds with booking requests, automatic conflict checking, and an approval trail.
1 TB per parish. Albums, a picker wired into every editor, and a quota you can actually see.
Registration triage, volunteer roles, substitutions and facility requests, each with who approved what and when.
Demographics, directories, new members. Run it, save it, or schedule it to arrive in your inbox.
Email, SMS and push from one composer, with per-category subscriptions so people can opt out of one thing, not everything.
A full public site on your own domain, edited by staff. Pages, news, sacrament pages, bulletins and Mass times, no developer in the loop.
Build a form, run a stewardship campaign, collect and review responses without a third-party form tool.
Ticketed and paid registration with tiers, capacity and custom questions. Festivals, retreats, men's conferences, and more!
If half your parish worships in Spanish, an English-only app is not worth installing. So the portal, the apps and the public site were built multi-language from the ground up rather than having a translation layer bolted on later. Spanish lands shortly after launch, and the next language after it is not a rewrite.
Coming soon after launchImport your existing giving data at launch and it drives statements, household and parishioner giving screens and every report. Taking the donation in the app comes next.
Coming soon after launchVolunteer records, roles and background-check compliance are here now. Building the schedule, filling shifts and covering substitutions is next.
Coming soon after launchRoll-up reporting for the chancery, diocesan compliance tracking, sacramental reporting and central policy push-down. The multi-parish foundation is already built.
Coming soon after launchBuilt Catholic
Seasons and colors it already knows. Daily readings pulled straight from the lectionary, every morning, without anyone retyping them. Mass, confession and adoration as real service types, not blank "events" your secretary has to name and re-name every single week.
Communications
Send to a ministry, a formation year, the whole parish or one family, then watch it land. Delivered, opened, clicked, unsubscribed, broken out by category. "Did anyone actually read it?" stops being a shrug at the staff meeting.
Per-category subscriptions mean a parishioner can mute volunteer reminders without losing the pastor's letter. Which is the difference between an unsubscribe and a lost parishioner.
For parishioners
A web portal plus iOS and Android. Today's readings, Mass times, their ministries, the directory, event RSVPs, their giving history and a word from the pastor. All the things they used to call the office about, in their pocket.
Parishioners update their own address, register for events, join a ministry, manage what they hear from you, and see their own giving history. Every change lands on the same record the staff sees.
If half your parish worships in Spanish, an English-only app is not worth installing. So the portal, the apps and the public site were built multi-language from the ground up rather than having a translation layer bolted on later. Spanish lands at launch, and the next language after it is not a rewrite.
That is the portal on a phone, not a cut-down version of it. Nothing to install, nothing to update, and the same record the office is looking at. Native iOS and Android apps are available too, for the people who want notifications and a home-screen icon.
Communities
Your choir is on GroupMe. Your youth group is in a Facebook group somebody's cousin admins. Your councils run on reply-all chains that drop half the recipients. None of it belongs to the parish, and when a leader steps down it walks out the door with them.
Every ministry, formation program and volunteer group gets its own channel, with membership drawn from the roster. Join the choir and you are in the choir's space. Leave it and you are out. Nobody maintains an invite list.
A parish-wide channel for the things everybody needs, and staff can pin a post so it stays at the top rather than scrolling away by Tuesday.
Leaders post updates, attach the schedule or the sign-up sheet, and people react and reply. The permission slip lives with the group that needs it instead of in one volunteer's inbox.
The conversation happens on the parish's system, under the parish's moderation, tied to the parish's directory. A leader stepping down hands over a role, not a password.
Your website
Either way you win, because the important part is not who hosts the pages. It is that the buttons on them write straight into the parish record instead of into somebody's email.
Love your website? Keep it. Registration, event sign-ups, forms and the parishioner portal all live at their own links. Drop them into the nav of whatever you already run and nothing else has to change. No migration, no redesign, no arguing with the volunteer who built it.
Your domain, your colors, your photos, and a staff member who can change the Mass times on a Tuesday without filing a ticket. Sacrament pages, faith formation, bulletins, news and the parish directory come built, because we already know what a parish site needs on it.
Here is the part that matters. A family that registers on the site is a household in your database before they reach the parking lot. A contact form lands in a staff inbox, not a Gmail account nobody has checked since 2019. Nothing gets re-typed, because there is nowhere to re-type it to.
Reports
Demographics, directories, new-member reports and ministry participation, built from the live record. Save the ones you run every month, schedule the ones somebody else asks for.
For dioceses
What is already true is the hard part. My Disciples was not built for one parish and then stretched later. Every record carries its parish and isolation is enforced in the data layer rather than screen by screen, so parishes never leak into each other. Standing up a new parish is a provisioning step, not a migration project.
If your diocese needs something in the right-hand column by a date, say so during early access. We will tell you honestly whether we can hit it, which is worth more to you than a yes.
Who we are
Ribb Technologies is a small company started and run by a Catholic couple, both software developers. We offered to help our growing home parish with their software needs, and saw the many struggles they had integrating so many different systems.
Through prayer we discerned that we would use our talents to build not just a parishioner management application, but one that would build stronger communities within our parish and strengthen the Body of Christ.
Ribb Technologies
Questions
Yes. It is your parish's data and export is not a retention lever. Ask us about the specific formats you need before you sign anything.
You take it with you. The written terms covering ownership, export and retention are being finalized and will be linked here before general availability.
You can use it as your website, with your own domain and branding, edited by staff. Mass times and events come straight off the parish calendar, so the site stops going stale. You can also keep the site you have and use everything else.
No. Everything a parishioner can do in the app they can do in a browser. The apps are for the ones who want notifications and a home-screen icon.
Not yet, and we would rather say so than let you find out in month two. The portal, the mobile apps and the public site were built multi-language from the start, so this is a matter of finishing and testing the translations rather than re-architecting anything. Spanish is scheduled for launch. If your parish is majority Spanish-speaking, tell us during early access and we will tell you honestly where it stands.
A Catholic couple who both write software and started by helping their own parish with it. The short version is above. Company details, security posture and compliance documentation will be linked from this page before general availability.
Early access
My Disciples is live, in use, and not finished. That is the offer. We are taking a handful of parishes now, and what those parishes ask for is what gets built next.
Come in later and you get a mature product shaped around somebody else's parish. Come in now and it gets shaped around yours.
