[ Case study ]Fleet Telematics

    Teflon Connect · Fleet Risk Platform

    Two no-code apps on two backends, rebuilt as one platform: a shared Supabase backend, a risk reporting web app and a live-alert mobile app. The live apps kept running throughout the migration.

    • Insurance-linked risk
    • Web + mobile on one backend

    Two apps, two backends, one slow experience

    The problem

    Teflon Connect turns vehicle telemetry into driving-behaviour scores, live alerts and insurance-facing reports for fleet operators, brokers and underwriters. It ran as two separate Bubble apps, a reporting web app and the Notify mobile app, each on its own Xano backend. This was the third generation of the platform in four years. Each app kept its own users, so a person could have access to one and not the other, and giving someone both meant a manual chain of steps across two backends. The apps were slow and performance complaints kept coming back. Access rules lived in app code rather than the database, and earlier piecemeal fixes never cleared the underlying problems.

    Four problems, one platform

    What we solved

    One person, one login

    One Supabase Auth identity per person, deduplicated by email across the legacy user stores. Staff invite anyone from a single screen, ticking reporting access, mobile access or both.

    Access enforced by the database

    Four roles, enforced by row-level security on every table. Each role was signed off with explicit tests of what it can and can't see, and a user only ever sees the fleets they're linked to.

    Alerts as they happen

    A live driving event goes straight to an authenticated Edge Function, which saves the record and sends the push notification at the same time. Tapping the notification opens the app on that event, and every acknowledge, snooze and call is audited.

    Risk, drilled down

    Underwriters, brokers and fleet managers each get a Teflon Reporting dashboard scoped to their own fleets. They can drill from the whole portfolio to one fleet and then to a single vehicle's events, and export the data or pull monthly reports.

    Teflon Reporting in action

    Teflon Notify in action

    What changed for Teflon

    Results
    • 01

      Teflon now runs one platform instead of two, with one login per person, one place to invite users and access rules the database enforces.

    • 02

      Web and mobile share a backend, so a change to the data shows up in both at once.

    • 03

      Four legacy subscriptions, two Bubble plans and two Xano plans, are being retired, and the saving comes through as each one winds down.

    • 04

      Live driving alerts reach phones as they happen, and Notify gives Teflon a new mobile offering to sell to its clients' fleets.

    How it was built

    Behind the build

    A shared Supabase backend

    One Postgres schema per environment with row-level security, Supabase Auth carrying the role in the sign-in token, and Edge Functions for sync, notifications, email, invitations and onboarding.

    Web and mobile, built to match

    Teflon Reporting is a Next.js web app and Teflon Notify is a React Native app for iOS and Android. Notify shipped as an update to the existing app store listings, so users simply updated the app they already had. The two apps share one database schema, which keeps them in step.

    Existing systems left where they live

    The platform reads from the Teflon API, an Azure scoring service, Azure Service Bus and a Dataverse faults-and-comments source, and sends email through SendGrid. During the parallel run, a read-only drift monitor compared old and new data, so nothing had to sync both ways.

    Ready to consolidate your platform?

    Let's discuss how we can deliver similar results for you.