---
sourceDocument: Australia Workflow Data Fabric
sourceDocumentLink: https://www.servicenow.com/docs/r/australia/integrate-applications

 Release :

    - australia

ft:locale :

    - en-US

ft:publication_title :

    - Australia Workflow Data Fabric

ft:clusterId :

    - crint

bundleId :

    - crint

workflow :

    - Creator


---

# Metadata collector deployment models

# Metadata collector deployment models {#ariaid-title1}

Release version: Australia  
Updated August 19, 2026  
![](https://www.servicenow.com/docs/portal-asset/ico-clock) 1 minute to read  
Choose how to deploy metadata collectors based on your network accessibility and security needs. Deploy on a MID Server you host, or use ServiceNow-managed cloud infrastructure.

Metadata collectors harvest metadata --- schemas, tables, columns, and lineage --- from your data sources and upload it to your ServiceNow instance for cataloging and governance. You can
deploy collectors in two ways: on a MID Server within your network, or in ServiceNow-managed cloud infrastructure. The choice depends on your source's network accessibility and whether you want to manage your own infrastructure.{#metadata-collector-deployment-models__metadata-collector-deployment-models-para-1}

## Deployment model selection {#metadata-collector-deployment-models__deployment-choice}

Select a deployment model using the Use MID server toggle on the metadata collector configuration form.

When a collector is configured to run on a MID Server, three routing models control how the system assigns a MID Server to the collection job. For details on each routing model, see [MID Server for metadata collectors](https://www.servicenow.com/docs/QcdynKbGhxv_ZIEalalxAg "When your source is behind a firewall or requires on-premises handling, deploy metadata collectors on a MID Server you host to harvest metadata from on-premises and privately networked data sources.").

## MID Server collectors (on-premises) {#metadata-collector-deployment-models__mid-server-collectors}

The collector runs as a job on a MID Server you host, inside your network. The MID Server reaches the source directly, then pushes the harvested metadata
back to your ServiceNow instance over the existing MID Server connection.

For system requirements and configuration guidelines, see [MID Server for metadata collectors](https://www.servicenow.com/docs/QcdynKbGhxv_ZIEalalxAg "When your source is behind a firewall or requires on-premises handling, deploy metadata collectors on a MID Server you host to harvest metadata from on-premises and privately networked data sources.").

## ServiceNow-hosted collectors (cloud) {#metadata-collector-deployment-models__servicenow-hosted-collectors}

The collector runs in ServiceNow-managed infrastructure. There is no host to provision or patch on your side. You register the connection and credentials, and ServiceNow runs the collector job.

Use this option if you do not want to provision or maintain a MID Server just for cataloging.

Requirements:

* Source system reachable from ServiceNow's cloud through direct internet access.
* Service account credentials with read access to the source's metadata APIs or system catalogs
* No local infrastructure to size or maintain

## Deployment model comparison {#metadata-collector-deployment-models__comparison}

{#metadata-collector-deployment-models__comparison__entry__3}

| Consideration | MID Server (on-premises) | ServiceNow-hosted (cloud) |
|-|-|-|
| Who runs the process | You, on your infrastructure | ServiceNow |
| Network exposure needed | None inbound; MID Server reaches out | Source must be reachable from ServiceNow's cloud |
| Best for | Sources behind a firewall or VPN, strict data residency requirements | Internet-reachable or cloud-native sources, no appetite for hosting infrastructure |
| Ongoing maintenance | You patch and size the MID Server | None |
[Table 1. MID Server versus ServiceNow-hosted collectors]

## What gets harvested {#metadata-collector-deployment-models__what-gets-harvested}

The deployment model doesn't change what's cataloged. Either way, the collector harvests schemas, tables, columns, and lineage from the source, then uploads them to the ServiceNow instance for cataloging, governance, and AI-ready workflows.