The first four articles in this series answered: what the GD6 is, why it's designed the way it is, how to use its open-source code, and how to deploy it. This final article answers the last question: which scenarios is it the right choice for, and how do you pick the right model.
For solution architects and procurement decision-makers, selection is never about "the best product" — it's about "the best fit for the project." This article walks through five typical scenarios where the GD6 is a strong fit, then breaks down the model code with a four-step decision tree, compares the GD6 against ManThink's GDI51 / GDO51 commercial gateways, and outlines three ways to pair the GD6 with the ThinkLink platform.
Typical deployment: Indoor environment monitoring, energy management, and people tracking in office buildings, industrial parks, and malls. These projects share common traits: moderate device density, devices scattered across floors, and reliable wired networks on site.
Why the GD6 fits:
Recommended models:
| Deployment region | Recommended model |
|---|---|
| Mainland China | GD614-AN-CN470-N-2 |
| Europe | GD618-AN-EU868-N-2 |
| Southeast Asia | GD618-AN-AS923-N-2 |
When to look elsewhere: If the project requires local historical data storage, offline data queries, or a built-in network server in the gateway, that's the GDI51's territory (see the positioning comparison below).
Typical deployment: Machine status monitoring on the shop floor, temperature/humidity and door-sensor monitoring in warehouses, environmental monitoring in electrical rooms. These sites often have dust and vibration, irregular power conditions, and some locations without wired networks.
Why the GD6 fits:
Recommended models:
| Deployment region | Recommended model |
|---|---|
| Mainland China | GD614-AG-CN470-N-2 |
| Europe | GD618-AG-EU868-N-2 |
Boundary note: The GD6 is an indoor product. For large outdoor coverage (factory perimeters, mines), choose the outdoor GDO51 gateway instead.
Typical deployment: Communication testing during product R&D, thing-model validation, protocol stack learning. This is where the GD6's differentiation is strongest — because it's open source.
Why the GD6 fits:
/api/status, /api/lora, /api/logs can be driven from scripts — far more efficient than clicking through a web UI for every device./spiffs can be read and written directly, covering non-standard test scenarios (custom channels, custom center frequencies).frontend/ source is open. When a demo system needs a tailored interface, changing the frontend beats changing protocols.Recommended model: Choose by local frequency band. Mainland China: GD614-AN-CN470-N-2; Europe: GD618-AN-EU868-N-2; Southeast Asia: GD618-AN-AS923-N-2.
When to choose the GDI51 instead: If what you're prototyping is edge capability itself — an embedded network server with local data storage — evaluate the GDI51 directly.
Typical deployment: University LoRaWAN labs, IoT course labs, graduate research projects.
Why the GD6 fits:
Recommended model: AN models by local frequency band. Labs have wired networks; 4G is not needed.
Typical deployment: Cross-border projects where the same product line deploys in multiple countries, or a company delivers LoRaWAN solutions to several overseas markets.
Why the GD6 fits:
Recommended model mix: Combine by "region → RF version → backhaul". For example, GD614-AN-CN470-N-2 for Mainland China, GD618-AN-EU868-N-2 for Europe, GD618-AN-US902-N-2 for North America.
Important: RF hardware and region are physically bound — they cannot be switched in software. Selecting the wrong region version means the device cannot legally transmit in the target market. Verify the target market's LoRaWAN regional parameters and local regulations before ordering.
The GD6 model format is GD61{4|8}-A{N|G}-{REGION}-{VERSION}-{1|2}. It's just four decision points:
Step 1: Target region → GD614 or GD618?
400 MHz-class (CN470, EU433) → GD614
800 MHz and above (EU868/AS923/AU915/US902) → GD618
Step 2: Need 4G / PoE? → AN or AG?
Ethernet + Wi-Fi is enough → AN
Need 4G backhaul or PoE power → AG
Step 3: Which concentrator? → suffix 1 or 2?
Cost-sensitive, proven classic → 1 (SX1301)
Lower power, higher sensitivity → 2 (SX1302)
Step 4: Confirm the region code → CN470 / EU433 / EU868 / AS923 / AU915 / US902
Region code must match RF hardware and local regulations
Example: GD618-AG-AS923-N-2 = 800 MHz-class RF + 4G/PoE included + AS923 region + default version + SX1302 concentrator.
Quick reference table:
| Scenario | RF version | Backhaul | Concentrator | Example model |
|---|---|---|---|---|
| Smart building (China) | GD614 | Ethernet+Wi-Fi | SX1302 | GD614-AN-CN470-N-2 |
| Smart building (Europe) | GD618 | Ethernet+Wi-Fi | SX1302 | GD618-AN-EU868-N-2 |
| Small industry (China, no cable) | GD614 | 4G primary | SX1302 | GD614-AG-CN470-N-2 |
| Small industry (Europe, no cable) | GD618 | 4G primary | SX1302 | GD618-AG-EU868-N-2 |
| Prototyping (SE Asia) | GD618 | Ethernet+Wi-Fi | SX1302 | GD618-AN-AS923-N-2 |
| North America project | GD618 | Ethernet+Wi-Fi | SX1301 | GD618-AN-US902-N-1 |
The GD6 isn't an isolated product in ManThink's lineup. To decide "GD6 vs GDI51 vs GDO51," start with the differences:
| Dimension | GD6 (open-source indoor) | GDI51 (commercial indoor) | GDO51 (commercial outdoor) |
|---|---|---|---|
| Positioning | Open, customizable, cost-effective | Complete out-of-the-box system | Rugged outdoor deployment |
| Main controller | ESP32-S3 (MCU) | LS1012A (Cortex-A53, Linux) | LS1012A (Cortex-A53, Linux) |
| OS | Bare metal + custom web services | Ubuntu / Linux environment | Ubuntu / Linux environment |
| Network server | External (ThinkLink/ChirpStack/TTN) | Embedded ThinkLink Edge | Embedded ThinkLink Edge |
| Local data storage | No (forwarding gateway) | Yes, historical data queries | Yes, historical data queries |
| Enclosure | Indoor design | Indoor design | IP67, surge protection, wide temperature |
| Open-source level | Firmware + web config fully open | Commercial product | Commercial product |
| Typical projects | Custom/self-built LoRaWAN, dev & verification | Mid-size commercial projects, building integration | Outdoor, industrial, harsh environments |
Selection guidance:
In one sentence: The GD6 puts control in your team's hands; the GDI51/GDO51 take the complexity off your plate. Choose the GD6 if you have development capability; choose GDI51/GDO51 if delivery speed matters most.
The GD6 is a full-protocol-stack gateway and works with any LoRaWAN network server. With the ThinkLink platform, there are three integration modes by project scale:
Mode 1: ThinkLink Cloud (free tier — up to 1,000 devices) For prototyping and small deployments. Free registration supports up to 1,000 devices, with device management, thing models, automation rules, and data visualization. As native gateway hardware, the GD6 registers in one click with automatic Gateway EUI sync. Cloud address: thinklink.manthink.cn.
Mode 2: ThinkLink Self-Hosted (Docker Compose) For private projects with data-sovereignty requirements. ManThink provides the ThinkLink-docker repository to run your own ThinkLink cloud with data staying on your network. The GD6 connects via UDP Packet Forwarder or MQTT Bridge, configured exactly like the cloud version.
Mode 3: Third-Party NS (ChirpStack / TTN / self-hosted LNS) For projects with an existing network server. The GD6 supports Basic Station (LNS/CUPS), Semtech UDP, and MQTT Bridge, so it plugs into existing infrastructure without any platform lock-in.
Decision guidance: Under 1,000 devices and quick time-to-live → Mode 1; data sovereignty concerns or larger fleets → Mode 2; existing NS or mandated platform → Mode 3. You can choose per project — no hardware change is needed on the GD6.
Looking back at the final question of the series: when should you choose the GD6?
If your core requirement is "gateway + network server + local storage in one box" or "outdoor harsh environments," the GDI51 / GDO51 are the better fit. The GD6's value isn't "good at everything" — it's delivering openness and cost-effectiveness to the extreme in the scenarios it's built for.
The four-step selection: fix the region (GD614/GD618), fix the backhaul (AN/AG), fix the concentrator (1/2), then verify the region code — and the right GD6 for your project is selected.
ManThink — Making IoT development more efficient.