# Deployment Guide SPICE can be deployed on the cloud or on-premise environment, determined based on your own requirements. The following guides walk through how to deploy the various components of SPICE in your own environment. Medtronic LABS also provides SPICE as a software as a service (SaaS) model where we can host the application in the cloud and on-premise environment on behalf of our partners. If you are interested in leveraging SPICE in this way, please reach out to . Medtronic LABS has developed a [Total Cost of Ownership (TCO) tool](https://medtroniclabsorg-my.sharepoint.com/:x:/g/personal/kelly_a_batlle_medtroniclabs_org/ESKmoPBa6rVKjFQxmHnFmWABV5njkYjue2hvEDrwyjZb9A?e=ivWhN1) as an example for implementers looking to understand cost. This example looks at scaling up to two districts in a country and is helpful for implementers looking to deploy. --- # Agent Instructions: Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter: ``` GET https://spice.docs.medtroniclabs.org/deploy/deployment-guide.md?ask= ``` The question should be specific, self-contained, and written in natural language. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.