The operating layer between your team and your software.
Six principles that define what Rehost actually is. Read this and you'll know whether we're the right partner for your operation or whether you're better off with a different model.
01
Operations stay in your name.
Domain on your registrar. Mobile-app developer accounts under your business. Payment processor wired to your bank. Customer database, member list, sales history — kept as your records, exportable on request. The fee covers Rehost operating the platform; the operation itself is yours from day one and stays yours if we ever part ways.
Why this principle: Most rented platforms hold the customer relationship. When you cancel, the app disappears and so does three years of operating history. We refused to design that pattern in.
02
Your team never logs into a dashboard.
No CMS account for your front desk. No admin panel password to forget. No quarterly login audit. When you want a price change, a new menu item, a sermon archive update, a property listed, an article published — you message us and we ship it. That is the entire interface your staff ever touches.
Why this principle: The point of done-for-you is that you don't do it. Every dashboard we hand a client is a dashboard that decays.
03
The number on the page is the number on the bill.
$250/mo per campus. $350/mo for a website. $850/mo for the business stack. No setup fee, no per-seat surcharge when you hire, no per-transaction cut when sales lift, no retainer reset on January 1. The number doesn't move when your operation grows; it moves only when something fundamental changes about what we run for you, and even then we tell you first.
Why this principle: Subscription pricing that meters every change is project pricing in disguise. We model the work into a flat fee and stay accountable for it.
04
Multi-campus, multi-property, multi-location is linear.
One Faith campus is $250. Three are $750. Five are $1,250. There is no separate Multi-Campus tier to upgrade to, no negotiated discount sheet, no per-member fee waiting at 1,000 members. Add a campus, your bill goes up by $250. Drop a campus, it goes down by $250.
Why this principle: Most multi-location pricing punishes growth. Linear math means the operator that adds a fifth campus pays the same per-campus rate as the operator with one. Growth shouldn't tax you.
05
The team that builds it is the team that runs it.
The engineer on your first call is the engineer who scopes your project, ships your build, and responds when something needs attention six months later. There's no agency-to-support handoff, no offshoring layer, no ticket queue routing your message through a triage step.
Why this principle: The hardest part of running software is context. Splitting the team that builds it from the team that runs it throws the context away every Monday.
06
Local. Physical. In-person available.
Headquartered at 453 S. Spring Street, Suite 400 in Downtown LA. Most of the operators we work with are inside a 30-mile radius. We meet in person at your location, we know the cross-streets, and we understand what "the lunch rush" means at a Whittier restaurant versus a downtown salon. Remote work is fine — but the LA roots matter for the operators who want them.
Why this principle: Local presence is a feature, not nostalgia. It's faster Monday-morning response, in-person launches, and a team that can show up if something is on fire.
Where the principles show up across the site.
Each pricing tier and case study below is an instance of the principles operating in a real client engagement.
Business — $850/mo
App, website, loyalty, AI ops — operated for LA County businesses.
Faith — $250/mo per campus
Linear multi-campus math. 3 campuses = $750/mo, 5 = $1,250/mo.
Website — $350/mo
Custom .com with weekly content, no CMS for your staff.
Case study: Vintage Nail Bar
A Whittier salon stops administering five tools and runs one app instead.
Case study: Nonna's Kitchen
A family Italian restaurant cuts a six-tool stack down to one bill.
Case study: Lumia Med Spa
A med spa replaces its scheduling stack and gets Mondays back.
Things people ask about the method.
Is this a process methodology like Agile or Waterfall?
It's more operating philosophy than software methodology. The six principles describe how the relationship works between Rehost and the operator, not how we run sprints internally. Internally we ship in short iterative cycles with the operator's review built into each cycle, but the principles are about what you can expect from us as a partner, not how engineers schedule their work.
Are these principles negotiable for enterprise customers?
The first four are not — operations in your name, no dashboards for your staff, flat pricing, linear multi-campus math. These are the deal. Principles five and six can flex for very large customers (dedicated team configurations, multi-region scope), but only after a scoping conversation that lays out what changes.
What's the catch?
The trade-off is configurability. Your team can't log in and tweak workflows — which is the whole point — but it also means changes happen on Rehost's pace, not yours. Most operators consider that a feature; some don't. If your team wants real-time control over every dashboard knob, we're the wrong partner and we'll tell you on the first call.