White Labeled Fleet Portals

The standard way, till now, for users of the RideView platform has been to integrate our secure RESTApis into their existing end-user dashboards, adding a layer of video and associated analytics on top of existing telematics data and workflows.

RideView dashboard image

The standard way, till now, for users of the RideView platform has been to integrate our secure RESTApis into their existing end-user dashboards, adding a layer of video and associated analytics on top of existing telematics data and workflows. And for good reason too, as giving fleets access to all their workflows under a single portal without having to switch context back and forth saves valuable time and effort for the fleet manager. Consequently, our APIs and webhooks have reflected all the data and analytics that can be efficiently displayed on our customers’ frontend applications.

As with other things, our thinking has evolved on this based almost entirely on customer feedback and request – we have come to the realization that consuming our web APIs need not be the only way for all customers to integrate our platform into end-user offerings. We have always had a fleet portal that we have primarily used for demos and pilots, and over time as our APIs have evolved and expanded, so has our portal. It can now be used as a fully-functional standalone fleet portal fleet that can be used to review, measure, and coach drivers effectively. The option of white labeling this portal helps our customers cut go-to-market times by half, at a minimum. Before we dive into its functionality, a few points around why this is significant:

  • Integrations take time, development resources are scarce and/or stretched. That should however not be an impediment to launch and validate a solution with an end-user. With white labeling, it is now possible to be up and running with a fully functional branded portal in less than 2 weeks:
  • Customer registers the domain of its choice
  • Shares the private key and SSL certificate for that domain with us
  • We host the white labeled website
  • We customize the portal with customers logo, font, and color schema
  • Optionally, we also help implement single sign-on to redirect into the customer’s authentication servers during login
  • It does not cost anything extra. Whether you use our API services or white label our portal (or both), our subscription charges do not change. We charge a nominal one-time fee for setting up the portal, and an AMC for maintenance and upgrades, and that’s it. No asterisks.
  • Some of our customers have used white labeling as an interim option to accelerate GTM while working in parallel on a deeper API integration into their backend systems. Others have used this as a long term solution. Our customers know best, and we are happy to support them either way.
  • Any enhancement to our platform becomes available first on our portal. From new AI triggered events, to innovative ways to review videos, our portal is where anything new sees the light of day. If your goal is to always be at the cutting edge of what our platform has to offer, white labeling our dashboards are a good bet.


Our goal with the fleet portal is to provide the most common video telematics workflows, in a way that is easy and intuitive. The main functionality is divided across three main views:


This has been designed to surface all the critical information a fleet manager needs to see at a quick glance (ref. header image):

  • Overall statistics, including a safety metric – Incidents/100 miles – and tracking if it’s trending up or down.
  • Driver leaderboards, showing both top drivers, and ones who need to be considered for coaching.
  • A highlight reel of critical incidents, sorted by severity. That is, the most severe incidents are surfaced at the top, and the user can scroll all the way down the list to view incidents of decreasing severity.
  • A drawer of video requests, corresponding to the DVR and Time-lapse DVR functionalities, in descending chronological order.
  • A breakup of incidents by category, and incident trends – overall, and by category.


This tab serves a dual purpose. It allows for a deeper dive into individual trips, and also allows fleet managers to make video requests on-demand:

  • The interface to make DVR and Time-lapse DVR requests, with options to configure duration, video resolution, and format.

  • A list of trips with status – ongoing, completed, pending upload of data, and other diagnostics data like camera mounting status coming soon.

  • A trip details page with expansive map-based views of routes with incidents and videos overlaid.


As we have spoken about earlier, incident configurations are an important tool in a fleet manager’s arsenal to keep data consumption in check, while still getting the most out of the platform. From setting event thresholds and configuring videos across a variety of parameters, to turning off incidents altogether, this is effectively the control room of the entire solution.

Other views include a driver-specific tab, that we are enhancing to include a list of coachable incidents shortlisted by a fleet manager, along with relevant notes. Our portal is responsive and designed to be consumed on large screens as well as tablets and smartphones, like most modern web applications. In addition, to monitor usage and derive insights from them, Google Analytics is instrumented into every critical interaction.

We realize that this is a journey and that we are early on in that process. We are committed to continuously evolving our portal in tandem with two driving forces – new features that our platform delivers, and best-in-class user interaction paradigms and workflows that fleets expect from a contemporary video telematics solution.

Reach out to us to learn more about accelerating your go-to-market plans for advanced video telematics.