More locations. More moving parts. One software team.
For larger teams and more involved projects. We agree on what to build, what we’ll run, the price, and the responsibilities before work starts. Security and support requirements are confirmed for your project.
No upfront cost·NDA before review·Terms in writing
*If you need an RFP cycle or 200-question vendor security questionnaire, see "Who this isn't for" below.
What changes when you're bigger.
The model is the same. The proof is different.
One team. One contract.
One team handles the build and ongoing work in your agreement. You can see who is responsible for each part.
Security needs a written plan.
Tell us your security and data requirements. Supported controls, service levels, data locations, and required agreements must be confirmed for your project.
Custom scope. Predictable team.
We agree on the work, price, review process, and handoff in writing. Special requirements belong in that plan.
What to confirm before we start.
The signed scope records the supported setup, required agreements, and responsibilities for your project.
Staff sign-in requirements
Review your identity provider and the sign-in methods the proposed setup supports.
Access that fits each job
Set different access for operations, marketing, finance, and engineering.
Data protection requirements
Confirm storage, encryption, access controls, and responsibilities for the agreed setup.
Written availability targets
Any uptime target, monitoring, and response terms belong in the signed agreement.
Data location review
Confirm supported storage regions and project requirements before work starts.
Required data agreements
Confirm which agreements and vendor arrangements the project needs and can support.
Mutual NDA before review
Standard mutual NDA before any code or systems discussion.
Handover terms by agreement
Documentation, data exports, account transfers, code licenses, and transition support are defined in the enterprise agreement.
Who this isn't for.
If you need an RFP cycle, a vendor security questionnaire round-trip, or a custom MSA before the first call, we are not the right fit. The model only works because we don't run that playbook. We will refer you to a partner who does, on the same call.
Questions your security team will ask.
Honest answers, in plain English.
Do you do SSO?
Single sign-on depends on the identity provider, accounts, and proposed software. We review those requirements and confirm any supported setup in the written scope.
Can we sign an NDA before talking?
Yes. Standard mutual NDA before any code review or systems discussion. Your legal team can send us a redline.
What's the minimum engagement?
Enterprise commitments, notice, termination, exports, handoff, and service-end terms are custom-scoped and documented in the signed agreement.
Can our security team review the stack?
Yes, on a call. We walk through hosting, data flows, encryption, and access controls. We will not fill out a 200-question vendor security questionnaire.
What about SOC 2 / HIPAA / GDPR?
These requirements need a project-specific review. A vendor’s certification does not establish the status of the whole service. The signed scope must confirm supported controls, vendors, required agreements, and responsibilities before work starts.
Can we receive code or repository access?
Yes, when the enterprise agreement includes the required license, repository access, documentation, infrastructure handoff, and transition support. Rehost owns its service software, code, and designs unless the signed agreement grants different project-specific rights.
Who is this not for?
If you need an 18-month procurement cycle, a custom MSA before the first call, or a vendor security questionnaire round-trip, we are not the right fit. We will refer you to a partner who is.
For multi-location operations.
Read about software for several healthcare locations or church campuses, and see how we plan larger projects.
Playbook
Multi-location dental groups
Patient-data requirements, provider agreements, and front-desk work across several offices.
Playbook
Multi-campus church operations
Sunday morning across multiple campuses, linear per-campus pricing.
Method
How Rehost works
How we handle the work, accounts, and handoff when your project needs a custom plan.
Business is unpredictable. We're not.
One conversation, then our team takes it. Custom-scoped commitment, notice, export, handoff, and service-end terms are documented in writing.
*If you're already a client, please reach out to us via email so we can add this to your account.