Skip to main content

Practices and clinics

A clear hosting plan for your practice website.

Keep your website's hosting manageable. See where your forms and patient data fit, what an engineer handles, and what your web team still owns.

No sales team. Quotes, customer service and support come from qualified, trained systems engineers.

01 / Find your starting point

What does your website actually do?

A practice website, a patient portal and an intake form can have different hosting arrangements. Start by following the data.

Information and directions

If the site only publishes information and does not handle patient details, you may not need this hosting service. Check forms, scripts and connected services before deciding.

Forms and appointment requests

Map where submissions are stored, emailed or forwarded. Hosting coverage does not automatically cover a separate forms or email provider.

A separately hosted portal

Identify what stays with your portal vendor and what runs on your website. Moving a website is not the same as moving your clinical records system.

Use the hosting assessment

02 / Budget before a call

Compare a starting point for your software.

Choose the platform your website already uses. Review the full tier details before deciding on capacity or support.

Drupal

From $229/month

Compare capacity, plan-specific support and onboarding terms for this platform.

Compare Drupal plans

WordPress

From $199/month

Compare capacity, plan-specific support and onboarding terms for this platform.

Compare WordPress plans

The workload determines the plan, not the size of your organization. Migration has defined onboarding terms; application work and custom architecture are separate from the managed infrastructure scope.

03 / Clear ownership

You should not have to guess who fixes it.

We operate the hosting layer

  • Server and supported service-stack maintenance.
  • Infrastructure monitoring, security controls and backups.
  • Investigation to identify whether a problem is in the infrastructure or application.

Your web team operates the website

  • Website code, CMS, plugins, themes and content.
  • Application updates, testing and user permissions.
  • Connected software and your organization's policies and training.

You can keep working with your designer or developer. If you do not have someone maintaining the application, tell us before the move so that responsibility is clear.

Read the full support scope and terms

04 / Moving with a plan

Know the steps before changing hosts.

  1. Review

    Identify your site, forms, dependencies and technical contact.

  2. Agree

    Confirm hosting, BAA and migration scope, including onboarding terms and any extra work.

  3. Test and move

    Check the new environment, agree the cutover window and plan recovery if something needs attention.

  4. Hand over

    Confirm access, support instructions and who maintains the website after the move.

Timing depends on the site and its dependencies. Review the included onboarding hours and conditions; additional work is scoped before it starts.

05 / Bring what you know

Your practice website handover checklist.

Use this with your practice manager and web designer. You do not need every answer to ask for help.

  • Website address, platform and current hosting provider.
  • Forms, appointment tools and the systems that receive their submissions.
  • Who manages the domain, application updates and website accounts.
  • Any launch date or times when a move would be disruptive.
  • Budget expectations and the support you need after the move.

Use this list with your team. Share this page or print it for your planning discussion. Keep patient information and credentials out of public inquiries.

Link to this checklist
Do I need to replace my website or EHR?

This is a hosting discussion. We will review the software you use and its requirements; it does not assume a new website or a replacement clinical system.

Can I start without knowing the right plan?

Yes. Describe your website and main concern. An engineer can help identify the next questions without asking you to choose server specifications first.

You do not need a server specification to start.

Tell us what you are building or moving. An engineer will help establish the infrastructure and support scope, whether that fits a published plan or needs a custom configuration.

Discuss my practice website

An inquiry does not place an order.