Skip to content
The Things Stack documentation home
Getting Started Concepts Cloud Enterprise Integrations API Hardware
Getting Started Concepts
Cloud Enterprise
Integrations API Hardware
Get The Things Stack

    Recent searches

      Popular pages

      • Getting Started
      • Adding Gateways
      • Adding Devices
      • Payload Formatters
      • Webhooks
      • Authentication

      No results for “”.

      • Check the spelling, or try fewer or more general words.
      • Ask the community on The Things Network Forum
      • Contact support
      ↑↓ to navigate ↵ to open Esc to close

      Concepts

      • Overview
      • Architecture
      • Features
        • Console
        • Command-line Interface
        • Multi-tenancy
        • Gaining insights using Events
        • LoRaWAN
        • Single Sign-On
        • Alerting
        • Network Operations Center
      • Networking
      • Migrate to The Things Stack
      • Packet Broker
      • Server Addresses
      • Advanced Topics
      • Troubleshooting
      • The Things Stack Sandbox

      Multi-tenancy

      Updated 20 January 2025 Edit on GitHub
      Copy page
      • View as MarkdownThis page as plain text
      • Open in ChatGPTAsk questions about this page
      • Open in ClaudeAsk questions about this page

      Multi-tenancy is at the core of what make The Things Stack a production-grade, enterprise level LoRaWAN Network software.

      This means that you can create multiple tenants, each of which operates as a separate logically isolated namespace with its own entities (ex: users, organisations, devices, gateways etc) but uses a shared underlying infrastructure.

      Key Features

      1. Tenant Isolation

      • Each tenant has its own namespace which forces data isolation.
      • Users/organizations of one tenant cannot access other tenants making the system secure by default.

      2. Extensibility

      • Creating multiple tenants makes it easy for users to manage their LoRaWAN Fleet.
      • Tenants can be used for logical separation of environments (e.g., development, staging, production) allowing for maximum flexibility.

      3. Custom Configurations

      • Tenants flexibility to customize their tenant configurations (ex: custom branding, user rights etc).

      4. Centralized Administration

      • Users can easily administer tenants (create/delete/update) using a Tenant Admin Key (which is available for enterprise deployments).
      • But tenant-specific admins control their respective environments.
      ← Command-Line Interface Reference Gaining insights using Events →

      On this page

      • Key Features

      Sections

      Getting Started

      Concepts

      Cloud

      Enterprise

      Integrations

      API

      Hardware

      Sitemap

      View our Sitemap

      Contributing

      GitHub

      About Us

      The Things Industries

      Privacy Policy

      Cookie settings

      Cookie Settings

      We use cookies to enhance your experience, analyze site traffic and deliver personalized content. Read our Privacy Policy.

      Cookie categories