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

      The Things Stack Cloud

      • Overview
      • Subscription and billing
      • Server Addresses
      • Custom branding
      • Data Retention and Privacy

      Server Addresses

      Updated 13 February 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

      This page provides configuration details and guidance for accessing and managing The Things Stack Cloud clusters, including Console, API endpoints, OAuth, CLI setup, and IP address considerations.

      Enter your tenant ID and choose a cluster from the dropdown. This will update the rest of the page with that address so you can get easily copyable links.

      Your cluster address is:

      ..cloud.thethings.industries

      Console

      To learn how to get started with the Console, see the Console Getting Started Guide.

      Each cluster has a Console where you can manage gateways and end devices of that cluster. You can use any cluster with your Cloud account.

      The address of the Console for the routing cluster includes both your tenant ID and the cluster ID:

      https://..cloud.thethings.industries/console

      API Endpoints

      The Application Server, Join Server and Network Server APIs are all available in your routing cluster.

      ..cloud.thethings.industries

      However, the Identity Server APIs (/api/is/*) are only available in the eu1 cluster. This is because eu1 is the central cluster where entity registrations are stored.

      .eu1.cloud.thethings.industries

      Warning:

      End-Device Registry API requests or other Identity Server API requests to any cluster other than eu1 will fail.

      Account and OAuth

      User accounts are stored in the eu1 cluster. For registering users, logging in, changing your password and for performing OAuth flows, you need to use the following address:

      https://.eu1.cloud.thethings.industries/oauth

      Command-line Interface

      The Command-line Interface (CLI) needs to be configured with the address of the OAuth server and the gRPC addresses of the different servers. The addresses for OAuth and the Identity Server are always those of the eu1 cluster. The other addresses are typically of the cluster of your choice.

      Here you find the contents of the CLI configuration file for the cluster:

      oauth-server-address: 'https://.eu1.cloud.thethings.industries/oauth'
      identity-server-grpc-address: '.eu1.cloud.thethings.industries:8884'
      
      gateway-server-grpc-address: '..cloud.thethings.industries:8884'
      network-server-grpc-address: '..cloud.thethings.industries:8884'
      application-server-grpc-address: '..cloud.thethings.industries:8884'
      join-server-grpc-address: '..cloud.thethings.industries:8884'
      device-claiming-server-grpc-address: '..cloud.thethings.industries:8884'
      device-template-converter-grpc-address: '..cloud.thethings.industries:8884'
      qr-code-generator-grpc-address: '..cloud.thethings.industries:8884'
      
      credentials-id: ''
      

      See the CLI Getting Started Guide to learn how to get started with the CLI and working with configuration files.

      IP Addresses

      The Things Stack Cloud runs on AWS. See the AWS IP address range documentation for IP addresses of Cloud clusters.

      Note:

      IP addresses of Cloud clusters are not static, and may change over time. We recommend whitelisting the DNS address of your Cloud cluster if possible.
      ← Subscription via AWS Marketplace Custom branding →

      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