1 Cost down
Resolve faults remotely before they become RMAs. Live BLE telemetry, admin-triggered Copilot sessions, and three-phase battery-health scoring flag failing cells early.
Connected-vehicle platform · E-mobility OEMs and fleet operators
One platform.
Five returns.
Reduce aftermarket cost, unlock service revenue, improve retention, and launch faster — on your brand, your instance, your data.
Working platform, not slides
Live portal and app in every demo
Multiple BLE protocols, one app
4 rounds pen testing
4
Deployed surfaces
9
Lifecycle stages
300K
k6 load-tested
18
Regulatory zones
8
EU languages
4×
Pen testing
One platform — nine stages of the vehicle's life
- 1Factory QA
- 2Distribution
- 3Registration
- 4Active ride
- 5Diagnostics
- 6Anti-theft
- 7Lease & subscription
- 8Service
- 9End-of-life
Why OEMs choose Fienti
Five returns from one platform.
Point tools give you one. A generic IoT cloud gives you the building blocks and a two-year timeline. Fienti is built to deliver all five at once.
2 Revenue up
Turn connected ownership into repeat revenue. Warranty tracking, safety-recall alerts and consent-based profiles open channels for service, parts and upgrades — revocable by the customer, always.
3 Retention
Customers keep the app because it keeps their vehicle safer, healthier and more useful. Live stats, ride history, sharing, remote lock, theft alerts, firmware updates — reasons to open it every week.
4 Speed
A working platform exists today — portal, app, APIs, documented security posture. Rebrand, configure, integrate, launch. Weeks, not years.
5 Control
The customer relationship is yours — not the battery OEM's, not the app store's, not a generic fleet platform's. Your branded app and portal, your data, in your own Supabase instance.
The platform
Four surfaces. One system. Your brand throughout.
Operators, technicians, customers, and customers-in-recovery all need different surfaces. Fienti ships all four — on your brand, on your instance, sharing one data model.
1 — Operator
Operator portal
The office view. Seven tool groups, nearly thirty tools: scooter operations, remote diagnostics, battery health, supply chain, firmware management, org administration, compliance. A radial dashboard that opens only what a given role can see.
2 — Workshop
Workshop portal
Built for the bench, not the desk. Barcode-driven diagnostics, guided repair flows, battery health scoring, firmware push, parts and warranty lookup, scoped job queue per workshop. Works on the tablet the technician already carries.
3 — Customer
Customer app
Registration, BLE pairing, live ride dashboard, ride history, battery health, fault history, scooter sharing, remote lock, theft reporting, firmware updates, warranty, granular consent dashboard, GDPR data export. Rebranded per OEM.
4 — Customer web
Customer web portal
A full browser-based customer portal — scooter management, BLE connect, remote lock, anti-theft, ride history, sharing, ownership transfer, notifications, and fault history. Works as a standalone surface or as a phone-loss failover. No app reinstall required.
Full lifecycle
From the factory floor to end-of-life — one platform follows every unit.
Every stage has dedicated tooling. Nothing falls through the gaps between your ERP, your service desk, your support inbox and your customer app.
-
Factory QA
Serial decoding, model variant tracking, component batch records, final-test flows.
-
Distribution
Inventory tracking from factory through distributor to workshop. Distributor-level feature-flag overrides for regional configuration.
-
Registration
Country-aware registration. Age checks per jurisdiction. Email and phone verification. Terms versioning and per-category consent recording.
-
Active ride
Live BLE telemetry. Speed, battery, range, fault codes. Ride history with distance, duration and energy efficiency.
-
Diagnostics
Admin-triggered BLE capture with customer consent. Battery health with three-phase confidence scoring. Copilot live-support sessions.
-
Anti-theft
Owner-initiated remote lock. Theft reporting. Connection event logging with owner alerts on unauthorised connects.
-
Service & firmware
Workshop job queue. OTA firmware with region + hardware targeting. Signed binaries with SHA-256 validation and rollback plans.
-
Transfer & resale
Secure ownership transfer with OTP verification and 24-hour cool-off. Designed for sale, lease hand-back, and fleet redeployment.
-
End-of-life
Seven-day account deletion grace. Full GDPR data export. Telemetry anonymisation. Audit trail preserved for compliance.
Built for multiple markets
Built for multi-region deployment from day one.
Most platforms treat regions and languages as an afterthought — a second launch, a services project, a vendor ticket queue. Fienti was built multi-region from day one, because retrofitting it costs more than building it in.
1 Language & regional terminology
Every string in every surface is externalised — operator portal, maintenance portal, customer app, emails, SMS. Adding or adjusting a language is a data change, not a code release.
Regional terminology nuances are handled natively: "scooter" vs "moped" vs "kick scooter", "battery" vs "accumulator", formal vs informal address. Approved regional users can edit local copy themselves — no vendor ticket, no release cycle, no waiting on central marketing.
Right-to-left layout supported for Arabic and Hebrew markets.
2 Jurisdiction awareness
Registration is country-aware from the start. Age gates per jurisdiction. Terms versioning and category-specific consent recording per market. GDPR, CCPA and equivalent privacy surfaces rendered per region.
Per-region feature flags mean capabilities can be turned on or off per country without a code branch — comply with a local regulator on Monday, roll it out everywhere else on Tuesday.
3 Distributed management hierarchy
The distribution and maintenance hierarchies are built in — not bolted on. Regional administrators manage their own users, their own devices, and their own warehouses. A Spanish distributor sees Spanish devices; their technicians see Spanish job queues. Audit trails respect the hierarchy.
Central oversight without central bottleneck. Your Tokyo team shouldn't file a ticket with your London HQ to add a workshop in Osaka.
Capabilities
Every role on the operator side has their own tools.
For your workshop & service team
- Live BLE scooter access
- Battery health scoring & trending
- Battery barcode diagnostics
- Fault-code reference (E & F codes)
- Customer support Copilot
- Service firmware upload
For your fleet operator
- Fleet dashboard, scoped per region
- Geographic ride heat-maps
- Range simulator
- Workshop job queue
- Per-region feature flags
- Broadcast notifications to users
- Diversion alerts
For your factory
- Serial decoder & model lookup
- Battery barcode logging
- Component batch records
- Supply-chain inventory tracking
- Factory component serial history
- Firmware provisioning per HW version
For your customers
- Multi-protocol BLE pairing
- Live ride dashboard
- Ride history & stats
- Battery health view
- Scooter sharing with expiry
- Remote lock & theft reporting
- Warranty registration
- Granular consent dashboard (7 categories)
- GDPR data export
Hardware-agnostic · integration-ready
Your hardware. Your brand. Not locked in, not built from scratch.
Two alternatives dominate this market. Neither fits an OEM who wants to own the customer.
Vertical incumbents
Strong on hardware. Weak on OEM ownership. Their name sits next to yours on your customer's phone, and your roadmap depends on theirs.
Generic IoT clouds
Powerful, general foundations. They'll accept BLE telemetry and store it — then leave you to build the mobility workflows. An 18-month project for a team you probably don't have.
Fienti
Your hardware, whatever protocol — integrated, not replaced. Your brand throughout. Lifecycle tooling, ERP/CRM/warranty APIs and multi-BLE support already in place. New protocols added on request.
Data sovereignty
Your instance. Your data. We run the plumbing.
Fienti is not a shared multi-tenant SaaS. You don't share a database with a competitor, and your customer data does not pass through our operational systems in a way that would make it ours.
Dedicated managed instance
Each customer runs on their own Supabase Postgres project. Your data is physically and logically isolated — not row-level-separated in a pool.
Your data, legally
Data belongs to you. We operate the infrastructure under a Data Processing Agreement and act as your processor, not as a controller or data broker.
EU or global hosting
Supabase regions span Europe, the Americas, APAC, and more. Pick the region that fits your GDPR footprint or your customers' expectations.
Built in, not bolted on
Anti-theft, transfer, lease and subscription built into the platform.
Anti-theft
- Owner-initiated remote lock — scooter locks on next Bluetooth connection.
- Theft reporting — owner flag triggers automatic lock and status change across all surfaces.
- Connection event logging — every BLE connect attempt logged with privacy-rounded location; owner alerted on unauthorised connects.
- Diversion alerts — detect movement or location signals inconsistent with expected use.
- Component serial tracking — stolen parts can be identified and rejected at service.
- Phone-loss failover — the web dashboard lets a customer lock, report and transfer without the original device.
Sale · Lease · Subscription · Fleet
- Secure ownership transfer — OTP verification and 24-hour cool-off prevent wrong-person assignment.
- Fleet allocation — scooters assigned to fleets, ports, and zones with role-scoped access.
- Sharing with expiry — time-bounded access for lessees and subscription users.
- Factory & component serial pairing — trace any unit through every contract and custodian it passes through.
- Feature-flag tiers — unlock or restrict features per commercial plan.
- Seven-day deletion grace — customers return a unit and their data exits cleanly.
Security & compliance
Built for procurement audits, not just for developers.
The site you're reading was built to pass those checks. The platform behind it was built the same way.
Tested
Four rounds of penetration testing. Dedicated BLE security review. Firmware integrity testing with SHA-256 validation. Edge-function unit tests under security scope. Independent third-party review on file.
GDPR-ready
Record of Processing Activities, third-party processor list and executive security summary — all translated into eight EU languages and supplied on request. Per-category consent, withdrawal tracking, and seven-day deletion grace.
Scaled
Reviewed under 300,000-user load. Row-level security hardened across multiple rounds. Firmware access levels enforced at the database.
- CSP: strict
- HSTS preload eligible
- No cookies
- No third-party trackers
- Contact form on our own infrastructure
.well-known/security.txtpublished
How deployment works
From agreement to go-live in four phases.
-
1 — Brand
Your logo, palette, domain, app-store identity. Terms, privacy policy, and in-app legal are configured to your jurisdiction.
-
2 — Integrate
Your hardware protocols plumbed into the BLE layer. Your ERP, CRM, warranty and finance systems connected via documented APIs. Regional rules, age limits and firmware zones configured.
-
3 — Launch
Mobile apps submitted to the stores under your publisher account. Operator portal deployed to your domain. Dedicated Supabase instance provisioned in your chosen region.
-
4 — Operate
We operate the platform under an SLA: infrastructure, patches, security rounds, firmware pipeline, integrations. You run the product; we keep it running.
Founder profile
Built on 35+ years of hands-on connected-device work — through every protocol generation.
Serial, RS-485, GSM modems, Bluetooth Classic, BLE — and most recently a production connected e-mobility platform deployed by a European OEM across multiple countries and tens of thousands of devices. Aftermarket-cost battles, OTA rollout discipline, GDPR reviews, factory-line QA, and the boardroom conversation when a connected project is a year late — scar tissue, not theory.
The commercial record matches: multiple board directorships, several ventures scaled, one taken to public listing. Delivery backed by established specialist partners for audit, firmware validation and mobile release — named on request.
Every platform I evaluated asked the OEM to choose. Cost, or revenue. Speed, or control. Safety, or brand ownership. I designed Fienti so no one has to make that choice again.
Foundation partners
We're taking a small number of foundation partners through 2026.
A foundation partner is an OEM or fleet operator who goes live in our first wave. It's a better deal than being customer number four-hundred on a generic platform — and it's a better partnership.
1 Preferential terms
Meaningful commercial discount on the first 24 months, locked in at renewal. Lower cost of ownership for the lifetime of the relationship.
2 Roadmap influence
Quarterly product council direct with the founder. Your priorities shape the roadmap. The platform bends toward the problems you actually have.
3 Senior attention
Your deployment is run by the founder who designed the platform — not a ticket queue. Direct line through launch and the first year of operation.
4 Reference on your terms
You stay anonymous until you choose to be named. When you're ready, we'll co-author the case study together.
In return, we ask for open feedback, a genuine working relationship, and a willingness to be a named reference when the time feels right. If that sounds like the right shape of engagement, let's talk.
Let's talk
Book a 30-minute demo.
Tell us a little about your operation and we'll come back within one working day. We'll show you the live portal, the live app, and talk through how we'd shape an instance to your brand, hardware, and commercial model.
Prefer email? [email protected]
Not ready for a call? Explore the live operator portal → or read the security posture.