Manage connected products in groups with name, description and tag. arranged by real-time device state, software version, technical details, logs, location, and high-end tools to control and monitor your fleet.More Information
Full visibility of the device fleet by your hierarchy of groups and sub-groups together with wide maintenance features and extensive information on each and every device, from name to description and current connection state.
From remote SSH or VNC accessing to deploy OTA updates and monitoring the device application, JFrog Connect provides an all-in-one solution that helps to maintain and manage IoT and Linux product fleet remotely with ease.
If the device's CPU crossed the defined limit or the device application crashed, with ten devices or thousands of them, JFrog Connect will send alerts to your account, enable you to quickly handle the current issue fast as possible.
Thanks to JFrog Connect software agent service running on the edge device, your product will be 24/7 managed and accessible remotely from JFrog Connect platform. The smart agent service will always run in the device background, even if no internet connection is available.
As part of JFrog Connect exceptional design, it takes just a few minutes to connect any type of Linux IoT device fleet to the platform, just before production or even for accessible deployed products. Combined with a simple option to include JFrog Connect on the cloned image.
Running on many different network environments, around the world, JFrog Connect security passive and active tools will make sure your edge devices are secured 24/7, remotely, with a single click.
View your entire product fleet in one place. Make significant decisions based on real-time data. Receive instant alerts in the event of issues, and view the corresponding log to debug and fix them quickly.
Make gathering information from your edge devices easy and efficient. View the last communication time of each device, as well as its real-time resource usage, application, and static details.
Split your edge devices into groups and deploy software updates gradually, for example by first allocating a 'Test' group and only rolling out the update to your 'Production' group after a successful test, or by using A/B test groups to try out different software on distinct groups of devices.
Create sub-accounts with restricted permissions: create a support account with view-only access, and a developer account with permission to connect to devices and deploy software updates or access the device shell. Enable two-factor authentication with SMS to make your accounts secured.