Driver app integrations

Roles and responsibilities

General Software Company LLC licenses ELD Factory backend software and assists client ELD providers with registration. For each tested ELD offering, the client company is intended to be the registered provider and remains responsible for that offering.

We recommend Annex Orbis as a driver app. Annex Orbis Inc is a separate company; using its apps requires a direct contract under its terms.

Read the Annex Orbis external ELD provider guide for its connection setup and current driver access.

Other driver apps may be considered through a partner agreement, an adapter and a tested supported configuration. An API key alone does not make an arbitrary app compatible.

Connect company setup

These steps describe the supported integration in existing administrative test workspaces. Customer-domain activation is still in development. Each new customer must connect a verified domain or subdomain before operational access is enabled; existing test workspaces retain their issued administration address during this transition.

1. Open the administration address issued to your organization and use your authorized provider workspace.
2. Select “Create connection key” and save the key securely. It is shown only once.
3. As an authorized company owner or administrator, enter the key in the provider connection-key field in Annex Orbis ELD settings, then select “Link company”.
4. Confirm the status reads “Linked · recording not active”.

The setup key connects company metadata. It is not driver authentication and does not by itself grant access to driver records.

Connect your driver account

1. Ask your ELD Factory administrator to set up your driver account and invite you to claim it. Open your organization’s administration address and claim your account there.
2. In your driver workspace, open “Connect Annex Orbis”, choose the connected company, and create a one-time invitation. It is shown once and expires in 10 minutes.
3. Sign in to your own Annex Orbis driver records, paste the invitation, and select “Connect my account”.
4. Return to your provider workspace, refresh your links, and confirm the displayed Annex account and membership belong to you. Then refresh the link in Annex Orbis.

After confirmation, you can review your own ELD Factory manual records, enter a current manual duty status, add annotations, and certify a day in Annex Orbis. Make historical corrections and manage provider and carrier settings in ELD Factory. Either side can revoke the driver link.

A current status entry uses the time you provide and must reach the hosted provider within five minutes. Backdated entries belong in ELD Factory. A complete operational ELD configuration still needs qualified device recording, offline behavior, roadside inspection and transfer support.

Registration and self-certification

FMCSA describes registration and self-certification for a tested, compliant ELD offering. Self-certification is not FMCSA product approval. Its white-label FAQ explains that branding partners can use certification performed by a white-label company; see also FMCSA’s ELD provider resources.