Skip to main content
Tapnet

How Tapnet is built.

A plain description of the platform’s architecture, security controls and support terms, for whoever has to sign the system off. Anything not covered here, ask on the diagnostic call.

Web
TypeScript end to end
Mobile
Android, offline-first; iOS coming soon
Support
Mon–Fri 09:00–17:00 SAST

Feeds in

  • Driver’s phone

    Signed POD and photos, captured offline

  • Cartrack

    Vehicle positions and ETAs

  • WhatsApp Business

    Messages to and from drivers

Tapnet

Dispatch, driver POD and invoicing on one record per load.

Goes out

  • Sage Accounting or Xero

    Invoices posted the day the POD is signed; payroll hours to Sage 300 People

  • Your customers

    Pay by OZOW, PayFast, Yoco, EFT or debit order

Architecture

Web dashboard
How it worksTypeScript from the database schema through the API to the front end.
Data
How it worksPostgreSQL. Multi-tenant: every database query is scoped to your team.
Workflow engine
How it worksEvent-driven execution with automatic retries. A failed run resumes where it stopped.
Modules
How it worksDeliveries, drivers, vehicles and the rest are self-contained modules, each with its own routes and components.
Driver app
How it worksAndroid today, with iOS coming soon from the same codebase. Deliveries are cached on the phone and sync on reconnect.
Mobile API
How it worksA dedicated REST API for the driver app, with small payloads and single-purpose endpoints.
Hosting
How it worksServerless deployment that scales with demand. Hosting, monitoring and updates are managed by Tapnet in every tier.

Security controls

Sign-in
DetailSession-based authentication with email and password or OAuth, on the web dashboard and the driver app.
Access control
DetailRole-based permissions: Owner, Admin, Editor, Viewer and Member.
Tenant isolation
DetailEvery database query is scoped to your team, so your data never mixes with another operator’s.
Credentials
DetailStored encrypted in the database. On phones, auth tokens are held in the device’s secure storage, never as plain text.
Transport
DetailEvery API call runs over HTTPS.
Security headers
DetailCSP, X-Frame-Options, XSS protection and HSTS.
Audit trail
DetailEvery user action, workflow run and API key use is logged.
Driver data
DetailDrivers see only their own deliveries, routes and vehicle. Location is tracked only during shifts.

Driver app

Platforms
DetailAndroid, built with Expo. iOS is coming soon from the same codebase.
Distribution
DetailGoogle Play, or an APK for direct enterprise distribution. Apple App Store coming soon.
Updates
DetailFixes are pushed over the air, without waiting for app-store review.
Offline
DetailDeliveries are cached on the phone. PODs are captured without signal and synced on reconnect.
Permissions
DetailCamera, location and storage are requested only when a feature needs them.
Backend
DetailThe same platform as the web dashboard: one source of truth.

POPIA and data handling

Tapnet is built to align with POPIA. Signed PODs are stored with a timestamp and audit trail, with SARS, CIPC and AARTO requirements in mind.

The data protection, data retention, security and breach response policies are published under Legal & POPIA. Questions about operator agreements or data handling go to wynand@tapnet.co.za.

Support

Hours
TermsMon–Fri 09:00–17:00 SAST
Critical issues
TermsEmergency on-call
Who supports you
TermsThe engineers who built your workflows
Included in every tier
TermsHosting, monitoring, maintenance and updates
Growth tier
TermsPriority support and faster changes

Technical questions?

Bring them to the free diagnostic call. You speak to the engineers who build and support the platform, not a sales team.

Book a free operations diagnostic