Access to the Frequently Asked Questions, where you’ll find maybe an answer and surely discover more about thingtia.cloud
Access to the Learning section. Demos and training material like videos about thingtia.cloud
Access to a form, let us your data and we’ll contact you. We can directly manage your needs or propose you to be contacted by a local partner if any in your region.
The thingtia.cloud is an Open Source sensor and actuator platform that collects, monitors, analyses and broadcasts the information. The platform is designed with a focus on performance, allowing the processing of millions of messages with a very fast response time.
Among its most important features, we could highlight:
The Iot Platform is based on sentilo that is licensed under LGPL3 or EUPL1.1 licenses.
We are constantly working on new functional, performance, and security improvements for the IoT Platform. You are welcome to browse the community forum to learn about tickets planned for future releases and stories filed for the roadmap
thingtia.cloud and thingtia solutions, SL do not guarantee or assume any responsibility or liability that the services will always function without disruptions, delay or errors. thingtia.cloud and thingtia solutions, SL disclaim any warranty that the services will be error free or uninterrupted or that all errors will be corrected. The services are provided on an “as is” or “as available” basis, without any warranties of any kind. You agree that use of the services is entirely at your own risk.
thingtia, short for thingtia solutions S.L., is a spin-off company of opentrends S.L., the crafter of sentilo©. It is a service aimed company created in early 2017 which offers an IoT Platform based on sentilo© software as a cloud instance, complemented with additional services such as training and support. Its employees are future oriented and business minded people, who are always looking for new opportunities.
Visit thingtia.cloud for more information.
Simple and quick. To get started with thingtia.cloud, access the Pricing page and choose an option.
The IoT Platform provides a publish/subscribe mechanism allowing external modules to subscribe to their desired topics. Once the data is received by the server, it is immediately transferred to the target system. You can easily develop a plugin that will enable integration with your proprietary analytics system.
All data structures are user-defined. You can use basic types(number, boolean, text) or define your own proprietary JSON structure.
The IoT Platform architecture provides the ability to quickly plug in different custom transport implementations. Currently, it provides an API-Rest and can use HTTP or HTTPs as application protocols. Further protocols will be supported in next releases.
Yes, if you use HTTPs protocol for your communications.
Linux distributions validated: Ubuntu, CentOS and RedHat
The IoT platform is designed to be horizontally scalable by distributing its core modules and agents in different servers. The High Availability should be targeted in next releases.
The catalog is stored in a document oriented database: MongoDB
The real-time data is stored in a in-memory database: Redis
The IoT Platform provides several connectors available for storing data in external repositories: Relational databases, Indexers (Elasticsearch) or Time series databases(OpenTSDB).
The IoT platform takes advantage of several of Open Source products and libraries, uses the following core major third-party components are HTTPCore, Tomcat, Redis and Mongo DB.
We cannot give an answer without having the number of sensors, actuators connected, the frequencies, the uses, etc.
The point we can remark is the big amount of ram needed in any case.
Absolutely. Since messages are based on user-defined data schemas which are hardware-agnostic, the messages can be shared across different devices regardless of the hardware platform. The only requirement is that the sensor or an intermediate gateway has the capability of publish data using the HTTP protocol.
Yes, you can send orders to your devices but they should have the capability of handling HTTP requests from the platform. Anyway, if this is not possible, the devices can also request for their orders through a pull HTTP request.
The general structure for the messages is defined by the IoT Platform, but the contents of the orders or data are user-defined.
The catalog configuration and the subscriptions are persisted for ever without any expiration date. The volatile data, like orders, data or alarms are stored in-memory and expires according with the policy according with your service plan. If you need to collect the data for any external treatment or persitency, you may use a connector for this purpose.