With every Connhex plan you get:

• a state-of-the art data collection infrastructure, with unlimited devices and unlimited data support. Simply put, this is an entity responsible for receiving data and storing it efficiently into a database
• every service included in Connhex Cloud, with limits and features specified in the {pricingPage}.every service included in Connhex Cloud, with limits and features specified in the pricing page.

The Enterprise plan includes a dedicated Connhex instance on your servers, with:

• 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
• Connhex Copilot: an AI copilot with direct access to databases, to extract insights and help with troubleshooting.
• Connhex AI: a set of anomaly detection and forecasting functionalities, automatically applied to data streamed from devices on the field.

Connhex Edge is included for free in all plans.

Absolutely not.

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.

Of course you can: only remember than if you choose to downgrade a lower data retention policy will apply.

The short answers is: yes, but.

You can definitely piece together many open-source projects and implement the missing functionalities Connhex offers. You can also implement 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. This is clearly just our perspective, and you’re welcome to challenge it! Look here for a detailed comparison between Connhex and custom projects.

We've shared our reflections here. In a nutshell, we will never open-source something if we can’t do it properly: right now we are still a small team, focused on serving our customers as best as we can. The overhead involved in managing and supporting an open-source project would be at the expense of the level of service we are currently providing.

Connectable is the general term we use to describe anything that can connect to Connhex (a bit of a tongue-twister, we know).

The difference between an edge and a device is actually very simple. An edge is a physical electronic device that is running Connhex Edge, whereas a device is a generally simpler 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.

You can read more here.

Like everything in software, it depends 😁. We wrote extensive documentation on this topic: you can find it here.