Skip to main content

How to become a partner

The path​

  1. Ask for the partnership. Click Become a partner and tell us a little about your company and the equipment you want to integrate.
  2. Meeting. Dersalis writes to the e-mail you gave to schedule a conversation and understand your case. To speed things up, do the technical survey below.
  3. NDA. After the meeting we exchange the confidentiality agreement, so we can share the technical material.
  4. Certification. With the NDA signed, we create your company in the Partner Portal and grant access. There you choose the architectures of your devices, download the right package, run the preflight on the device and validate the integration with our team.
  5. Integration agreement. Once certification is complete, we sign the integration agreement and your company becomes a certified partner.
  6. Rollout. Only after validating on a single device does the integration move on to the fleet.

What partners get in the portal​

  • Builds per architecture, with SHA-256, and the changelog of each release. You choose the architectures you use and are alerted, in the portal and by e-mail, only about releases that have a build for them.
  • Technical help center with the installation, API integration, MQTT and telemetry, and diagnostics guides.
  • Preflight: the report the device generates says whether it is ready and which build to use.
  • Support tickets, with logs and attachments, and the registry of your equipment.

Technical survey​

To prepare a compatible binary, we ask you to run the commands below on the MDVR itself (usually root or sudo is needed) and send us the output. If you do not have direct access to the device, tell us who does.

1. Architecture and operating system​

uname -m                # architecture: armv7l, aarch64, x86_64...
uname -a                # full kernel version
cat /etc/os-release     # distribution and version (may not exist)

2. Bluetooth​

# Is there any Bluetooth adapter visible to the system?
ls /sys/class/bluetooth/ 2>/dev/null || echo "no adapter found"

# Is BlueZ installed? Which version?
bluetoothctl --version 2>/dev/null

# Is libdbus available?
ldconfig -p | grep libdbus-1

If the device does not have built-in Bluetooth, let us know: a USB dongle is possible, but we need to know beforehand to point you to the model.

3. Device identification​

# Hardware serial (the first one that exists will do)
cat /proc/device-tree/serial-number 2>/dev/null
grep -i serial /proc/cpuinfo

Some devices have a manufacturer command to read the identifier. If yours does, tell us which.

4. Model and quantity​

  • Exact manufacturer and model of the MDVR.
  • How many devices of this model do you have in operation?

5. Connectivity​

  • How does the MDVR reach the internet (its own data plan, the operator's phone, something else)?
  • Is there a monthly data cap? dex-embedded was designed to be light, but this helps size it.

6. Your side of the integration​

  • What language or platform does your software run on the MDVR?
  • Do you have a test vehicle or bench?
  • Who is the technical contact for the integration?

After the survey​

With the answers, Dersalis confirms whether the device is compatible and guides the conversation through to certification. Already a partner? Go to the Partner Portal.