Frequently asked questions.

No. The SIM is fitted on the production line — soldered down for the MFF2 build, or inserted for the removable card — and the operator profile is loaded before the device is boxed. Units arrive sealed and ready. Nobody opens, fits and re-seals anything, which is where the $10–15 per unit re-packing cost used to go.

Two ways, depending on who is doing it. An installer at the vehicle powers the device on, scans the supplied QR code and enters the activation code. An office deploying a shipment opens eSIM management in FT Cloud and batch-activates the whole inventory list at once. Both are in the console demo →

Connectivity stops being on the critical path. Profiles are loaded and IMEI mapped to ICCID before the devices leave the line, so activating them is a list operation rather than 500 individual jobs. The trucks are the constraint, not the SIMs.

Yes. Streamax devices take a standard SIM and always have — there is no lock-in. The case for the eSIM is commercial and operational: no re-packing, no consumer SIM degrading silently at year two or three, and no truck roll to change operator. The full argument is on the overview →

The soldered MFF2 part is the default for sealed, high-vibration installs: no slot, no spring contacts, nothing to work loose or corrode. The triple-cut card is for deployments where somebody has to be able to take it out, or where you pre-provision per region. Same grade of silicon, same temperature range, same design life — the difference is mechanical, not functional. Both specifications →

It is specified to operate from −40 °C to +105 °C with a ten-year design life, and is qualified to ETSI TS 102.671 plus an extended JEDEC test set covering thermal cycling, humidity, salt atmosphere, vibration, shock and ESD. Certificates for the exact part in your device are available on request.

Remotely. A eUICC holds several operator profiles side by side; enabling a different one is a command from the subscription manager. The module stages the change and asks the device to refresh, so it lands on a clean re-attach rather than mid-upload. Nothing in the vehicle is touched.

No. The eUICC presents itself to the device as an ordinary UICC — the modem only needs to support the standard card application toolkit (ETSI TS 102.223), including REFRESH, and a data bearer the subscription manager can reach it over. Nothing above the SIM layer has to know the eUICC is there.

189 countries and territories, across 388 partner networks. The map shows how many networks stand behind each one. Open the coverage map →

The device is not tied to one operator. If the serving network weakens, loses the cell or fails to re-attach, it moves to the next best available network in the same country automatically — no configuration, no dispatch, and the driver never knows. (If you have designated a carrier manually for that device, your choice stands.) It costs you nothing extra: every network in a country is the same rate to you, so a carrier switch never changes the bill.

The eSIM attaches to the best-performing network in the new country on its own. There is no roaming surcharge — not a percentage, not a separate line. The rate simply becomes that country's published rate for the data used there.

Yes. You can designate a carrier manually — for one device or for a group of them — and that designation always holds. Unless you set one, the eSIM chooses the carrier with the best connectivity on its own, which is what most fleets want most of the time. Set it manually where a route, a customer requirement or a known dead spot means you need a specific network; leave it automatic everywhere else.

The rate card prices 28 destinations; we provision 189. If your countries are not priced on the pricing page, send the list and they will be rated.

No, and we would rather say so. Operator agreements, network sunsets and regulation all move it, so treat the list as indicative. If a route depends on a single network in a single country, have your Customer Success Manager confirm that specific footprint before you commit to it.

If the fleet is growing or the device count is uncertain, take the dynamic pool — it re-sizes itself as devices join, and your cost per device stays flat. If the fleet is stable and you would rather commit to a known volume and a known invoice, take the static pool. Neither caps an individual device; both cap the fleet total. Side by side →

Nothing happens. There is no per-device cap — the only constraint is the total across every device in the billing cycle. A camera that uploads three collisions in a week is covered by the vehicles that sat in the depot. That is the entire reason for pooling, and it is why per-SIM allowances strand data.

You are not cut off. Usage beyond the pool is billed as overage at the published overage rate of the country it was used in — not an averaged rate and not the most expensive country you touched. FT Cloud flags excess data in red and can alert you long before it matters.

On a dynamic pool the pool grows with them: each new device adds its allowance, and the next invoice reflects it automatically — no purchase order, no re-quote. On a static pool the block is what you bought, so more devices simply share the same data.

Honestly, it depends almost entirely on what you have configured to trigger an upload — event clips, scheduled uploads, how often anyone opens live view — far more than on the camera model. That is why the tiers are described by usage profile rather than by product. Send your trigger configuration and a realistic live-view habit and your Customer Success Manager will size it against fleets that run the same way.

Yes, between billing cycles, without re-contracting. Different depots can sit on different tiers at the same time.

At the start of the next billing cycle. Move a fleet from 3 GB to 5 GB today and it keeps running on 3 GB — same pool, same per-device allowance, same invoice — until that cycle ends; the 5 GB pool and its rate begin on the first day of the next one. FT Cloud shows both: the current plan, and the change booked beside it with the date it starts. Downgrades and cancellations work the same way, so a change made mid-cycle never splits an invoice. Two things do move immediately, because they are not plan changes: devices added to a dynamic pool bring their allowance with them, and suspending a SIM takes it out of the active count. See it in the console →

One pool, bought at your home region's rate. Data used in another country draws more of that pool, in proportion to what the country costs and never more than its list rate. There is no roaming surcharge and no second pool. Your bands are set in your quote and recalculated whenever a new quote is issued. Fleets with no home region can be quoted a single blended rate instead. The bands and a worked example →

Monthly, in USD, against the pool. Data only — devices, FT Cloud licensing and options such as private APN, fixed IP or VPN are quoted separately.

Checkout runs on Stripe, so the methods Stripe supports are available: card, bank account debit (ACH and its local equivalents) and wire transfer. Which ones appear depends on your billing country and the size of the invoice — a finance team that will not put a five-figure monthly bill on a card can pay it by bank transfer instead. Pick the pool and the tier in FT Cloud, pay, and the pool is live from the next cycle. Confirm what is enabled in your own tenant with your Customer Success Manager before you plan around it. See the flow →

No. Pricing on this site is indicative and subject to confirmation; a written quotation is valid for 30 days from issue.

The destinations your vehicles run in, the pool type and size you choose, the number of devices, and any data used beyond the pool, which is billed at the overage rate. A fleet that crosses borders buys its pool at the home-region rate and draws it down abroad by band. Your Customer Success Manager or Business Development Manager confirms the total in a written quote.

Suspend the SIM from FT Cloud and resume it the day the vehicle returns — no call to a carrier and no technician. Suspended SIMs are excluded from the active count.

In FT Cloud, in the Cellular section, beside the evidence and the tracking. There is no separate telecom portal to log into — the person who sees the camera problem is the person who can see the SIM.

Activate, suspend, resume and deactivate a SIM; batch-activate a whole inventory list; switch a device to a different operator profile; set caps, alerts and APN; and watch usage per device against its plan.

Yes — all three are available, and they are quoted separately from the data. Tell your Customer Success Manager what the security model on your side requires.

On the soldered part there is nothing to remove. On both form factors, IMEI lock refuses the profile in any device other than the one it was issued to, and every line carries an audit trail. If a device does go missing, suspend it from the console.

SIMs are deactivated and profiles can be removed remotely; the memory a profile occupied is released. What happens to the video and telemetry already in FT Cloud is a question for your platform agreement rather than the connectivity one — your Customer Success Manager can walk through both.