> For the complete documentation index, see [llms.txt](https://docs.didge.io/home/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.didge.io/home/pricing/sensors-and-probes-pricing/gateways.md).

# Gateways

Multitech Conduit AP – LoRaWAN Gateway with SIM Connectivity (MT-CAP Model)

### Overview

The **Multitech Conduit AP (MT-CAP)** is a commercial-grade LoRaWAN gateway designed for reliable and secure long-range communication in IoT environments. Featuring **SIM-based 4G LTE connectivity**, it ensures robust data transmission even in remote or infrastructure-limited locations.

<a href="https://didge.io/purchases/p/gateway" class="button primary" data-icon="wave-sine">Purchase</a>

> $900 AUS per unit, including SIM card

<figure><img src="https://763736409-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FYnSaa2Z7Ds33LciBBITN%2Fuploads%2FjR55ufPY7YkMqoJKEbwi%2FTap%20Phone%20(6).png?alt=media&amp;token=6d5e7b4b-227b-4960-895e-cb33e087fa3f" alt="" width="563"><figcaption></figcaption></figure>

Purpose-built for seamless integration with the MFC/Didge temperature and compliance ecosystem, the MT-CAP model delivers stability, uptime, and secure device-to-cloud communication for distributed sensor networks.

***

{% tabs %}
{% tab title="Kit" %}

<figure><img src="https://763736409-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FYnSaa2Z7Ds33LciBBITN%2Fuploads%2FVBhOL5EQa5BJWffbUjUE%2FIMG_6271.jpg?alt=media&amp;token=5c5f4f48-ba56-4b17-8932-2272ff32a157" alt="" width="563"><figcaption></figcaption></figure>
{% endtab %}

{% tab title="Installed" %}

<figure><img src="https://763736409-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FYnSaa2Z7Ds33LciBBITN%2Fuploads%2FDUccEaOsuYppvOBFGWPy%2FIMG_7699.jpg?alt=media&amp;token=799a3a94-1a7b-4460-be90-db5f3dd4a2d9" alt="" width="563"><figcaption></figcaption></figure>
{% endtab %}
{% endtabs %}

### Key Features

* **LoRaWAN Gateway (MT-CAP)**
  * Designed for indoor/outdoor commercial use
  * Supports LoRaWAN Class A & C devices
* **SIM-Based 4G LTE Backhaul**
  * Operates on mobile networks for primary or backup internet
  * Ideal for locations with no Wi-Fi or Ethernet
  * **Includes international roaming SIM card** for immediate deployment and global compatibility
* **Plug-and-Play Provisioning**
  * Ships pre-configured to connect to MFC/Didge cloud services
  * Minimal setup required onsite
* **High Device Capacity**
  * Supports 100+ active sensors with low latency
* **Rugged Form Factor**
  * Compact ABS housing, DIN rail or wall mountable
* **Remote Management Enabled**
  * Firmware upgrades and diagnostics available over the air (OTA)

***

### Typical Use Cases

* Retail and hospitality (back-of-house cold storage)
* Remote facilities with no fixed network
* Food trucks or mobile operations
* Pop-up/seasonal kitchens and storage depots
* Supplementary coverage in large commercial sites

***

### Technical Specifications

* **Model**: Multitech Conduit AP (MT-CAP-LNA3)
* **Connectivity**:
  * Cellular LTE (4G SIM)
  * Ethernet LAN port (for redundancy or alternative)
* **LoRa Frequency Bands**: AU915 / AS923
* **Antenna**: External LTE and LoRa antennas included
* **Power**: 9–32 VDC input (AC adapter included)
* **Mounting**: DIN rail, wall, or surface mount
* **Certifications**: CE, FCC, RCM compliant

***

Deploy the **Multitech MT-CAP Gateway** to enable fast, reliable LoRaWAN connectivity—anywhere you need IoT sensor coverage with or without fixed infrastructure.


---

# 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 by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.didge.io/home/pricing/sensors-and-probes-pricing/gateways.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

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.