# Deployments Overview

### Deployment Architecture

Metamanagement deploys your vendor's services in as much isolation as we can. We isolate the infrastructure at a networking level, putting all services in their own VPC, but we also isolate the VPC itself from your main services, putting content in a sub-account or separate project to ensure that there's no ability for Metamanagement or your vendor to inappropriately access data or services that they should not.

This architecture decision affords us a few advantages. Because the customer owns the deployment in its entirety, they can change VPC ingress/egress settings, install endpoint monitoring solutions, and even set billing alerts to control how the infrastructure behaves.

Even more importantly, this architecture gives customers tight control over what data the newly installed service can access and what systems can access the newly installed service. By using either VPC peering or more selective cloud-specific networking primitives, customers can enjoy a tight flow of information above and beyond what they might expect in traditional on-premise settings.

### How to deploy

For specific instructions on how to deploy, please consult the following pages:

{% content-ref url="/pages/-MAD0Kd7K-xTDRqiV8ea" %}
[Deploying on AWS](/deployments/aws.md)
{% endcontent-ref %}

{% content-ref url="/pages/-MAD0NB0SQ0UZz7yQiIO" %}
[Deploying on GCP](/deployments/gcp.md)
{% endcontent-ref %}

{% content-ref url="/pages/-MAD0OdQkb-LGlMqTw-0" %}
[Deploying on Azure (beta)](/deployments/azure.md)
{% endcontent-ref %}


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## 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://docs.metamanagement.dev/deployments/overview.md?ask=<question>
```

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.