---
title: "What is LoRaWAN?"
canonical: https://wavect.io/glossary/lorawan/
language: en
description: "A low-power, long-range wireless protocol for connecting battery-operated sensors to the internet, used in smart-city and agricultural IoT deployments."
image: "https://wavect.io/img/general/bak/open_graph_preview.jpg"
---

TECHNOLOGIES

# LoRaWAN

A low-power, long-range wireless protocol for connecting battery-operated sensors to the internet, used in smart-city and agricultural IoT deployments.

Last reviewed: 2026-05-24 by [Kevin Riedl](/team/kevin-riedl/) [wiki ↗](https://www.wikidata.org/wiki/Q139796365)

LoRaWAN is the networking layer that makes large-scale [IoT](/services/internet-of-things/) economical. Devices run on coin-cell batteries for years, transmit small payloads (a few hundred bytes), and reach gateways kilometers away. The trade-offs: low bandwidth, infrequent updates, and a non-trivial deployment phase to get gateway coverage right.

When the radio is working but the application payload is wrong, use the free [LoRaWAN payload codec tester](/tools/lorawan-payload-codec-tester/) to run TTN, ChirpStack, and legacy JavaScript formatters against repeatable byte fixtures without uploading device data.

The applications we have shipped include smart-city sensor networks (parking, environment, waste), agricultural monitoring, and industrial telemetry. The pattern is the same in all of them: cheap, dumb sensors at the edge; gateways aggregating to a network server; the network server forwarding to your application backend.

Worked example of where the budget actually goes, and the mistake founders make: they price the sensors and forget the coverage. A farm or a city district needs gateways positioned so that every sensor reaches at least one, and getting that wrong means dead zones, retransmissions, and batteries that drain in months instead of years. On a real deployment the site survey and gateway placement is often the harder half of the project, well after the per-unit sensor cost has been signed off. Walls, terrain, and metal silos all eat range, and you only find out by measuring on site.

The other decision founders rush is who owns the network. With LoRaWAN you typically run your own gateways, which means no per-device cellular bill but a real responsibility: you operate the gateways, the network server, and the coverage. The cellular alternatives (NB-IoT, LTE-M) flip that, the carrier owns coverage everywhere they reach, and you pay a per-device data plan in exchange. For a dense, fixed deployment you control (a campus, a farm, a city district), owning the network usually wins on cost over the device lifetime. For a low device count spread unpredictably across regions, paying the carrier is cheaper than building coverage you will barely use.

The honest trade-off: LoRaWAN trades bandwidth and latency for range and battery life, and that trade is non-negotiable, not tunable. It is the right tool when you need many sensors over a wide area with multi-year battery life and you only send a few bytes now and then. It is the wrong tool when you need high bandwidth, low latency, or per-device connectivity that follows the device around; for those, 5G NB-IoT or LTE-M is usually the better fit. Decide which axis your product actually lives on before committing to the radio.

// FAQ

## FAQs

### LoRaWAN or NB-IoT?

LoRaWAN when you control the gateways and want no per-device cellular fees. NB-IoT when device count is lower, coverage is needed everywhere a carrier reaches, and per-device data plans are acceptable. Range and battery life are comparable; the economics and deployment model are not.

### What kills most LoRaWAN deployments?

Gateway coverage planning. Engineers underestimate how much building density, terrain, and antenna placement matter. A pilot that works in the parking lot dies in the basement. Site-survey before scale-up, every time.

### Can LoRaWAN carry real-time data?

No. Duty-cycle regulations and the low-bandwidth physical layer cap transmissions to small payloads, infrequently sent. If you need sub-minute updates, sub-kilobyte payloads, or two-way streaming, you want a different protocol.

Related services

- [Internet of Things](/services/internet-of-things/)

Related case studies

- [Twinsoft AI](/case-studies/twinsoft-ai/)

Related guides

- [How to choose a tech stack for an MVP](/software-development-guide/how-to-choose-a-tech-stack-for-mvp/)

Talk to us

## Structured Data

```json
{
  "@context": "https://schema.org",
  "@graph": [
    {
      "@id": "https://wavect.io/#organization",
      "@type": [
        "Organization",
        "ProfessionalService",
        "LocalBusiness"
      ],
      "employee": [
        {
          "@id": "https://wavect.io/team/kevin-riedl/#person",
          "@type": "Person",
          "jobTitle": "Managing Director",
          "name": "Kevin Riedl",
          "url": "https://wavect.io/team/kevin-riedl/",
          "worksFor": {
            "@id": "https://wavect.io/#organization",
            "@type": [
              "Organization",
              "ProfessionalService",
              "LocalBusiness"
            ]
          }
        },
        {
          "@id": "https://wavect.io/team/christof-jori/#person",
          "@type": "Person",
          "jobTitle": "Managing Director",
          "name": "Christof Jori",
          "url": "https://wavect.io/team/christof-jori/",
          "worksFor": {
            "@id": "https://wavect.io/#organization",
            "@type": [
              "Organization",
              "ProfessionalService",
              "LocalBusiness"
            ]
          }
        }
      ],
      "founder": [
        {
          "@id": "https://wavect.io/team/kevin-riedl/#person",
          "@type": "Person",
          "jobTitle": "Managing Director",
          "name": "Kevin Riedl",
          "url": "https://wavect.io/team/kevin-riedl/",
          "worksFor": {
            "@id": "https://wavect.io/#organization",
            "@type": [
              "Organization",
              "ProfessionalService",
              "LocalBusiness"
            ]
          }
        },
        {
          "@id": "https://wavect.io/team/christof-jori/#person",
          "@type": "Person",
          "jobTitle": "Managing Director",
          "name": "Christof Jori",
          "url": "https://wavect.io/team/christof-jori/",
          "worksFor": {
            "@id": "https://wavect.io/#organization",
            "@type": [
              "Organization",
              "ProfessionalService",
              "LocalBusiness"
            ]
          }
        }
      ],
      "legalRepresentative": [
        {
          "@id": "https://wavect.io/team/kevin-riedl/#person",
          "@type": "Person",
          "jobTitle": "Managing Director",
          "name": "Kevin Riedl",
          "url": "https://wavect.io/team/kevin-riedl/",
          "worksFor": {
            "@id": "https://wavect.io/#organization",
            "@type": [
              "Organization",
              "ProfessionalService",
              "LocalBusiness"
            ]
          }
        },
        {
          "@id": "https://wavect.io/team/christof-jori/#person",
          "@type": "Person",
          "jobTitle": "Managing Director",
          "name": "Christof Jori",
          "url": "https://wavect.io/team/christof-jori/",
          "worksFor": {
            "@id": "https://wavect.io/#organization",
            "@type": [
              "Organization",
              "ProfessionalService",
              "LocalBusiness"
            ]
          }
        }
      ],
      "name": "Wavect GmbH",
      "subjectOf": {
        "@id": "https://wavect.io/verified-claims.json#dataset",
        "@type": "Dataset",
        "creator": {
          "@id": "https://wavect.io/#organization",
          "@type": [
            "Organization",
            "ProfessionalService",
            "LocalBusiness"
          ]
        },
        "description": "A machine-readable registry of quantitative and qualitative claims published by Wavect, with review dates, localized page appearances and public third-party citations where available.",
        "inLanguage": "en",
        "isAccessibleForFree": true,
        "license": "https://creativecommons.org/licenses/by/4.0/",
        "name": "Wavect verified publication claims",
        "url": "https://wavect.io/verified-claims.json"
      },
      "url": "https://wavect.io/"
    },
    {
      "@id": "https://wavect.io/team/kevin-riedl/#person",
      "@type": "Person",
      "jobTitle": "Managing Director",
      "name": "Kevin Riedl",
      "sameAs": [
        "https://www.wikidata.org/wiki/Q139796365",
        "https://www.linkedin.com/in/wsdt",
        "https://github.com/wsdt"
      ],
      "url": "https://wavect.io/team/kevin-riedl/",
      "worksFor": {
        "@id": "https://wavect.io/#organization",
        "@type": [
          "Organization",
          "ProfessionalService",
          "LocalBusiness"
        ]
      }
    },
    {
      "@id": "https://wavect.io/team/christof-jori/#person",
      "@type": "Person",
      "jobTitle": "Managing Director",
      "name": "Christof Jori",
      "sameAs": [
        "https://www.wikidata.org/wiki/Q139796367",
        "https://www.linkedin.com/in/jocr77/",
        "https://github.com/jo-chris"
      ],
      "url": "https://wavect.io/team/christof-jori/",
      "worksFor": {
        "@id": "https://wavect.io/#organization",
        "@type": [
          "Organization",
          "ProfessionalService",
          "LocalBusiness"
        ]
      }
    },
    {
      "@id": "https://wavect.io/#website",
      "@type": "WebSite",
      "inLanguage": [
        "en",
        "de",
        "es",
        "zh"
      ],
      "name": "Wavect",
      "potentialAction": {
        "@type": "SearchAction",
        "query-input": "required name=search_term_string",
        "target": {
          "@type": "EntryPoint",
          "urlTemplate": "https://wavect.io/search/?q={search_term_string}"
        }
      },
      "publisher": {
        "@id": "https://wavect.io/#organization",
        "@type": [
          "Organization",
          "ProfessionalService",
          "LocalBusiness"
        ]
      },
      "url": "https://wavect.io/"
    }
  ]
}
```

```json
{
  "@context": "https://schema.org",
  "@graph": [
    {
      "@id": "https://wavect.io/glossary/lorawan/#term",
      "@type": "DefinedTerm",
      "alternateName": [
        "LoRa",
        "IoT",
        "Long Range WAN"
      ],
      "description": "A low-power, long-range wireless protocol for connecting battery-operated sensors to the internet, used in smart-city and agricultural IoT deployments.",
      "inDefinedTermSet": "https://wavect.io/glossary/#termset",
      "name": "LoRaWAN",
      "termCode": "lorawan",
      "url": "https://wavect.io/glossary/lorawan/"
    },
    {
      "@id": "https://wavect.io/glossary/lorawan/#webpage",
      "@type": "WebPage",
      "about": {
        "@id": "https://wavect.io/#organization",
        "@type": [
          "Organization",
          "ProfessionalService",
          "LocalBusiness"
        ]
      },
      "author": {
        "@id": "https://wavect.io/team/kevin-riedl/#person",
        "@type": "Person",
        "name": "Kevin Riedl",
        "url": "https://wavect.io/team/kevin-riedl/"
      },
      "dateModified": "2026-05-24",
      "description": "A low-power, long-range wireless protocol for connecting battery-operated sensors to the internet, used in smart-city and agricultural IoT deployments.",
      "headline": "LoRaWAN",
      "inLanguage": "en",
      "isPartOf": {
        "@id": "https://wavect.io/#website",
        "@type": "WebSite"
      },
      "lastReviewed": "2026-05-24",
      "mainEntity": {
        "@id": "https://wavect.io/glossary/lorawan/#term"
      },
      "mentions": [
        {
          "@id": "https://wavect.io/#organization",
          "@type": [
            "Organization",
            "ProfessionalService",
            "LocalBusiness"
          ]
        },
        {
          "@type": "Service",
          "name": "Internet of Things",
          "url": "https://wavect.io/services/internet-of-things/"
        }
      ],
      "name": "LoRaWAN",
      "reviewedBy": {
        "@id": "https://wavect.io/team/christof-jori/#person",
        "@type": "Person",
        "name": "Christof Jori",
        "url": "https://wavect.io/team/christof-jori/"
      },
      "speakable": {
        "@type": "SpeakableSpecification",
        "cssSelector": [
          ".gls-single__h1",
          ".gls-single__tldr"
        ]
      },
      "url": "https://wavect.io/glossary/lorawan/"
    },
    {
      "@type": "BreadcrumbList",
      "itemListElement": [
        {
          "@type": "ListItem",
          "item": "https://wavect.io/",
          "name": "Home",
          "position": 1
        },
        {
          "@type": "ListItem",
          "item": "https://wavect.io/glossary/",
          "name": "Tech, product & engagement glossary",
          "position": 2
        },
        {
          "@type": "ListItem",
          "item": "https://wavect.io/glossary/lorawan/",
          "name": "LoRaWAN",
          "position": 3
        }
      ]
    }
  ]
}
```

```json
{
  "@context": "https://schema.org",
  "@type": "FAQPage",
  "mainEntity": [
    {
      "@type": "Question",
      "acceptedAnswer": {
        "@type": "Answer",
        "text": "LoRaWAN when you control the gateways and want no per-device cellular fees. NB-IoT when device count is lower, coverage is needed everywhere a carrier reaches, and per-device data plans are acceptable. Range and battery life are comparable; the economics and deployment model are not."
      },
      "name": "LoRaWAN or NB-IoT?"
    },
    {
      "@type": "Question",
      "acceptedAnswer": {
        "@type": "Answer",
        "text": "Gateway coverage planning. Engineers underestimate how much building density, terrain, and antenna placement matter. A pilot that works in the parking lot dies in the basement. Site-survey before scale-up, every time."
      },
      "name": "What kills most LoRaWAN deployments?"
    },
    {
      "@type": "Question",
      "acceptedAnswer": {
        "@type": "Answer",
        "text": "No. Duty-cycle regulations and the low-bandwidth physical layer cap transmissions to small payloads, infrequently sent. If you need sub-minute updates, sub-kilobyte payloads, or two-way streaming, you want a different protocol."
      },
      "name": "Can LoRaWAN carry real-time data?"
    }
  ],
  "speakable": {
    "@type": "SpeakableSpecification",
    "cssSelector": [
      ".faq-question",
      ".faq-answer"
    ]
  }
}
```
