Safety comes free.
The layer is the opportunity.
Every safety feature LumpiApp offers is free and hardware-optional — a rider connects straight from the phone or the watch, across manufacturers, no purchase, no subscription. Our hardware stopped being a gate and became what a rider buys because they want it. What's left to build is a cross-manufacturer connective layer on the rider's own phone — positioned for the day connected technology is required on these vehicles. We are building the safer, connected ride — better for the rider, and better for everyone sharing the road.
Two natural ways to arrive here: you make something for riders and want it on the ride — or a rule is coming and you need a layer that already works across brands. Both doors are open. This is the honest version: thesis and capability, not deployments.
Safety is free. It is not attached to buying anything.
A LumpIO or LumpIA device is no longer required. Celpon and Relo connect directly to the ride across major EUC manufacturers — the brands we've decoded are supported today; confirmed where we've had a vehicle in hand, widening with access. We didn't do it to be generous: a safety feature that costs money is a safety feature most riders don't have, and a layer that only works for our own customers is not a layer anyone can build policy on.
Identity. Their ride, their way.
LumpIO brains and LumpIA accessories are the owner's statement — bought because they're wanted, not because something important was locked behind them. Every safety feature is free for anybody — no purchase, no subscription, no account tier, no exceptions — and where a capability sits on the line between safety and convenience, it goes free. That's a rule we hold ourselves to, not a launch promotion.
Prohibition punishes the people who ride properly.
The direction of travel for personal electric vehicles is restriction and outright bans — and the people who lose most ride carefully and did nothing wrong. Society did not ban cars because some people drive drunk; it licensed drivers, registered vehicles, insured them, and taught people how to drive. These vehicles deserve the same path.
That path needs what cars have had for decades and these vehicles never have: a connective layer between the rider, the machine, and the systems that train, register, insure and hold people accountable — with the rider in the middle, deciding what leaves their own ride. That's the layer we build. We are not asking for anyone to be policed harder; the alternative on the table is prohibition, and prohibition takes the ride away from the people who were never the problem.
The day connected tech is required on these vehicles, it will have to work across brands.
A requirement, when one comes, lands on the whole fleet at once — including the vehicles already in riders' hands. Answering it brand by brand is slow and leaves that fleet out entirely. LumpIO is positioned to be the cross-manufacturer add-on that closes the gap. Read the cards below as what we are building towards. None of it is deployed, none of it is committed, and no authority anywhere has asked us for it — nor are we lobbying for a requirement. We are making sure that if one arrives, a rider isn't criminalised for owning a machine built before it.
One honest limit up front: where a vehicle already offers a sanctioned way to be held to a lower ceiling, the layer asks the machine to do the thing it was engineered to do safely. Where a vehicle offers nothing of the kind, the layer is advisory only — it warns the rider and records the excursion, and it does not improvise control of a self-balancing machine. Closing that gap for the fleet already sold is precisely the conversation we want to have with manufacturers.
Zone-aware speed ceilings
Where a local rule calls for a lower speed, the vehicle's ceiling comes down gradually — warned first, ramped smoothly. A ceiling, never a cut.
Thesis · capabilityRestricted zones, rider override
A restricted area brings the ride down to a safe crawl and asks the rider to stop. The rider can always override — and the override is recorded rather than refused.
Thesis · capabilitySidewalk detection
Where riding on a footway isn't permitted: walking pace, plus an audible presence cue — the same idea as the sound a modern EV makes reversing.
Thesis · capabilityA record the rider owns
A rider keeps their own record of their own ride. If they're hit, or blamed for something they didn't do, they can show what actually happened. It stays the rider's record. It is not a feed of anybody's whereabouts.
Thesis · capabilityRiding that counts in the rider's favour
How someone actually rides, worked out on their own device and shown to them first. If the rider chooses to share a summary, careful riding is finally worth something to them. Nothing leaves the device the rider didn't send.
Thesis · capabilityBuilt for the fleet already out there
Machines sold years ago can gain the layer without being redesigned, recertified or recalled. An add-on, not a new model year.
Thesis · capabilityEnforcement that throws a rider isn't enforcement. It's an accident.
These constraints come before any capability on this page, and we'd much rather a partner meet them here than halfway through a negotiation. We lead with safety and with riders' rights. If what someone wants is a kill switch or an always-on tracker, they want a different company.
Never an abrupt cut-out
A self-balancing vehicle that suddenly loses power at speed throws the person on it. Nothing we build will abruptly disable or brake one. Enforcement is a smoothly ramped speed ceiling, warned before it moves — and it never kills the motor.
AbsoluteThe rider override stays
A rider can always push past a restriction. Geofences are wrong sometimes and emergencies are real. Overrides are logged and reviewable; they are never blocked.
AbsoluteUncertainty biases towards not restricting
Position, mapping and surface classification are all imperfect. Where the system isn't confident, it does not restrict. Losing a signal must never mean losing the ride.
AbsolutePrivacy by construction
A rider's behaviour data is the rider's. We design for minimal, purposeful, consented disclosure, and prefer evaluating on the rider's own device over uploading where they went. Continuous surveillance of every rider is not the product — and the privacy architecture for anything authority-facing goes to privacy counsel before it exists, let alone ships.
Absolute · under counsel reviewWe'd sooner lose a requirement than ship a feature that can drop someone at speed or turn a rider's day into a record somebody else owns.
Compliance-readiness for the machines you already sell.
A connected-tech requirement lands on your whole catalogue at once — including every unit already with a customer. The answer is either a redesign per model, with recertification, or a layer that works across brands and rides on top of what already exists. We're building the second one. It doesn't ask you to change a design or put us between you and your customer: your riders keep your app, your brand and your relationship.
A conversation, not a contract
An hour on what a cross-brand layer would need from a vehicle, and where that helps you. No procurement, no exclusivity, nothing signed.
Start hereAn interface you define
The single most useful thing a vehicle can offer is a sanctioned, documented way to be held to a lower ceiling — specified and controlled by you — so the machine enforces it exactly the way you engineered it to. Without that, a layer can only advise.
Low askA unit to build against
A vehicle in our hands is how support gets confirmed properly on real hardware, and how any capability above stops being a slide.
Low askAn alternative to a ban: rider-respecting first, and workable second.
A ban is quick to write and hard to live with. The alternative needs three things that don't exist today: a way to express local rules to a vehicle, a way for the vehicle to respect them without endangering the person riding it, and a record — held by the rider — that lets an incident be settled fairly. That's what this layer is for. We'd far rather help a city write rules riders can live with than watch it write a ban.
Stated plainly: no jurisdiction has engaged us, we have no pilot anywhere, and nothing on this page is advice about what any law requires or is going to require.
Rules a vehicle can act on
Local limits and restricted areas expressed so the ride itself can respect them — graduated, warned, and always with the rider's override intact.
Thesis · capabilityEvidence, not surveillance
Enough of a record — held by the rider — to reconstruct an incident, without a live feed of where every law-abiding rider is. That distinction is the whole design, and it is not negotiable in a procurement.
Thesis · capabilityA path instead of a prohibition
Registration, training and a rider-held record give a city a workable answer that doesn't take machines off commuters who never caused a problem.
The argumentPrice the riding, not the category.
Cover for these vehicles rests on a category, a headline top speed, and an assumption — so careful riders subsidise careless ones, and many can't get cover at all. The layer gives the careful rider a way to show how they actually ride, and the training they've done — as much or as little as they choose to send. For a riding school, it turns a course into something that keeps paying a rider back. What we won't do is hand over a rider's movements: a summary a rider chooses to share, never a feed somebody subscribes to.
What would you actually need?
Tell us what a signal has to look like to move an underwriting decision, and we'll tell you honestly whether it can be produced without compromising a rider.
Start hereTraining that counts for something
Completed rider education as a durable, rider-held credential rather than a certificate in a drawer.
Thesis · capabilityConsent is the mechanism
Nothing reaches an insurer that the rider didn't choose to send. That constraint isn't a concession we're offering — it's the architecture.
AbsolutePre-launch. No signed partners. No pilots. Nothing dressed up.
This page is worth exactly as much as its caveats. lumpi.app is pre-launch, and no partnership listed or implied anywhere on our site is a signed or confirmed agreement unless we say so in plain words, with your name on it. What rides today is the app and the free safety layer. The compliance capabilities described above are not built and are not shipping — the safety constraints come first, and the privacy architecture goes to counsel before anything authority-facing exists. What we won't do is invent traction we don't have, or put your name on our site before we've earned it.
Where this is going — without inventing a calendar.
Free safety, multi-brand
- The app and the safety layer ride today, direct to vehicles from several makers, with nothing to buy.
Proof and guardrails
- More vehicles supported; the safety and privacy design for any enforcement capability written down, reviewed, and made public before a line of it ships.
The public campaign
- A backer / pre-order launch that puts genuine units in riders' and reviewers' hands.
The mandate conversation
- With riders already carrying the layer, the cross-brand case becomes a serious conversation with makers, cities and insurers — from strength, not from a deck.
Deliberately no dates. If you want to be part of an early step, the best time to talk is now — before the list gets longer.
We open small. You risk almost nothing.
Every partnership is sorted by how much we're asking of you — and we always start at the lowest rung. You don't have to believe the whole thesis to say yes to the first step.
Open integration
We build support for your existing product; you do nothing but bless it. Your gear or your vehicle gains a feature at no engineering cost to you.
Start hereA unit to build against
Send us one unit — gear or vehicle — and we'll build the integration properly, confirm it on real hardware, publish an honest public review, and list you as a first-supported device.
Low askA working conversation
For a city, an insurer or a riding school: no product, no procurement. An hour on what your rules or your underwriting would actually need, and an honest answer on whether we could provide it.
No commitmentBuilding together
Co-developed hardware, a compliance-ready lineup, a real business relationship. Earned, later, from proof — never an opening ask.
EarnedBATIS — the Fountain. A watering hole for riders, hosted by you.
Batis is Tagalog for a spring — an oasis. BATIS is a charging-and-vending station you host to draw PEV riders in: safe charging, a free air compressor, a shared toolset, a machine that sells cables and cold drinks. Not an integration — a placement: riders plan routes around where they can charge, so hosting one makes you a stop on the map. Rent or buy; the commercial shape is worked out per site, and nothing here is a committed price. The concept is early, and we'd rather tell you that than dress it up — the enquiry form below fits.
Send us the short version.
A partnership enquiry doesn't need a deck. Tell us, briefly:
- Who you are — what you make, govern, underwrite or teach.
- What you're imagining — what would yours do if it could speak to the ride?
- Where you'd like to start, and what you can offer — a dev unit, docs, a contact.
- How to reach you.
We read every enquiry, and we'll always be straight about where a conversation actually stands. You can also just email hello@lumpi.app.
Nothing on it is a public announcement, a committed timeline, a regulatory opinion, or an offer of investment. The compliance capabilities described are our thesis and what we are positioning to be able to provide — they are not built, not deployed, and not promised to anyone; no authority has requested them and we make no claim about what any jurisdiction requires or intends. Rider data handling described here is a design commitment pending privacy-counsel review. Partnership terms, if any, are agreed in writing — never implied by this page.