Thinger.io Cloud

Subscribing and Deploying a Cloud Instance

This section describes the process to deploy a private Thinger.io Cloud instance within minutes by just accessing the Pricing Page. This pricing is also a deployment system that will setup a private Thinger.io Server instance within minutes, just following the next three steps:

1. Select a license

Private cloud instances can be deployed with different licenses, depending on the requirements, like host performance, bandwidth or other platform features like branding, custom domains, additional support, plugins, etc. Once the cloud provider is selected, then it is necessary to select the desired license, as shown in the image below:

This pricing includes the software license and all cloud expenses. Note that yearly subscriptions offer a discount over the monthly one.

The next table shows all the different features provided by each license as well as a desirable purpose specification. It is possible to select one license and change it in the future using the subscription management portal.

Features	SMALL	MEDIUM	LARGE
Devices	100	1000	2500
Plugins	1	3	5
Multi-tenant		✓ (Up to 5)	✓ (Up to 15)
White-labels		✓ (Up to 1)	✓ (Up to 5)
Server size	M1	M2	M3
Extended Features	Extended	Business	Business Plus
Support	Community	Extended Support Available (Paid)	Extended Support Available (Paid)
MQTT Support	✓	✓	✓
Daily Backups	As a service	As a service	✓

Additionally, all these subscriptions provide:

• Unlimited Data Points, only limited by the underlying instance storage

• Advanced Analytics, meaning that aggregation windows are provided

Dedicated server

Size	CPU	RAM	Storage	Network Transfer
M1	2	1GB	40GB SSD	2TB
M2	2	4GB	80GB SSD	4TB
M3	4	16GB	320GB SSD	6TB

Additional features

	Small	Medium	Large
Dashboards	Unlimited	Unlimited	Unlimited
Data Buckets	Unlimited	Unlimited	Unlimited
Endpoints	Unlimited	Unlimited	Unlimited
Access Tokens	Unlimited	Unlimited	Unlimited
File Storages	Unlimited	Unlimited	Unlimited
Asset Management	Unlimited	Unlimited	Unlimited
Projects	Unlimited	Unlimited	Unlimited
Syncs	Unlimited	Unlimited	Unlimited
Claims	-	Unlimited	Unlimited
Products	1	5	10
Proxies	-	5	10
Oauth Clients	-	3	5

2. Configure license

After selecting the license and completing the payment process, you will receive an email containing a link to a page where you can choose the desired base hostname and deployment region.

Instance license preferences

These options are described in more detail in the following:

• E-mail: This is the e-mail address that must be used when creating the Thinger.io account in the private instance deployed. It will be the main account with admin privileges, allowing to create (if contracted) new users, domains, brands, etc. It does not need to match the billing e-mail address.

• Hostname: Enter the hostname for your private IoT instance. This hostname will always be accompanied by the subdomain "aws.thinger.io" to access your host.

• Region: Cloud providers provides servers in different geographic locations. This option allows to select the closest region to your business or project in order to minimize latency between the instance and the devices, users consuming information, etc. It is recommended to select the closest region to the project location.

3. Instance deployment

After the configuration has been done, a launch process will execute to deploy your environment, and a progress bar will be shown to give feedback on the current status of the deployment.

Billing email

Once the process is done, you may follow the Steps After Cloud Deployment.

Steps After Cloud Deployment

As soon as the deployment process has been completed, a confirmation email will be sent to the Admin E-mail configured in the configuration process, meaning that the server is completely ready to be used. To start working with it, just follow the next steps:

First Login

1. Access the server by writing the configured domain in a web browser, for example: https://acme.aws.thinger.io. This step should show you the Thinger.io login screen.
2. Note that this server has never been accessed before, and it is a completely isolated instance so there is not any user account created. Then, it is necessary to click on Create an accountbutton, and fill the form to create a new user profile using the Admin E-mail address provided while configuring the instance (any other address will not be authorized to sign up).

3. After creating the new account it is possible to access the new server. It is not necessary to confirm the mail address.

Device Connection

When working with a private Thinger.io Cloud Instance, it is necessary to point your devices to the newly created hostname. If you are using the Arduino or Linux client libraries, i.e., for Arduino, ESP8266, ESP32, Raspberry Pi, etc., you should add a definition on top of your code to point to your host. So, modify your sketch like this:

#define THINGER_SERVER "acme.aws.thinger.io"

// the rest of your code goes here

If this host definition is not provided, your devices will try to connect with the public instance.