Your identity. An existing foundation.

Your name.
Your driver
experience.

Put your fleet’s identity at the center of your ELD setup. Choose a shared app or commission a branded app, with hardware and licensed access to hosted software through ELD Factory.

YOUR FLEET / YOUR IDENTITY
NORTHLINEA FLEET BRAND, REIMAGINED
01 / BRAND SYSTEMELD
N↗NORTHLINEDRIVER WORKSPACE
ONE FAMILIAR IDENTITYYour next mile
starts here.
YOUR WORKSPACEDriver logbook →Vehicle details →Company support →
YOUR NAME ON THE EXPERIENCE
Branding illustration · fictional fleet and app screens
Custom ELD by General Software Company LLCA choice of two approaches

Start with the experience you need

Your own ELD identity.
Two ways to present it.

A separate app is a branding choice. First decide whether your drivers need a dedicated app under your name, or whether the shared-app approach fits your operation.

01 / SHARED APPLaunch

Keep the start
straightforward.

Use the shared app and hosted platform under your organization’s ELD identity. Avoid commissioning a separate app.

$2,500one-time plan setup
  • Your workspace on the hosted platform
  • Shared iOS and Android apps when released
  • Registration and self-certification assistance
Explore the Launch plan ↗
02 / CUSTOM APPBranded

Put your name
on the app.

Commission iOS and Android apps for your company, with a dedicated brand presentation and store-submission assistance.

$30,000one-time custom-app fee
  • Custom iOS and Android app development
  • Your company’s developer accounts
  • App Store and Google Play submission assistance
Explore the Branded plan ↗
THE SAME PLATFORM, EITHER WAY

$100/month platform + $15/month per asset.
Add $100 one-time setup per asset.

Both plans require a domain or subdomain your company controls for the operational portal. Domain routing is not yet implemented and must be arranged during onboarding. The $30,000 fee replaces the $2,500 Launch setup fee. Your agreement sets the final scope and charges. The per-asset price includes the hardware lease, backend, ELD service and shared apps when released.

More than a logo

Make the operation
recognizably yours.

The right starting point is the company behind the drivers. Your brand should make it clear who they work with and who handles their questions.

01

Your company identity

Plan the ELD name, organization details and driver-facing brand together. Use your trucking company’s identity or a separately structured offering.

02

Your administration

Give your team responsibility for people, equipment and permitted record workflows through licensed access to ELD Factory’s hosted backend.

03

Your support operation

Your staff supports drivers and manages logbook requests. ELD Factory handles platform technical faults; it does not make log edits for you.

04

Your launch decisions

Bring a domain or subdomain your company controls for your operational portal, such as eld.yourcompany.com. This is required for onboarding. Domain routing is not implemented yet; there is no self-service activation.

ELD hardware available through ELD FactoryHARDWARE + SOFTWARE / ELD FACTORY

The foundation behind your brand

Bring the identity.
Start with the technology.

ELD Factory produces the hardware and hosts the backend, with registration assistance alongside them. You receive access under license, not ownership of the software or rights to its source code.

CAN BUS 1 + CAN BUS 2BUILT-IN GPSPHONE / TABLET DATA RELAY

The device has no cellular modem. A connected phone or tablet relays its data. Hardware is leased; compatibility and complete-system qualification depend on your configuration.

Explore ELD Factory hardware ↗Understand the software foundation ↗

From brand decision to launch

A clear brief.
A responsible launch.

A brand is part of the system. The app, hardware, records and provider registration still need to work together.

  1. 01 / DEFINE

    Agree on the experience.

    Choose shared or custom apps. Confirm your fleet size, supported vehicles, brand assets and the people who will support drivers.

  2. 02 / PREPARE

    Build the launch package.

    For custom apps, prepare your organization’s developer accounts and D-U-N-S information. Agree on design, scope and the submission process.

  3. 03 / QUALIFY

    Validate the full system.

    Test the configuration and prepare provider self-certification and registration. Apple and Google make their own app-review decisions.

Plan with the current stage in mind.

The administrative workspace exists. Operational ELD recording, customer-domain routing and public app-store releases are still in development. Shared and custom app plans are launch offerings; neither is an operational app download today.

FMCSA’s process requires provider testing and self-certification; listing is not agency product approval. Read the provider guidance ↗

Before you commission an app

A few important distinctions.

Is a custom app the only option?

No. The Launch plan uses the planned shared apps. Branded adds custom iOS and Android development. Choose the approach for your fleet’s needs, with registration and complete-system testing addressed separately.

Does “custom” mean I own the source code?

No. The offering provides licensed access to ELD Factory’s hosted backend. A custom app package does not transfer software ownership or source-code rights. Your agreement defines the development deliverables and access.

Is app-store approval included?

Submission assistance is included in Branded. Apple and Google control approval. Developer account setup, organization information, app scope and review outcomes affect the process.

Are Custom ELD and ELD Factory separate vendors?

These websites are operated by General Software Company LLC. Custom ELD explains the branding choices; ELD Factory is the destination for the hardware, software and registration-assistance offering.

Where will drivers and admins sign in?

The operational portal is planned for a domain or subdomain your company controls. ELD Factory’s main-site account is for billing only. Neither customer-domain routing nor billing access is implemented yet.

What do I need before onboarding?

Your company details, a controlled domain or subdomain, a fleet and device scope, and a team that will support drivers. For custom apps, also prepare organization developer accounts and D-U-N-S information.

Make it yours, thoughtfully.

Start with your fleet.
Build from there.

See the platform and choose the app approach at ELD Factory.

Explore the ELD Factory plans ↗