Your ministry, in their pocket.
A custom church app, in your branding, in your App Store account, with the code in your GitHub repo. Built and operated by an LA team for $250/mo per campus. Multi-campus scales linearly, no separate tier. Your staff never designs your app. If the website is the first problem, start with the church website rehost guide.
No build fee · Launch target in writing · Terms in writing
Numbers that actually move when ministries switch.
Pulled from launches across denominations: Christian, Catholic, Jewish, Muslim, Hindu, Buddhist, Sikh communities running their own custom app instead of a templated platform.
38%
Average lift in digital giving within 6 months, across launches with connected giving (Stripe, Tithe.ly, Pushpay).
40-60%
Increase in weekday engagement vs. email and social alone.
2-3 wks
From kickoff to live on the App Store and Google Play.
Sources: Barna Group (digital giving), LifeWay Research (engagement), Rehost portfolio data.
$250 per campus. The math doesn't get more complicated.
One tier, one rate. Three campuses is $750/mo. Five is $1,250/mo. There is no Multi-Campus tier to upgrade to, no per-member fee, no annual renewal cycle, no per-feature unlock.
Faith
A native app under your church's brand, with sermons, giving, push, groups, and tradition-specific features. Multi-campus is simple multiplication.
- One-page agreement
No 50-page legal binder. A short doc that names the work and the cost.
- Terms in writing
Commitment, notice, data exports, account responsibilities, licenses, handoff, and service-end terms follow the signed agreement.
- No surprise invoices
No setup fee, no per-feature unlock, no per-member surcharge. The number on the page is the number on the bill.
Snapchat
TikTok
Netflix
Gmail
X
Maps
More than one campus?
Included in FaithNo multi-campus negotiation. The first campus is $250. The seventh campus is $250. Add or drop a location and the line item adjusts. 3 campuses run $750/mo, 5 run $1,250/mo, 10 run $2,500/mo: same architecture, same support, same app shell.
- One app shell, separate campus entries
Members pick their location on first launch. Each campus gets its own service times, giving funds, sermon library, and group directory.
- Weekly cross-campus summary
Who opened the sermon, which group is growing, where giving is up when your processor is connected, which campus needs a touch. Written out, not buried in a dashboard.
- Sunday-morning on-call
If anything breaks during a service, our on-call engineer is paged within minutes. Worship-day SLAs are the default, not an upgrade.
- Cross-campus reporting
Giving, engagement, attendance, and conversion-from-visitor-to-regular, all rolled up across locations and broken down per campus.
- ChMS / accounting integrations included
Planning Center and QuickBooks, wired up so the data flows without your admin re-entering anything.
The work the app actually does, day to day.
Not a feature checklist. The list of things your members actually open the app for between services.
Sermons that survive a commute
Native player with offline downloads, chapter markers, and resume-where-you-left-off across devices.
Push notifications, not email blasts
Prayer requests, weather closures, sermon-day reminders, segmented by campus, group, or congregation.
Two-tap giving in your processor
Recurring tithes, one-time offerings, designated funds. Money flows through your Stripe / Tithe.ly / Pushpay account, not ours.
Daily devotionals tied to your tradition
Liturgical readings, weekly haftarah, daily Gurbani, daily salah times, pulled from sources your tradition trusts.
Small groups that find each other
Searchable directory, group chat, prayer wall, RSVP. Not a Facebook group your pastor moderates at 11pm.
Calendar wired to your real schedule
Service times, sacrament dates, fasts, retreats, volunteer signups, pulled from the source your church admin already updates.
Engagement, in plain English
Each Monday: who opened the sermon, who tapped giving, which group is growing, what's quietly going stale.
An LA team you can call by name
Headquartered in Downtown LA. Same engineers build, ship, and operate. Sunday-morning issues page our on-call directly.
A side-by-side that makes the rented platforms uncomfortable.
The same line items they'd quote you, with the structural difference that the app and data are in your name from day one.
| Feature |  Rehost | Subsplash / Tithely / Pushpay |
|---|---|---|
| Custom Branded App | 100% Custom | White-label template |
| Sermon Streaming | Native Player | Basic Player |
| Push Notifications | Unlimited | Limited |
| Giving | Stays on your rails | Moves to theirs |
| Daily Devotionals | Included | Not Included |
| Staff Messaging | Included | Paid Add-On |
| Data Ownership | You own your data | Locked in their platform |
| Upfront Cost | $0 | $5,000+ |
Custom Branded App
Sermon Streaming
Push Notifications
Giving
Daily Devotionals
Staff Messaging
Data Ownership
Upfront Cost
A rented app makes a serious message feel cheap.
When members open a templated app and see another church's layout with your logo dropped in, the experience signals "this is rented." Custom changes that, quietly, without anyone naming it.
A native app, not a wrapped webview
React Native, real iOS and Android binaries. Sermons play offline. Push notifications arrive instantly. Members feel the difference between "an app" and "a website pretending to be an app."
The data is yours from day one
Member directory, giving history, push subscribers, prayer requests, all live in databases your ministry owns. We hand off the export the day you ask, no platform-side gating.
A flat fee, not a SaaS staircase
Subsplash, Tithely, and Pushpay charge per-feature, per-member, and per-transaction. We charge per campus, flat, indefinitely. The bill in year five looks like the bill in month one.
The week between Sundays is where the app earns its keep.
Service is one hour. The rest of the week is where most ministries lose the connection. The app's job is to keep that thread alive Monday through Saturday without becoming another notification stream.
A morning rhythm, on your tradition's calendar
Daily readings, devotionals, prayer prompts, fasting reminders, pulled from sources your tradition trusts and surfaced at the hour your members are already on their phones.
No ads, no algorithm, no recommended-for-you
The app shows what your ministry chose to show, nothing else. Members open it because they came to read their devotional, not because a feed pulled them in.
Built for your tradition.
The features change with the tradition. Mass schedules and the liturgical calendar for a parish, the sermon series and next-steps path for an evangelical church, the prayer wall and livestream for a Pentecostal congregation.
Weighing a platform? See the honest side-by-sides.
Real numbers, including where the other side wins.
What ministry leaders ask first.
Pulled from actual first calls: multi-campus math, ownership, tradition-specific features, and what happens to the data if anything goes sideways.
We have three campuses. How does the math work?
Three campuses is $750/mo, total. Five is $1,250/mo. Each additional campus is a flat $250/mo, with no per-member fee, no per-feature unlock, and no separate Multi-Campus tier. Add a campus, your bill goes up by $250. Drop a campus, it goes down by $250. There is no minimum and no ceiling.
Do we need someone on staff who's technical?
No, and that's the point. We build the app, write the push notifications, run App Store submissions, and ship every update. Your team updates facts in a simple admin: events, service times, group leads. Nobody on your staff designs screens, builds graphics, or touches a build.
How is this actually different from Subsplash, Tithely, or Pushpay?
Those are self-serve platforms with established templates and feature sets. Rehost provides a custom app under your ministry's brand and an operating team that handles updates. Member data remains yours, while developer accounts, domains, code licenses, exports, and handoff follow the signed agreement.
What about denomination-specific needs: Catholic confession times, Hebrew calendar, Hindu festival dates?
Built in, custom per ministry. We've shipped Mass schedules with Liturgical seasons, yahrzeit reminders tied to the Hebrew calendar, Ramadan prayer-time integration, daily Gurbani for Sikh sangats, and saint-of-the-day flows. Tell us what your tradition requires and we build it. No checkbox required.
How does giving actually work? Who holds the money?
Members give inside your app in two taps, recurring or one-time. Funds route through your processor (Stripe, Pushpay's API, Tithe.ly's API, or whichever is in your name) and land in your account. We don't touch your money. We integrate the rails.
Will members actually download it?
Adoption depends on how clearly the ministry launches the app, whether it replaces a real weekly task, and how consistently leaders use it. We help with the launch plan and measure installs and active use, but we do not promise an adoption or giving percentage without evidence from that specific ministry.
How fast does a campus go live?
The launch schedule depends on scope, content readiness, integrations, and App Store or Google Play review. The signed scope names the target timeline and responsibilities. We handle design, store submission, reviewer notes, and compliance work; your ministry handles approved content and the launch announcement.
What about congregant data: who owns it, where does it live?
Your ministry retains the member content and data it provides. The signed agreement identifies storage, security responsibilities, exportable records, transferable accounts, retention, code licenses, handoff, notice, and service-end terms. Rehost owns its service software, code, and designs unless that agreement states otherwise.
Faith-specific resources.
For multi-campus operations, the cost math, and the migration path off Subsplash, Tithe.ly, or Pushpay.
Math
Multi-campus pricing math
Three-year cost comparisons across 1, 3, 5, 10 campus configurations vs Subsplash, Pushpay, custom dev.
Migration
From Subsplash, Tithe.ly, or Pushpay
The 30-day migration plan that doesn't break Sunday morning.
Playbook
Multi-campus operations in LA County
How LA-area multi-campus churches actually run on Sunday mornings.