As you read articles in our Help Center, you will see references to the remoteit and connectd packages. While these packages are similar, there are some important differences to note. Both packages support incoming connections and bulk scripting (with one exception). However, there are some important differences which are summarized in the table and paragraphs below.
|package||Windows / Mac||Linux||console based configuration||web based configuration||P2P initiator support||Mass production ready
- remoteit is available for Raspberry Pi and other armhf Debian compatible operating systems. The headless desktop, which opens in a web browser, is used as the primary configuration method. The Command Line Interface (CLI) available as a secondary configuration method.
- Windows and macOS are supported with the Desktop application, and the Command Line Interface (CLI) available as a secondary configuration method.
- Peer-to-peer connection initiation is possible using the Desktop (where available), headless Desktop, or the CLI.
Bulk scripting support is not available on Windows.
- The connectd package supports the widest variety of Linux packages, including many types of Arm, x86/AMD and MIPS CPUs.
- Debian package files are supplied for Debian compatible operating systems, while a generic tar package is supplied for all other Linux types.
The connectd package supports the following configuration methods:
- Interactive installer script "connectd_installer"
- Batch installer script "connectd_register" - similar to the interactive installer except table driven to allow easily repeatable results for small quantities of devices.
- Mass production methods which allow you to prepare an OS image which can be cloned in manufacturing without further per-device interaction required. The devices will register and become active in your account the first time they are powered on with an active internet connection.
Note 1: Peer to peer initiator support is available by writing your own scripts.