SkyLog Join the founding fleet

Fleet monitoring / South Africa

Built with the control room in mind

Your whole fleet.
One screen.

A control-room workspace for South African fleets. Starting with CarTrack, built to bring more tracker feeds together.

Join the founding fleetFollow the story

01 / Fleet

Start with the whole picture.

Veldspan Freight on the N1. Unit 214 brings a roadside exception into focus.

Context: Unit 214 · Scania R 560, BA 42 ZK GP, N1 Laingsburg to Beaufort West

02 / Context

Follow the vehicle.

Thabo’s Scania R 560 travels between Laingsburg and Beaufort West. Follow Unit 214 from the map to the road.

Incident: Unit 214 · Scania R 560, BA 42 ZK GP, N1 Laingsburg to Beaufort West

03 / Incident

A position needs a story.

BA 42 ZK GP. Stopped on the N1 near Prince Albert Road at 21:14 SAST. A roadside security incident needs review.

Vehicle: Unit 214 · Scania R 560, BA 42 ZK GP, N1 Laingsburg to Beaufort West
01 / Cab 02 / Lead body 03 / Rear body

04 / Vehicle

One rig. Three points of context.

Cab, lead body, rear body. Three hardware positions connect the vehicle’s physical context.

Signal: Unit 214 · Scania R 560, BA 42 ZK GP, N1 Laingsburg to Beaufort West
GNSS positioning Vehicle receiver Tracker provider Telemetry APIs Common state SkyLog GNSS positioning Position downlink Vehicle receiver Tracker APIs Tracker telemetry SkyLog Common vehicle state

Positioning downlink ≠ provider telemetry

05 / Signal

Different signals. A common view.

GNSS provides position. Tracker providers supply telemetry through their APIs. These are different paths.

Operations: Unit 214 · Scania R 560, BA 42 ZK GP, N1 Laingsburg to Beaufort West
SkyLog
Operations / Night shift CarTrack · Position feed
Veldspan Freight / Unit 214BA 42 ZK GPScania R 560 · Thabo
Priority review · VF-214

Roadside security incident

N1 corridor

Last ping 21:14:00 SAST
LaingsburgBeaufort WestPrince Albert RoadN1 Unit 214 · Stopped
33.09276° S, 21.57368° ELaingsburg → Beaufort West

Vehicle telemetry

Latest received
Speed0 km/h
Cab doorOpen
Last ping21:14:00
0km/h
Stationary
Ignition
On
Cab door
Open
Last ping
21:14:00
Geofence
N1 corridor
Position feedTrip records

Incident timeline

18 Oct 2026 · SAST
  1. Vehicle stopped on N1Position feed
  2. Cab door openedVehicle telemetry
  3. Security review queuedCase VF-214
Ready for client review

Position and provider context stay with the case.

Connected rig

3 nodes reporting
  • Cab21:14:00
  • Lead body21:13:58
  • Rear body21:13:59
Assigned toNaledi · Night control
Veldspan Freight · Unit 214Case VF-214 · Operator review

06 / Operations

Give the control room context.

The same vehicle and incident arrive together. Review the latest position, vehicle telemetry and case timeline together.

SkyLog
Client workspace · Read only CarTrack · Position feed
Veldspan Freight / Unit 214BA 42 ZK GPScania R 560 · Thabo
Case received · VF-214

Roadside security incident

N1 corridor

Last ping 21:14:00 SAST
LaingsburgBeaufort WestPrince Albert RoadN1 Unit 214 · Stopped
33.09276° S, 21.57368° ELaingsburg → Beaufort West

Vehicle telemetry

Latest received
Speed0 km/h
Cab doorOpen
Last ping21:14:00
0km/h
Stationary
Ignition
On
Cab door
Open
Last ping
21:14:00
Geofence
N1 corridor
Position feedTrip records

Incident timeline

18 Oct 2026 · SAST
  1. Vehicle stopped on N1Position feed
  2. Cab door openedVehicle telemetry
  3. Security review queuedCase VF-214
Ready for client review

Position and provider context stay with the case.

Connected rig

3 nodes reporting
  • Cab21:14:00
  • Lead body21:13:58
  • Rear body21:13:59
Shared by operationsNaledi · Night control
Veldspan Freight · Unit 214Case VF-214 · Read only

07 / Client

Keep the case connected.

Veldspan Freight receives the same vehicle, position and review context in one case.

01 / FleetScroll to follow
Geography: Natural Earth · © OpenStreetMap contributors / ODbL data

02 / From a feed to a decision

Different feeds.
One way to read them.

SkyLog’s adapter approach gives tracker feeds a common vehicle state. Provider access and compatibility are confirmed with each fleet before onboarding.

From tracker feeds to vehicle context

Position feed

Vehicle telemetry

  • BA 42 ZK GP
  • Unit 231

Trip records

Vehicle telemetry

  • Unit 227

Shared vehicle state

Operations workspace preview

Unit 214 · Scania R 560BA 42 ZK GP

Source
Position feed
Last received

The vehicle ID, source and last received time stay together.

Position updates and trip records enter the same adapter layer. Provider compatibility is confirmed before onboarding.

  1. 01

    Connect a supported feed

    Confirm provider access with the team. CarTrack is the starting point; compatibility comes before onboarding.

  2. 02

    Review the fleet in context

    Workspace preview. Bring vehicle positions and their last update together, so the age of the picture is visible.

  3. 03

    Investigate an exception

    Case review preview. Read the route, latest position and vehicle context together before deciding what needs attention.

03 / Start with what connects

Your tracker.
Let’s talk fit.

Integrations are being validated with founding fleets.

CarTrack

Documented production integration

Ctrack

Experimental · Confirm pilot compatibility

Another provider?

Ask about your tracker

Before you join

Good questions.
Straight answers.

Do I need to replace my trackers?

The aim is to work with existing tracker feeds. Start by telling us your provider and hardware setup. Compatibility and any provider access requirements need to be confirmed before onboarding; keep your existing contracts in place.

Which providers are connected today?

CarTrack is the documented production integration. Ctrack is experimental; live API compatibility must be confirmed before onboarding. Ask about any other tracker; its presence in your fleet does not imply current support.

Can I use the screen shown here?

The screens illustrate the proposed workspace. Join the founding fleet to discuss pilot availability and the workflows your team needs.

Will SkyLog send instant alerts?

Position feeds update through batch polling. SMS, WhatsApp, email and push alert delivery are outside the current pilot offering. Confirm monitoring and response arrangements with your existing provider.

What should I share in an enquiry?

Your name, work email and current tracker are enough to start. Company and fleet size are optional. Do not email passwords, driver records or sensitive routes. Ask the team about data access, storage and retention before sharing operational data.

Shape what comes next

Your control room
knows what’s missing.

Bring that experience to the founding fleet.
Tell us where your current tools leave a gap.

Join the founding fleet

Tell us about your fleet.

Compose enquiry email