Developer Support Iotic Labs

The essentials of the Iotic system

Iotic space

The whole system.
Iotic Space is a safe place for Things to interact, and includes the Space app (UI) and software layers.

Developer portal

Your gateway into Iotic Space.
It holds all of the information about your account and the public and private spaces which you have access to.


More information on the Iotic interface can be found in the following sections



Screenshot of the front page of the developer portal with links to My Spaces, How To, and Github


Private and public spaces

Ring-fenced areas of Iotic Space
Each space has its own permissions and requires an individual login. All Iotic users can access the public Community space and create public Things, but there are limits on how many private Things you can create. To develop large, private systems you will need to purchase a Private space.


You can view which spaces you have access to on the Developer portal Profile page.


Find out how to link your Iotic account to a Private space.



A Private Space enquiry form can be found on the Iotic Labs website.


Community Space

A public space which all Iotic users have access to.
There are usage limits on how many private Things you can create.

Space app

The GUI interface for Iotic Space.
It lets you manage all of your Things, agents, and interactions. It enables you to search The Space app is essential for creating new agents and searching the range of public data feeds available for you to use in your Iotic systems.

Each public and private space has its own instance of the Space app.


More information on the Iotic interface can be found in the following sections


Screenshot of the Space app with labels for the different menu functions



There are two types of Things: virtual Things, which exist in Iotic Space, and real-world Things, which are the devices and programmes which run outside of Iotic Space.

Virtual Things exist in Iotic Space, representing real-world Things at an abstract level and backed up by a local application. They can publish feeds and controls, or follow the feeds and controls of other Things.


How to create an Iotic Thing

Points and Feeds

Data published by a Thing.
Each data type which a Thing publishes is a point, and has a point ID. Points can be grouped into Feeds to make it easy to follow more than one point at a time. For example, a weather station might publish the points °F, °C, and humidity as a Temperature feed.


A published application which changes the behaviour of other Things.
A feed just publishes data, but a control contains logic which prompts a change in behaviour from the Thing following it. A control is also a point.


A gatekeeper which allows your Things to connect to an application.
You need to assign your virtual Iotic Things to an agent to allow it to securely communicate with a backend application and publish the data it is receiving. The agent creates an .ini file, which contains the security credentials, and then communicates with the Iotic registrar on behalf of your Things.


Find out more about Iotic Agents


The Iotic brokering service which checks security credentials.
The registrar brokers interactions between Things, checking that the .ini file contains the correct credentials, and that user has the correct permissions.


Creates virtual Iotic Things from backend applications.
When you locally run an application, it will create or the link the virtual Iotic Things, which will appear in the Space app.

IoticAgent API

API which allows you to write applications for Iotic Space.
The py-IoticAgent package, which includes the Iotic IOT.Client, needs to be downloaded to begin programming for Iotic Space.


Find out how to set up your computer.

By continuing to use the site, you agree to the use of cookies. more information

This website uses cookies via Google Analytics to give you the best browsing experience possible. No personally-identifiable information is collected about you unless you explicitly submit that information on this website. Click "Accept" to continue.