Deployment Options
If you need a development or training instance of the platform, we can build one for you as part of our Deployment services. Secondary Systems will only be built or refreshed as part of the Deployment Services listed below. We do not offer standalone sandboxes.
Sandbox System
A Sandbox System is set up to run in side-by-side folders in the production domain. A Sandbox can be used for training, software development, testing, or idea proving.
- MobileTools
- Sunset or Legacy Applications
This type of system is eligible for Sandbox Deployments.
Beta System
A Beta System runs on a separate domain from the production system and supports Cloud Applications.
This type of system is required for Development Deployments and is also eligible for Sandbox Deployments.
Sandbox Deployments
Deployments for sandbox systems exclude some applications. This type of deployment takes place at the same time as production so the two systems are always up-to-date.
Sandbox and Beta systems are eligible for this service.
Price is $75/month 1
- Receive updates applied to a Sandbox system so your Sandbox system is always ready for training, software development, testing, or idea proving.
- Designed primarily for churches who are Self-Hosted or Dedicated Cloud customers.
- Includes:
- Sandbox system updated on the same schedule as your Production system as part of the regular Deployment schedule, including:
- Sandbox cloud instance for Tools, Batch Manager Tool, and LifeApps.
- Report updates for a separate instance of SSRS (or a separate folder in the existing instance).
- Two data refreshes/syncs are included per year. The first of these will be used to build or initially refresh your sandbox. Contact Support to schedule.
- Additional data refreshes are available upon request for an additional cost. Contact Support to request.
- Sandbox system updated on the same schedule as your Production system as part of the regular Deployment schedule, including:
- Exclusions:
- Not available for onboarding churches until after your Cutover Date.
- Shared Hosting is excluded.
- This service applies only to Deployments, not Support. Support coverage does not include supporting Sandbox systems. If you email Support regarding an issue with your Sandbox system, we are happy to recommend the services of one of our highly regarded vendors.
Contact Support to request joining the Sandbox Deployments.
Development Deployments
Development deployments are available for beta systems and include all applications. This type of deployment is designed for staggered deployments in which the Beta system receives updates in advance of the production system.
- Receive staggered deployments to Beta and Production systems to allow time for internal testing of MinistryPlatform releases and for your team to make any impact-related changes needed to custom development before production is affected.
- Designed primarily for churches that:
- Create extensive custom development leveraging the MinistryPlatform API.
- Are a Self-Hosted or Dedicated Cloud customer.
- A wildcard certificate or second domain certificate (this service requires a beta system, not a sandbox).
- Beta and Production systems exist on the same server (we are willing to discuss exceptions).
- At least one full-time, on-staff developer (the majority of custom development is not via a third party).
- Includes:
- Beta instance updated as part of the normal customer-wide deployment schedule, including:
- Beta cloud instance for Batch Manager Tool
- Beta cloud instance of Tools
- Report updates for a separate instance of SSRS (or separate folder in an existing instance)
- Production instance updated with one or more releases upon request. Contact Support to schedule. Must be within three deadlines throughout the year where your Production instance must be up to date with all the latest updates:
- February 1 (Updates applied to Beta Sept 16-Jan 15)
- June 1 (Updates applied to Beta Jan 16-May 15)
- October 1 (Updates applied to Beta May 16-Sept 15)
- Two data refreshes/sync included per year. Contact Support to schedule.
- Additional data refreshes are available upon request for an additional cost. Contact Support to request.
- Beta instance updated as part of the normal customer-wide deployment schedule, including:
- Exclusions:
- Not available for Shared Hosting churches or churches in implementation.
- This service applies only to deployments, not Support.
- Any issues that arise follow the standard process for reporting issues for Support to vet and document and if needed for Dev to address in a future release.
- Any issues that arise in Production, but not in Beta, can be addressed by updating Production to the latest release. Contact Support to schedule. If there is a specific report/routine fix needed immediately, but updating Production is not yet an option (for example, another change's impact is still being tested and addressed by your team), we are willing to discuss applying partial updates charged on a per-hour basis.
Contact Support to request joining the Development Deployments.