A dedicated plugin enables the visualization of your flespi items parameters in Grafana.

How much flespi storage will your telematics project need?

Revolutionizing telematics with tailored AI assistance.

MQTT broker Fast, secure, and free public MQTT broker with MQTT 5.0 support, private namespace, WSS, ACLs, and rich API. MQTT as a remote distributed storage system MQTT as the foundation for event-driven web-application design Check broker changelog to track the development progress of this wonderful service. Join in to establish MQTT connectivity with flespi Login/Register Perform and scale better with MQTT 5.0 The number of sensors in the IoT and M2M systems is skyrocketing. The flespi team has been working hard to add the MQTT 5.0 specification support into the broker to enhance the productivity and scalability of your projects. Check our MQTT 5.0 compliance checklist for details. Be the boss in the isolated MQTT namespace Each flespi user operates in an isolated MQTT topics namespace. It's only you who chooses how to name message topics and what kind of hierarchy to use. Operate the broker via REST API Manage sessions, publish messages, read and delete retained messages, and access logs via a flexible REST API. Fine-tune access to topics We take security and privacy seriously. To make sure each subscriber gets the data they need but cannot cause harm by their negligence or accidental actions, we devised a flexible access control system. It allows creating tokens with different ACLs and lifetime settings to finely customize what different parties can access within a topic. Use shared subscriptions for easy load-balancing When incoming messages start heavily bombarding the handler of your business app, you might lose data. We don’t want that! flespi offers shared subscriptions and even their extended sticky version to spread the load across multiple service workers in a smart manner. Never hit the speed limit It’s frustrating when your technological partner can’t live up to your needs. We don’t want to be a bottleneck as your business grows. flespi MQTT broker can receive one million messages per second and send three million messages per second. Impressive, huh? Stay safe with SSL-protected MQTT and WS connections We care about the security of the messages you entrust to our MQTT broker. That’s why we support MQTT over SSL and MQTT over Secure WebSocket. Do testing & debugging easily Our MQTT Board MQTT 5.0 client tool makes playing with MQTT connections handy thanks to a well thought-out interface and functionality. 5 easy steps to setup flespi MQTT broker Create free account on flespi.io Create an authorization token Connect to mqtt.flespi.io via TCP or WebSocket Authorize with flespi token as user name Subscribe/publish to any topic flespi MQTT broker configuration Host mqtt.flespi.io Port MQTT over TCP: 8883 (SSL) or 1883 (non-SSL) MQTT over WebSockets: 443 (SSL) or 80 (non-SSL) MQTT version 3.1, 3.1.1, 5.0 QoS supported QoS 0, QoS 1 REST API Yes, it's possible to publish messages, read and delete retained messages, manage connected and offline sessions, and access broker logs via MQTT broker REST API ACL Yes, topics access is adjustable via token ACL setting Shared subscriptions Yes, implemented according to MQTT 5.0 specification. Allows load-balancing published messages between multiple subscribers in the same shared group with sticky distribution scheme on top of this Retained messages Yes, with limited storage according to restrictions Logs MQTT broker logs available via either REST API or MQTT Authorization Username Password ClientID your flespi token not used * any ** * Alternatively, if it's more convenient and secure for your client library, you can put a flespi token into the Password field instead of Username. For MQTT clients with a 16-byte limit on username or password fields, you may use special authorization. ** ClientID should be unique for each connection. If you have few connections with the same client id they will be disconnected by the Broker in round robin fashion. flespi MQTT broker specifics Feature Explanation Topics names Use any topic names except those starting with "flespi/...". Topics selectors When using HASD database for storage purposes or in general to achieve maximum performance on large volumes we introduced topic selectors in subscriptions. Here's how it works: if you subscribe to 'topic/a,b/e,f/field', you end up with retained and online messages from 'topic/a/e/field', 'topic/b/e/field', 'topic/a/f/field', 'topic/b/f/field'. The logic of the subscription is similar to 'topic/+/+/field' but the first '+' wildcard will filter out all topics except 'a' and 'b' and the second '+' will filter out all topics except 'e' and 'f'. Wildcard deletion of retained messages If you publish a message with an empty payload to a topic that contains wildcards ("#" or "+"), flespi will perform bulk deletion of retained messages that match the published topic mask. Retained messages and SUBACK When you subscribe to a topic that has matching retained messages, the broker delivers all of them before sending the SUBACK for that subscription. The SUBACK therefore marks the end of the retained snapshot, so you can rely on its arrival to know the full set of retained messages has been received. If no retained messages match the subscription, the SUBACK is sent immediately. Shared group sessions storage If the message arrives at the shared group but no sessions are online, for clean=false or non-zero expiration timeout sessions that were previously subscribed to this shared group, the message will sit in the storage until such sessions connect again. As shared groups are mostly used for load balancing, this feature prevents any data loss when all such sessions are offline for whatever reason. Sticky shared subscriptions In some cases, it is desirable to redirect specific topics to the same subscriber within the shared group (unlike in a traditional use for load balancing). This approach allows for implementing more efficient cache between shared subscribers. With 'sticky' shared subscriptions, you can specify the initial word position and words count to calculate the topic fingerprint, e.g. '$share/group_name:from:count/...' (a simpler form is '$share/group_name:count/...' for zero-based 'from' topics). The broker will calculate the topic fingerprint and assign it and future topics with the same fingerprint to the same subscriber. "timestamp" user property (publish) If not set by the publisher flespi broker will attach this property to the published message with the current UNIX time value. This property is used to sort which message will be the last in retained storage. "token_id" user property (publish) Every message published by the user is signed by the broker with a "token_id" user property containing the ID of the flespi token used by the sender for authorization. This property can be used on receivers to distinguish message senders. "modified_since" user property (subscribe) If valid value is specified, the subscriber will receive only newer retained messages than the given UNIX timestamp. "cid" user property (publish/subscribe) ID of flespi account that originally generated this message. Upon subscribe it is possible to subscribe only to messages available to specified flespi account ID. "freeze_timeout" user property (connect) The broker treats a session as frozen when its outgoing queue is non-empty but the client stops acknowledging delivered QoS 1 messages (PUBACK) — its in-flight window stays full and nothing drains. A frozen session is disconnected after 600 seconds by default, so its queued messages can be redelivered when it reconnects. Set the "freeze_timeout" user property in the CONNECT packet (value in seconds, from 10 to 3600) to override the timeout for that connection. CONNACK user properties Session connection acknowledgment packet contains additional information about the session including ACL settings for the session authorization token and its current subscriptions. Number of subscribers to a topic Add a count_subscribers user property with 1 payload and publish a QoS(1) message. You can then find the subscribers_count user property in the received PUBACK. Message filtering Subscription filter format: $filter/cid={cid filter}&modified_since={timestamp}&payload={expression}&message={expression}/{filter topic}. cid - allow only messages from specific subaccount ID. modified_since - allow only messages with timestamp above specified value. payload - apply expression to filter message by its payload. Can be used to filter both simple payloads like string, number, boolean or complex payloads such as JSON objects and arrays. More details and examples here. message - apply expression to filter message by its timestamp, topics, user properties or payload(string only). Can be used to filter both simple payloads like string, number, boolean or complex payloads such as JSON objects and arrays. More details and examples here. MQTT limitations Broker accepts messages with maximum payload size of 60MB Maximum outgoing (pending to client) messages queue size is 256MB Maximum QoS=1 unacknowledged messages queue size is 100MB Maximum single retain message size is 16MB Maximum number of levels in the topic is 24 If using multiple topics per one subscribe/unsubscribe request, broker accepts maximum 64 topics in it Follow broker changelog MQTT client You may play with flespi MQTT broker via this mqtt.js-based MQTT client or try fully-featured MQTT client tool. Feel free to open multiple instances simultaneously — e.g. you may publish messages from one tab and subscribe to them from other tab. You may also subscribe to everything, e.g. # — this token provides read-only access to a couple of GPS trackers installed on vehicles that periodically update their positions. Connection Username: Client ID: Connect Publish message Topic (please use valid MQTT topic, should not start from '/'): QoS: 0 1 2 Message: Publish Subscription Topic: QoS: 0 1 2 Subscribe MQTT 5.0 client libraries Here are some MQTT client libraries created or complemented by Gurtam developers: MQTT.js — MQTT client for Node.js and the browser gmqtt — Python asynchronous MQTT client luamqtt — pure Lua MQTT client MQTT 5.0 compliance checklist Feature Description Status Shared groups Load-balancing; delivering messages to a single subscriber from the group Message expiry interval Limiting the messages TTL (for both queued and retained) Response topic Subscriber response to received topic (executing commands and getting response) Receive maximum Client limits the number of incoming messages sent by the broker Maximum packet size Client limits the max size of messages sent by the broker Topic alias Replacing a topic name with the 2-byte index (to save traffic) Will delay interval Delaying the generation of a will message Subscription identifier Client specifies own index upon subscription; broker specifies according to which subscription the message is sent to the client Join in to establish MQTT connectivity with flespi Login/Register

Telematics hub Connect IoT and telematics devices from multiple manufacturers to fleet management, IoT, or BI platforms. Integrate with ERPs, third-party platforms, and cloud IoT hubs. Run real-time analytics over your telemetry data. Power own telematics developments and custom software solutions. Check telematics hub changelog to track its development progress. Join in to start connecting IoT and telematics hardware with flespi Login/Register Stay flexible with multi-protocol support We can’t boast hundreds of supported protocols like some fleet management platforms do. We prioritize the order of protocols integration and grade the level of protocol support by demand. Check the protocols we are currently supporting. Have data at your fingertips with a lightning-fast telematics database Once your messages flow into flespi, the platform transforms them into the unified JSON format and saves in the database. We designed the database engine to store telematics data most efficiently and spit it back instantly. Stream data to multiple platforms simultaneously If you want several platforms (BI, ERP, fleet management, etc.) to consume data from your IoT and telematics devices for further use, fork the dataflow across multiple streams and customize the configuration for each destination. Access your data from various platforms via rich APIs Comprehensive REST API empowers you to manage all components and data transfers inside flespi from a third-party app. MQTT API offers fast and secure access to device messages, telemetry, logs, connection info, etc. Configure and run automated data analyses Let flespi post-process your telematics data, extract intervals based on your custom algorithms and calculate each message inside interval accordingly. Keep calm with 99.9% platform availability We care about your business and guarantee the “three nines” platform uptime. Even though flespi updates a few times a day to give you the freshest features and superior performance, we would never compromise the credibility of your venture. Layers of interaction with flespi Gateway level — protocol-specific channels gettings data from your IoT and telematics devices into flespi. Registry level — virtual devices with dedicated long-term message storage, access to telemetry, and remote management capabilities. Analytics level — real-time calculation of user-defined metrics for business-specific insights. I have a tracker. What's next? 1 Create a channel to collect data from IoT and telematics devices 2 Create a device to aggregate messages and configure the tracker’s settings 3 Create a stream to forward data to a third-party platform 4 Subscribe a stream to a channel or device to pick what data to forward 5 Get the data inside the platform of your choice Three ways to access messages REST API — pull-based; request any information from the flespi platform. Check the docs here. MQTT API — push-based; subscribe to certain events and get updated on any changes immediately. More info here. Streams — push-based; forward data from flespi to specific 3rd-party platforms and applications. Check the available streams here. Join in to start connecting IoT and telematics hardware with flespi Login/Register Have you always dreamt of a handy device configurator? learn about our device management portal

Storage A one-of-a-kind telematics database will be happy to store telemetry from tracking devices, readings from sensors, pics & videos from cameras, and more. Get them in an instant in your applications once needed. Check flespi database changelog to track the development progress of this wonderful engine. Join in to store your telematics data and media with flespi Login/Register Never wait for your data Performance has always been our top priority. And since telematics and IoT are all about big data, we need to maintain performance regardless of the database size. Fetch up to 100,000 messages per second in a random access mode. The database engine is 100% developed in-house using pure C with mmaped b+tree under the hood. Never lose a single byte Every piece of data matters. We apply a special share mechanism to replicate data on several database nodes — this way we ensure RAID-10-like redundancy and guarantee your data integrity. Pick the best storage type for your data We offer several storage elements to better fit the nature of your data. Container is a simple key:value database that will store data in a custom JSON format. You can then extract certain messages by specifying a key range or a value range. Containers can serve as a time series database where keys represent UNIX time. You can filter messages by key (specify a key range) or by value (specify a value range for a JSON object). E.g., if a container stores the floating car data where a key is a timestamp and value is the current vehicle state and location, you can immediately fetch all messages when the driver was not wearing the seat belt. You can also define how a container will deal with duplicates — ignore, overwrite, merge or add — depending on the nature of the data. CDN is a special file storage with protected modification operations and read-only access via a public link. Use storage API in your apps Ease of integration means quicker results. Interact with the flespi database engine via REST API to manage all the low-level elements from any application that needs the data. Join in to store your telematics data and media with flespi Login/Register

Privacy policy DATA PROTECTION AGREEMENT Last Updated on May 19, 2025. The Customer shall make available to the Company and the Customer authorizes the Company to process information including Personal Data for the provision of the services under the public offer contract of rendering services of the flespi platform. The parties have agreed to enter into this Data Protection Agreement (the “DPA”) to confirm the data protection provisions relating to their relationship and so as to meet the requirements of the applicable Data Protection Law. 1. Definitions 1.1. For the purposes of this DPA: “Personal Data” means any information relating to an identified or identifiable natural person (‘data subject’); an identifiable natural person is one who can be identified, directly or indirectly, in particular by reference to an identifier such as a name, an identification number, location data, an online identifier or to one or more factors specific to the physical, physiological, genetic, mental, economic, cultural or social identity of that natural person; “Data Protection Law” means all applicable laws, regulations, and other legal requirements relating to (a) privacy, data security, consumer protection, marketing, promotion, and text messaging, email, and other communications; and (b) the use, collection, retention, storage, security, disclosure, transfer, disposal, and other processing of any Personal Data; “the Company” means a legal entity on whose behalf the Personal Data is processing under this DPA and called: (a) Gurtam UAB established under the law of Lithuania and registered at the address: Ozo g. 12A (5th floor), Penta Technopolis, 08200, Vilnius, Lithuania; or (b) any other Affiliate that means, with respect to a specified entity, (a) an entity that directly or indirectly, through one or more intermediaries, owns more than 50% of the outstanding voting securities of the Company, and (b) an entity that directly or indirectly through one or more intermediaries, is controlled by the Company, in each case where the term control means possession, directly or indirectly, of the power to direct or cause the direction of the management and policies of an entity, whether through ownership of voting securities, by contract interest or otherwise. “Services” means any of the following services provided by the Company: (a) the Company-branded product offerings made available via the Internet on https://flespi.com, (b) consulting or training services provided by the Company either remotely via the Internet or in person, and (c) any support services provided by the Company, including access to the Company’s help desk; the terms “data controller”, “data processor”, “data subject”, “personal data”, “processing” and “appropriate technical and organizational measures” shall have the meanings given to them under applicable Data Protection Law. 2. Subject Matter, Nature and Purpose of the Company’s Processing of Personal Data 2.1. The subject matter, nature and purpose of the processing of Personal Data under this DPA is the Company performance of the flespi platform services (the “Services) as further instructed in writing by the Customer in its use of the Services, unless required to do so otherwise by the Data Protection Law, in which case to the extent permitted by the Data Protection Law, the Company shall inform the Customer of this legal requirement prior to carrying out the processing. The Company shall only collect or process Personal Data for the period of rendering of the Services to the extent, and in such a manner, as is necessary for provision of the Services and in accordance with the DPA and the Data Protection Law applicable to the Company. 3. Duration 3.1. The processing of Personal Data will be carried out by the Company while flespi Account of the Customer is in existence or as needed for the performance of the obligations and rights between the Company and the Customer unless otherwise agreed upon in writing. 4. Type of Personal Data Processed 4.1. The Customer may submit Customer Personal Data to the Services, the extent of which is determined and controlled by the Customer in its sole discretion, and which may include, but is not limited to the following categories of Personal Data: Account Information. When the Customer signs up for a flespi Account, it is required certain information such as the name and email. The Customer may update or correct its information and email preferences at any time by visiting the flespi Account. The Company can provide the Customer with additional support to access, correct, delete, or modify the information the Customer provided to the Company and associated with the Customer’s flespi Account. To protect the security, the Company takes reasonable steps (such as requesting any legal information) to verify the identity of the Customer before making corrections. The Customer is responsible for maintaining the secrecy of the password and information of the Customer’s flespi Account at all times. Additional Profile Information. The Customer may choose to provide additional information as part of its flespi profile. Profile information helps the Customer to get more from the flespi platform. It’s the Customer’s choice whether to include sensitive information on its flespi profile. Other Information. The Customer may otherwise choose to provide the Company information when the Customer fills in a form, conducts a search, updates or adds information to its flespi Account, responds to surveys, posts to community forums, participates in promotions, or uses other features of the flespi platform. 5. The Company Obligations 5.1. The Company agrees and/or warrants: (a) to process the Personal Data only on behalf of the Customer and in compliance with its instructions and the DPA; if it cannot provide such compliance for whatever reasons, it agrees to inform promptly the Customer of its inability to comply, in which case the Customer is entitled to suspend the transfer of data and/or terminate the Services; (b) that all Personal Data processed on behalf of the Customer remains the property of the Customer and/or the relevant Data subjects; (c) that it has no reason to believe that the legislation applicable to it prevents it from fulfilling the instructions received from the Customer and its obligations under the DPA and that in the event of a change in this legislation which is likely to have a substantial adverse effect on the warranties and obligations provided by the DPA, it will promptly notify the change to the Customer as soon as it is aware, in which case the Customer is entitled to suspend the transfer of data and/or terminate the Services; (d) that it has implemented the technical and organizational security measures specified in Appendix 1 before processing the Personal Data transferred; (e) that it will promptly notify the Customer about: any legally binding request for disclosure of the Personal Data by a law enforcement authority unless otherwise prohibited, such as a prohibition under criminal law to preserve the confidentiality of a law enforcement investigation; any accidental or unauthorized access; and any request received directly from the data subjects without responding to that request, unless it has been otherwise authorized to do so; (f) to deal promptly and properly with all inquiries from the Customer relating to its processing of the Personal Data subject to the transfer and to abide by the advice of the supervisory authority with regard to the processing of the data transferred; (g) at the request of the Customer to submit its data-processing facilities for audit of the processing activities covered by the DPA; (h) that, in the event of sub-processing, it has previously informed the Customer and obtained its prior written consent; (i) that the processing services by the sub-processor will be carried out in accordance with Section 8; (j) to entrust only such employees with the data processing outlined in this DPA who have been bound to confidentiality and have previously been familiarized with the data protection provisions relevant to their work. The Company and any person acting under its authority who has access to Personal Data, shall not process that data unless on instructions from the Customer, unless required to do so by the Data Protection Law; (k) to monitor periodically the internal processes to ensure that processing within the Company area of responsibility is in accordance with the requirements of the Data Protection Law and the protection of the rights of the data subject. 6. Customer Obligations 6.1. The Customer agrees and/or warrants: (a) that the processing, including the transfer itself, of the Personal Data has been and will continue to be carried out in accordance with the relevant provisions of the Data Protection Law and does not violate the relevant provisions; (b) that it has instructed and throughout the duration of the personal data-processing services will instruct the Company to process the Personal Data transferred only on the Customer’s behalf and in accordance with the Data Protection Law and the DPA; (c) that the Company will provide sufficient guarantees in respect of the technical and organizational security measures specified in Appendix 1 to this DPA; (d) that after assessment of the requirements of the Data Protection Law, the security measures are appropriate to protect Personal Data against accidental or unlawful destruction or accidental loss, alteration, unauthorized disclosure or access, in particular where the processing involves the transmission of data over a network, and against all other unlawful forms of processing, and that these measures ensure a level of security appropriate to the risks presented by the processing and the nature of the data to be protected having regard to the state of the art and the cost of their implementation; (e) that it will ensure compliance with the security measures; (f) to access and use the Services only for legal, authorized, and acceptable purposes. The Customer will not use (or assist others in using) the Services in ways that: (a) violate, misappropriate, or infringe the rights of the Company, its users, or others, including privacy, publicity, intellectual property, or other proprietary rights; (b) are illegal, obscene, defamatory, threatening, intimidating, harassing, hateful, racially, or ethnically offensive, or instigate or encourage conduct that would be illegal, or otherwise inappropriate; (c) involve publishing falsehoods, misrepresentations, or misleading statements; (d) impersonate someone; (e) involve sending illegal or impermissible communications such as bulk messaging, auto-messaging, auto-dialing, and the like; or (f) involve any other use of the Services prescribed in this DPA unless otherwise authorized by the Company; (g) do not to (or assist others to) access, use, copy, adapt, modify, prepare derivative works based upon, distribute, license, sublicense, transfer, display, perform, or otherwise exploit the flespi platform in impermissible or unauthorized manners, or in ways that burden, impair, or harm the Company, the flespi platform, systems, other users, or others, including that the Customer will not directly or through automated means: (a) reverse engineer, alter, modify, create derivative works from, decompile, or extract code from the flespi platform; (b) send, store, or transmit viruses or other harmful computer code through or onto the flespi platform; (c) gain or attempt to gain unauthorized access to the flespi platform or systems; (d) interfere with or disrupt the integrity or performance of the flespi platform; (e) create accounts for the flespi platform through unauthorized or automated means; (f) collect the information of or about other users in any impermissible or unauthorized manner; (g) sell, resell, rent, or charge for the flespi platform; or (h) distribute or make the flespi platform available over a network where it could be used by multiple devices at the same time; (h) that the Customer is responsible for keeping the Customer’s flespi Account safe and secure, and the Customer will notify the Company promptly of any unauthorized use or security breach of the Customer’s Account or the flespi platform. 7. Technical and Organizational Measures 7.1. The Company shall take the appropriate technical and organizational measures to adequately protect Personal Data against accidental or unlawful destruction, loss, alteration, unauthorized disclosure of, or access to Personal Data, described under Appendix 1. Such measures include but not limited to physical and IT measures, and organizational measures to: (a) the prevention of unauthorized persons from gaining access to Personal Data processing systems (physical access control), (b) the prevention of Personal Data processing systems from being used without authorization (logical access control), (c) ensuring that persons entitled to use a Personal Data processing system gain access only to such Personal Data as they are entitled to accessing in accordance with their access rights, and that, in the course of processing or use and after storage, Personal Data cannot be read, copied, modified or deleted without authorization (data access control), (d) ensuring that Personal Data cannot be read, copied, modified or deleted without authorization during electronic transmission, transport or storage on storage media, and that the target entities for any transfer of Personal Data by means of data transmission facilities can be established and verified (data transfer control), (e) ensuring the establishment of an audit trail to document whether and by whom Personal Data have been entered into, modified in, or removed from Personal Data processing systems (entry control), (f) ensuring that Personal Data is protected against accidental destruction or loss (availability control). 7.2. The technical and organizational measures are subject to technical progress and further development. In this respect the Company may implement alternative adequate measure, however, the security level of the defined measures must never be reduced. Major changes must be documented. 8. Sub-Processors 8.1. The Customer hereby gives general advance consent to the Company to engage the Company’s Affiliate or third parties which will process Personal Data on behalf of the Company in order to assist the Company to deliver the Services (“Sub-processors”) according to the scope and purposes specified in this DPA. The Company has or will enter into written agreement with each Sub-processor containing data protection obligations not less protective than those in this DPA to the extent applicable to the nature of the Services provided by such Sub-processor. If the Sub-processor processes the Services outside the EU/EEA, the Company shall ensure that the transfer is made pursuant to European Commission approved standard contractual clauses for the transfer of Personal Data which the Customer authorizes the Company to enter into on its behalf, or that other appropriate legal data transfer mechanisms are used. 8.2. The current Sub-processors for the Services are as follows: Sub-processor nameService descriptionLocationMore information ZylonData hosting servicesNetherlandshttps://www.zylon.net/en/ OpenAI Ireland Ltd.AI powered featuresIrelandhttps://openai.com/ Anthropic PBCAI powered featuresUSAhttps://www.anthropic.com/ Mistral AIAI powered featuresFrancehttps://mistral.ai/ Google Cloud EMEA LimitedAI powered featuresIrelandhttps://cloud.google.com The Customer agrees and approves that the Company has engaged such Sub-processors to process Personal Data as set out in the list. 8.3. The Company shall notify the Customer about its plans to replace or engage a new Sub-processor by making such information available to the Customer no later than fourteen (14) calendar days prior to the planned event. If the Customer continues using the Services following the replacement or involvement of a new Sub-processor and notification of the Customer under the procedure provided for in this clause, it shall be considered that the Customer agreed to such actions of the Company. If the Customer withdraws its general consent to engage Sub-processor, the Company shall have the right to unilaterally, under out-of-court procedure, terminate this DPA and public offer contract of rendering services of the flespi platform, and such termination shall be considered to have been made for important reasons and the Customer shall be deemed not to have suffered any damage due to such termination. 8.4. For the avoidance of doubt, where any Sub-processor fails to fulfill its obligations under any sub-processing agreement or under applicable law the Company will remain fully liable to the Customer for the fulfillment of its obligations under this DPA. 9. Audit 9.1. In order to confirm compliance with this DPA, the Customer shall be at liberty to conduct an audit by assigning an independent third party who shall be obliged to observe confidentiality in this regard. Any such audit must occur during the Company’s normal business hours and will be permitted only to the extent required for the Customer to assess the Company’s compliance with this DPA. In connection with any such audit, the Customer will ensure that the auditor will: (a) review any information on the Company’s premises; (b) observe reasonable on-site access and other restrictions reasonably imposed by the Company; (c) comply with the Company’s policies and procedures, and (d) not unreasonably interfere with the Company’s business activities. The Company reserves the right to restrict or suspend any audit in the event of any breach of the conditions specified in this Section 9. 9.2. In the event that the Customer, a regulator or data protection authority requires additional information or an audit related to the Services, then, the Company agrees to submit its data processing facilities, data files and documentation needed for processing Personal Data to audit by the Customer (or any third party such as inspection agents or auditors, selected by Customer) to ascertain compliance with this DPA, subject to being given notice and the auditor entering into a non-disclosure agreement directly with the Company. The Company agrees to provide reasonable cooperation to Customer in the course of such operations including providing all relevant information and access to all equipment, software, data, files, information systems, etc. used for the performance of Services, including processing of Personal Data. Such audits shall be carried out at the Customer’s cost and expense. 9.3. The audit may only be undertaken when there are specific grounds for suspecting the misuse of Personal Data, and no earlier than two weeks after the Customer has provided written notice to the Company. 9.4. The findings in respect of the performed audit will be discussed and evaluated by the parties and, where applicable, implemented accordingly as the case may be by one of the parties or jointly by both parties. The costs of the audit will be borne by the Customer. 10. Notification of A Data Breach 10.1. In the event of the Company aware of any breach of security that results in the accidental, unauthorized or unlawful destruction or unauthorized disclosure of or access to Personal Data the Company shall to the best of its ability, notify the Customer thereof with undue delay, after which the Customer shall determine whether or not to inform the Data subjects and/or the relevant regulatory authority(ies). This duty to report applies irrespective of the impact of the leak. The Company will endeavour that the furnished information is complete, correct and accurate. 10.2. If required by law and/or regulation, the Company shall cooperate in notifying the relevant authorities and/or Data subjects. The Customer remains the responsible party for any statutory obligations in respect thereof. 10.3. The duty to report includes in any event the duty to report the fact that a leak has occurred, including details regarding: the (suspected) cause of the leak; the (currently known and/or anticipated) consequences thereof; the (proposed) solution; the measures that have already been taken. 11. Deletion and Return of Personal Data 11.1. The parties agree that on the termination of the provision of data-processing services, the Company and its subcontractors shall, at the choice of the Customer, return all the Personal Data transferred and the copies thereof to the Customer or shall destroy all the Personal Data and certify to the Customer that it has done so, unless legislation imposed upon the Company prevents it from returning or destroying all or part of the Personal Data transferred. In that case, the Company warrants that it will guarantee the confidentiality of the Personal Data transferred and will not actively process the Personal Data transferred anymore. The Company and its subcontractors warrant that upon request of the Customer and/or of the supervisory authority, it will submit its data-processing facilities for an audit of the measures referred to in Section 9. 12. Governing Law/Forum 12.1. This DPA shall be governed by and interpreted in accordance with the laws of Lithuania. 12.2. Any and all claims, disputes or controversies arising under, out of, or in connection with this DPA, breach, termination or validity thereof, which have not been resolved by good faith negotiations between the Company and the Customer within period of thirty (30) calendar days after receipt of a notice from one party to the other requesting negotiations shall be resolved by final and binding arbitration in the Vilnius Court of Commercial Arbitration in accordance with its Rules of Arbitration as in force and effect on the date of the DPA. Disputes shall be settled by a single arbitrator. Arbitration proceedings shall be held in Vilnius, Lithuania. The place of arbitration shall be Vilnius, Lithuania. The language of arbitration shall be English. Relevant documents in other languages shall be translated into English if the arbitrators so direct. All expenses and costs of the arbitrators and the arbitration in connection therewith will be shared equally, except that the Company and the Customer will each bear the costs of its own prosecution and defense, including without limitation attorney’s fees and the production of witnesses and other evidence. Any award rendered in such arbitration shall be final and may be enforced by either party. 12.3. The parties agree to keep all details of the arbitration proceedings and arbitral award strictly confidential and shall use all reasonable efforts to take such action as may be appropriate to prevent the unauthorized disclosure of the proceedings, any information disclosed in connection therewith and the award granted. Appendix No. 1 Description of the technical and organizational measures implemented by the Company: The Company shall implement the measures described in this appendix, provided that the measures directly or indirectly contribute or can contribute to the protection of Personal Data during the period of the Company’s Services rendering to the Customer. If the Company believes that a measure is not necessary for the respective Service or part thereof, the Company will justify this and come to an agreement with the Customer. The technical and organizational measures are subject to technical progress and development. In this respect the Company is permitted to implement alternative adequate measures. The level of security must align with industry security best practice and not less than, the measures set forth herein. All major changes are to be agreed with the Customer and documented. 1. Risk management 1.1. Security risk management 1. The Company shall identify and evaluate security risks related to confidentiality, integrity and availability and based on such evaluation implement appropriate technical and organizational measures to ensure a level of security which is appropriate to the risk. 2. The Company shall have documented processes and routines for handling risks within its operations. 3. The Company shall periodically assess the risks related to information systems and processing, storing and transmitting information. 1.2. Security risk management for personal data 1.2.1. The Company shall identify and evaluate security risks related to confidentiality, integrity and availability and based on such evaluation implement appropriate technical and organizational measures to ensure a level of security which is appropriate to the risk of the specific Personal Data types and purposes being processed by the Company, including inter alia as appropriate: The pseudonymisation and encryption of Personal Data; The ability to ensure the ongoing confidentiality, integrity, availability and resilience of processing systems and services; The ability to restore the availability and access to the Customer’s Data in a timely manner in the event of a physical or technical incident; A process for regularly testing, assessing and evaluating the effectiveness of technical and organizational measures for ensuring the security of the processing. 1.2.2. The Company shall have documented processes and routines for handling risks when processing Personal Data on behalf of the Customer. 1.2.3. The Company shall periodically assess the risks related to information systems and processing, storing and transmitting Personal Data. 1.3. Information security policies 1.3.1. The Company shall have a defined and documented information security management system including an information security policy and procedures in place, which shall be approved by the Company’s management. They shall be published within the Company´s organization and communicated to relevant the Company personnel. 1.3.2. The Company shall periodically review the Company’s security policies and procedures and update them if required to ensure their compliance with this Appendix. 2. Organization of information security The Company shall have defined and documented security roles and responsibilities within its organization. 3. Human resource security The Company shall ensure that the Company personnel handles information in accordance with the level of confidentiality required under the DPA. The Company shall ensure that relevant the Company personnel is aware of the approved use (including use restrictions as the case may be) of information, facilities and systems under the DPA. The Company shall ensure that any the Company personnel performing assignments under the Agreement is trustworthy, meets established security criteria and has been, and during the term of the assignment will continue to be, subject to appropriate screening and background verification. The Company shall ensure that the Company personnel with security responsibilities is adequately trained to carry out security related duties. The Company shall provide or ensure periodical security awareness training to relevant the Company personnel. Such Company training shall include, without limitation: (a) How to handle customer information security (i.e. the protection of the confidentiality, integrity and availability of information); (b) Why information security is needed to protect customer’s information and systems; (c) The common types of security threats (such as identity theft, malware, hacking, information leakage and insider threat); (d) The importance of complying with information security policies and applying associated standards/procedures; (e) Personal responsibility for information security (such as protecting customer’s privacy-related information and reporting actual and suspected data breaches). 4. Access control The Company shall have a defined and documented access control policy for facilities, sites, network, system, application and information/data access (including physical, logical and remote access controls), an authorization process for user access and privileges, procedures for revoking access rights and an acceptable use of access privileges for the Company personnel in place. The Company shall have a formal and documented user registration and de-registration process implemented to enable assignment of access rights. The Company shall assign all access privileges based on the principle of need-to-know and principle of least privilege. The Company shall use strong authentication (multi-factor) for remote access users and users connecting from an untrusted network. The Company shall ensure that the Company personnel has a personal and unique identifier (user ID), and use an appropriate authentication technique, which confirms and ensures the identity of users. 5. Physical and environmental security The Company shall protect information processing facilities against external and environmental threats and hazards, including power/cabling failures and other disruptions caused by failures in supporting utilities. This includes physical perimeter and access protection. 6. Operations security The Company shall have an established change management system in place for making changes to business processes, information processing facilities and systems. The change management system shall include tests and reviews before changes are implemented, such as procedures to handle urgent changes, roll back procedures to recover from failed changes, logs that show, what has been changed, when and by whom. The Company shall implement malware protection to ensure that any software used for the Company’s provision of the Services to the Customer is protected from malware. The Company shall make backup copies of critical information and test back-up copies to ensure that the information can be restored as agreed with the Customer. The Company shall log and monitor activities, such as create, reading, copying, amendment and deletion of processed data, as well as exceptions, faults and information security events and regularly review these. Furthermore, the Company shall protect and store (for at least 6 months or such period/s set by Data Protection Law) log information, and on request, deliver monitoring data to the Customer. Anomalies / incidents / indicators of compromise shall be reported according to the data breach management requirements as set out in clause 9, below. The Company shall manage vulnerabilities of all relevant technologies such as operating systems, databases, applications proactively and in a timely manner. The Company shall establish security baselines (hardening) for all relevant technologies such as operating systems, databases, applications. The Company shall ensure development is segregated from test and production environment. 7. Communications security The Company shall implement network security controls such as service level, firewalling and segregation to protect information systems. 8. The Company relationship with sub-suppliers The Company shall reflect the content of this Appendix in its agreements with Sub-processors that perform tasks assigned under the DPA. The Company shall regularly monitor, review and audit Sub-processor’s compliance with this Appendix. The Company shall, at the request of the Customer, provide the Customer with evidence regarding Sub-processor’s compliance with this Appendix. 9. Data breach management The Company shall have established procedures for data breach management. The Company shall inform the Customer about any data breach (including but not limited to incidents in relation to the processing of Personal Data) as soon as possible but no later than within 36 hours after the data breach has been identified. All reporting of security-related incidents shall be treated as confidential information and be encrypted, using industry standard encryption methods. The data breach report shall contain at least the following information: (a) The nature of the data breach, (b) The nature of the Personal Data affected, (c) The categories and number of data subjects concerned, (d) The number of Personal Data records concerned, (e) Measures taken to address the data breach, (f) The possible consequences and adverse effect of the data breach, and (g) Any other information the Customer is required to report to the relevant regulator or data subject. To the extent legally possible, the Company may claim compensation for support services under this clause 9 which are not attributable to failures on the part of the Company. 10. Business continuity management The Company shall identify business continuity risks and take necessary actions to control and mitigate such risks. The Company shall have documented processes and routines for handling business continuity. The Company shall ensure that information security is embedded into the business continuity plans. The Company shall periodically assess the efficiency of its business continuity management, and compliance with availability requirements (if any). Contact us

First-ever flespi offline event. Content-rich, interactive & community-bonding flespi conf 2023 September 12 VILNIUS 100 attendees 10h content 75% practical Log in / register Supercharge Your Solution Delve into the depths of the flespi architecture, philosophy, and best practices to unlock the potential for computational optimization, cost-effectiveness, and accelerated time-to-market. Know Your Allies It's important for you to realize that when you start working on a project, you are not the only one who cares about its success! Our goal for this event is to show how the three parties involved (solution developers, flespi team, and hardware manufacturers) are actually looking in the same direction, how they can complement each other's efforts, and how to orchestrate them. Grow Together Stay ahead of the curve and gain valuable insights into market trends, telematics equipment, and flespi's future plans. Get prepared to seize new opportunities as they arise. Share experience with the peers across borders, industries, and business domains. Topics we’ll cover Level up the basicsexplore channels, devices, plugins, groups Embrace integrabilityREST API, streams, MQTT, webhooks Adopt Zero scriptingdataflow automation & time-series data analysis Hardware insightsBLE tags, video, gateways, other connected peripherals Data & Integration Hubready-made for feeding your data into target platforms Discover the UIfeatures, tricks and apps that will save you enormous time [workshop] Meet our speakers Aliaksei Shchurko Chief Gurtam Architect, CEO Jan Bartnitsky Software Engineer Sergei Leuchanka VP of Business Development Nadzeya Mikhailava Software Engineer Hardware partners in attendance Agenda Conference language: English 9:00-10:00 Registration, welcome coffee & introduction 10:00-11:00 flespi past, present, future 11:00-11:30 Core flespi entities: channels, devices, plugins 11:30-12:00 Integration with flespi: REST API, streams, MQTT 12:00-12:30 1st coffee break 12:30-13:00 Reports and notifications with flespi 13:00-13:30 How to automate your processes with zero scripting 13:30-14:00 How to organize your account secure and future-proof 14:00-15:00 Networking lunch️ 15:00-16:00 flespi UI: features, tricks and apps [workshop] 16:00-16:30 flespi as Data and Integration Hub 16:30-17:00 2nd coffee break 17:00-17:20 Video functionality announcement 17:20-18:00 Panel discussion with Hardware Partners 18:00-21:00 Networking Reception Where? Courtyard by Marriott Rinktines st. 3, Vilnius Registration Registration is only available for the flespi users, so make sure your account is alive ;) Seats are limited, be among the first so we can secure your visit. Log in / register One super-intensive day of speeches is not all we want to see you for!  To get the most out of your visit, you may book a personal consultation with one of our developers and discuss the specific technical, architectural, and business issues. Booking will be available after registration. FAQ ? Can I invite a colleague or a few colleagues to the event?Yes, you can add up to 3 team members during registration. ? Do I need a visa to visit Lithuania? We’ve opened registration in advance so you have enough time to handle your Schengen visa arrangements in case you need it for entering Lithuania. We advise you to check the visa requirements for your country. Please note: we don’t provide assistance with visa applications. ? Can you advise a place to stay in Vilnius? To make your visit even more comfortable we're offering special prices right at Courtyard by Marriott. Please reach us in chat for details. ? I’ve booked a personal consultation. When and where will we meet?Personal meetings will be arranged on September 13. You’ll be invited to our HQ at Technopolis Penta (Ozo g., 12A). ? I'm a hardware manufacturer / service provider. Can we discuss participation options for partners?You're welcome! Just leave us a note while filling in the registration form and we'll get in touch with you asap. Got a question? Contact us in chat

Technologies flespi is not about neverending features and eye-candy interfaces. It’s about technologies. We invent them. We implement them. We share them with you. Below are some of the core technologies making up a unique technological blend to power your most daring projects. PVM: Universal protocol parsing technology Receiving telematics messages from hundreds of GPS tracker types by multiple manufacturers and giving them to you in an easily manageable format is the primary goal of the flespi telematics hub. What PVM does is unscrambles each message according to the protocol specification, applies universal parameter naming, and saves the message in a JSON format. The common naming scheme enables aggregate data processing across protocols, while the ubiquitous JSON format makes it straightforward to access the data from any target application. The same is true for the opposite direction - you can send commands to devices and they will automatically convert into the proper format for the receiving device. Read all the technical details of PVM implementation here. More information MDB: Specialized telematics storage MDB architecture accounts for the specifics of the telemetry messages to guarantee fetching 500,000 messages per second in a block mode and 100,000 messages per second in a random access mode. Redundancy mechanisms ensure superior data integrity by replicating data on several database nodes to deliver RAID-10-like performance. Once your data gets into the flespi platform, you can rest assured that it’s sitting in a safe place and is available in an instant from anywhere in the world. Learn more about a unique telematics database here. More information HASD: The new generation of hierarchical state database Inspired by the databases of the 60s but wired using the cutting-edge MQTT 5.0 protocol, HASD uses retained messages to store data inside flespi MQTT Broker. The hierarchy is determined by the MQTT topic structure, asynchrony is inherited from the nature of MQTT protocol, object state updates happen automatically via the established subscription. Read an in-depth HASD overview here. More information AI Assistant: : Continuously learning support technology Providing instant technical assistance across hundreds of device types and complex telematics scenarios is the main goal of the flespi AI Assistant. It continuously examines support conversations, device configurations, and platform behavior 24/7 to deliver contextual answers. The self-learning architecture makes it capable of tackling increasingly sophisticated tasks — from device integration troubleshooting to advanced analytics setup — while drawing on past resolutions to proactively prevent similar issues. This transforms reactive help into predictive guidance that anticipates user needs. Read all the technical details of AI implementation here. More information

Collect custom data relevant to your project via flespi MQTT API and visualize it effectively.