With every version of Connhex you'll get:
- a state-of-the art data collection infrastructure. Simply put, this is an entity responsible for receiving data and storing it efficiently into a database
- every service included in Connhex Cloud
- Connhex Control: Connhex's device management application. Think of it like an admin-level device management application for all the devices connected to Connhex: you can see what messages are coming from each device, send commands and configuration to devices
- out of the box Grafana integration to create custom dashboards
Connhex AI and Connhex Edge licenses are billed separately instead.
Connhex has been designed to be the foundation for your product, with an emphasis on "your". Moreover, Connhex is not yet another white-label platform: if you're using one of those, you can probably customize the both the logo and the branding - but your most knowledgeable customers will still be able to tell what white-label platform you're using.
Needless to say, we are very careful in sharing information. Some of the companies using Connhex were gracious enough to provide a testimonial: this is, of course, optional. Every success story was shared with the customer involved before publication.
It really depends on your needs. A few examples:
- if you plan to use Connhex to gather data and create dashboards, you can leverage Connhex's Grafana integration. Let Connhex do the heavy lifting for you - getting data from devices into a database - and build your own dashboards to visualize those data. A typical use case for this is the creation of internal dashboards to monitor company equipment
- if you need to create a complex web application that includes more advanced logic than simply collecting and visualizing device data - think users management, handling user-devices associations, generating reports - you'll need to hire a software development team, typically a software house or a web agency. The advantage in using Connhex is two sided, the first being cutting down time to market, since developers be able to use all the additional services included in Connhex through API calls. The second one deals with demand and supply: there are many great companies that can develop beautiful apps, less of those know all the nitty-gritty details involved in getting data from intermittent sources and storing it efficiently. By choosing Connhex, you are expanding the pool of potential suppliers for the solution and lowering the total cost dramatically.
- if you need to create a mobile app, all of the previous still applies with a single exception - you'll probably need to hire dedicated mobile developers instead of a standard web agency
These are just examples: if you're not sure whether your solution could benefit from leveraging Connhex or not contact us and we'll take a look at it together.
The main difference between those two versions is the performance you'll be getting. Approximately speaking, there are two factors that scale the cost of a data collection infrastructure:
- how much data is involved
- what is the availability required for the infrastructure. For example, are you okay with the system being down for a few hours in a year or not?
Connhex Enterprise is engineered to auto-scale as the data flow goes up, whereas Connhex Standard has been optimized to work with relatively low hardware resources - this is why Connhex Standard is not simply a shrinked down version of Connhex Enterprise.
Of course you can. If Connhex Standard is hosted by you, just get in touch and we'll provide the migration tools - and support if necessary. If Connhex Standard is hosted by us, we'll take care of migrating all of your data.
The short answers is: yes, but.
You can definitely piece together many open-source projects and write some glue-code to connect them together. You can also write it yourself from scratch. However, besides the fact you'd be giving up on all the optimizations we spent years to achieve, there are a few things to consider:
- open-source components are typically developed in isolation. While this is why open-source is great for lots of infrastructural stuff (we didn't write an MQTT broker from scratch, rest assured!), you can't build a great product by forcing together pieces that are not intended to work this way. This is another reason why, if you decide to go the in-house route, you'll need to write a lot of it yourself.
- sad as this is, open-source funding is a hard problem in itself. You should also factor in the risk of the project you're using to be abandoned in the future
- creating something is just a fraction of the work. The real deal is testing it, smoothing out edge cases and making sure it's production-grade
- once you bring a project in-house, it immediately becomes both an asset and a liability. You should compare the benefits of building it yourself with the costs of monitoring, maintaining and updating it. Do you have a dedicated team or do you need to build one? What's your core business and where are you subtracting resources from?
Keep in mind the total cost of ownership: you'll need to code your solution, test it, validate it, monitor it, maintain it and support it.
The difference between an edge and a device is actually very simple. An edge is a physical electronic device that is running Connhex Edge, while a device is a generic object sending messages to Connhex and receiving commands from it. In short, you can think of edges as super-powerful devices that leverage Connhex Edge's functionalities.
GDPR is a commonly used shorthand to identify the Regulation (EU) 2016/679 of the European Parliament and of the Council of 27 April 2016 on the protection of natural persons with regard to the processing of personal data and on the free movement of such data, and repealing Directive 95/46/EC (General Data Protection Regulation).
You can find the complete regulation here.
How we approach GDPR compliance is a prime example of what we mean when we say Connhex is an IoT suite, not a platform.
We offer a comprehensive solution for device manufacturers: legal aspects are just as important as technical ones if your goal is to provide a service to your users. GDPR compliance is one of those things that comes easy if one keeps it as a constraint during the initial design phase: otherwise there could be fatal flaws impossible to patch.
And if you're not convinced on the importance of protecting personal data just from a moral standpoint, sanctions can be quite heavy (see below).
No, you're not - and incidentally you won't be by choosing any IoT solution.
You should have a 360-degree view when reasoning about GDPR. For example, no one but your company can:
- adhere to the principles relating to the processing of personal data (Article 5). One above all: you are expected to only acquire data relevant to the purpose of processing (data minimisation, see also Article 25)
- establish whether a data protection impact assessment is needed (Article 35)
- designate a data protection officer (Article 37)
To the best of our knowledge: no, there isn't - nor it can exist at all.
If you have a role in deciding what data is collected, you are the data controller: there's no way any supplier can guarantee your compliance to GDPR - no matter what their sales representatives say 😉
In GDPR terminology, Compiuta is a data processor. This means Compiuta (or any other data processor) must:
- provide sufficient guarantees to implement appropriate technical and organisational measures in such a manner that processing will meet the requirements of the Regulation and ensure the protection of the rights of the data subject
- process the personal data only on documented instructions from the controller (you)
- ensure that persons authorised to process the personal data have committed themselves to confidentiality or are under an appropriate statutory obligation of confidentiality
- assist the controller by appropriate technical and organisational measures, insofar as this is possible, for the fulfilment of the controller's obligation to respond to requests for exercising the data subject's rights
- make available to the controller all information necessary to demonstrate compliance
For the complete list of obligations, see Article 28.
The GDPR includes consultation between the actions performed on personal data that classify as processing - see Article 4.
Since we need to maintain, update and support Connhex instances, we need to have access to database clusters.
We don't take this responsibility lightly: Connhex databases containing personal data are accessible only to a limited number of people inside Compiuta and we keep a log of any action performed when accessing them.
There are two ways Connhex helps you with compliance:
- by implementing tools that address specific obligations or data subject rights. For a first look at what those are, see the GDPR compliance map: you can also contact us to get information about design details of those tools, should you need it.
- uses best practices and state of the art approaches to ensure security of processing (see Article 32)
See Article 83: up to 20.000.000 € or 4% of total worldwide annual turnover of the preceding financial year, whichever is higher.
In short: no, at the moment we do not.
We are a small, independent and self-founded team with the goal to operate in a way that’s sustainable. Our business model is simple: we sell our product at a fair price and that's it. We believe this commitment to long-term sustainability is a responsibility to our customers, who can trust that we’ll continue to be here and leverage Connhex as a foundation for their products. We are focused on making Connhex better every day instead of spending time trying to upsell customers that have signed up for a free tier of our product.
This doesn't mean you should buy Connhex blindly. We:
- try to continuously improve our online documentation and use cases
- are more than happy to chat and help you understand if Connhex is the right product for you
- guarantee 30-day money back on all Connhex instances hosted by us, as long as you have not accessed our servers during this period
As of right now, Connhex Enterprise is priced differently according to a few factors - how many devices the application needs to handle, what cloud provider has been chosen and what availability is expected, to name a few. We are working to publish its pricing transparently: expect updates on this front - just contact us for the time being.
No, you don't. Just contact us before migrating the system and we'll generate a new license, while deactivating the previous one. If you want to clone Connhex on a different server, keeping two active installations, you need to pay an extra license instead. This may be the case if you want to provide two of your customers with two identical but separate platforms based on Connhex.
We usually charge a one-time fixed amount for each Connhex Edge license you get. Each license is tied to a single device, so it's not possible to move licenses between devices - or to share a license across devices. Updates to the Connhex Edge executable can be purchased at a discount for each license.Alternatively, we offer an annual subscription to keep your devices always updated with the latest Connhex Edge version: contact us and we'll be happy to discuss it.
Of course, we'd be delighted to. Just contact us and we'll get back to you.
We're definitely reachable by phone and ready to jump on a call if you'd like us to, but we prioritize product development and supporting current customers over new business. We don't have a dedicated sales team and reinvest all of the profits coming from Connhex into making it better.
To get the fastest response, you can contact us through any of the dedicated support channels we've shared with you. If you're not able to access those, just send us an e-mail and we'll get in touch with you.