NEQTO Docs
  • Languages iconEnglish
    • 日本語
  • Docs
  • API
  • FAQ

›NEQTO

Getting Started

  • NEQTO Hello World!
  • Tutorial Step 1. NEQTO Console Setting
  • Tutorial Step 2. Device Settings & Launching Service (NEQTO Bridge)
  • Tutorial Step 2. Device Settings & Launching Service (STM32 Discovery)
  • Tutorial Step 2. Device Settings & Launching Service (SPRESENSE)
  • Tutorial Step 3. Application development using scripts

NEQTO

  • NEQTO Account Registration
  • Sub-accounts
  • API Usage
  • NEQTO Engine Firmware List
  • Support Guidelines
  • For safe and secure use of the NEQTO products
  • Vulnerability Disclosure Policy

NEQTO Console

  • Introduction
  • Fundamentals
  • Administrative Actions
  • Device Management
  • Linux-based Device Management
  • Batch Registration
  • Scripts
  • Actions and Contacts
  • View Data from the Console
  • NEQTO Apps

    • About NEQTO Apps
    • NEQTO Infinitypool
    • NEQTO Insights
    • NEQTO Custodia
    • NEQTO Flow
  • Machine Driver
  • Recommended Browsers
  • Billing Information

SPRESENSE

    Hardware Specifications

    • 01. About Spresense

    Software Specifications

    • 01. Operational Flow
    • 02. Initial Installation
    • 03. Spresense Wi-Fi Initial Setup
    • 04. Spresense LTE-M Initial Setup
    • 05. Debug Log Acquisition
    • 06. System LED Indications
    • 07. Event Messages
    • 08. Updating Firmware

    neqto.js

    • 01. About neqto.js
    • 02. Log
    • 03. Timers
    • 04. HTTP
    • 05. HTTPS
    • 06. MQTT
    • 07. Secure
    • 08. Storage
    • 09. Sleep
    • 10. RTC
    • 11. GPIO
    • 12. UART
    • 13. SPI
    • 14. I2C
    • 15. ADC
    • 16. GNSS
    • 17. Camera
    • 18. Utils
    • 19. nqSpresense
    • 20. nqService
    • 21. nqMqtt
    • 22. nqFOTA
    • 23. nqWiFi
    • 24. nqLte

STM32 Discovery

    Hardware Specifications

    • 01. About STM32 Discovery Kit (B-L4S5I-IOT01A)

    Software Specifications

    • 01. Operational Flow
    • 02. Initial Installation
    • 03. STM32 Discovery Wi-Fi Initial Setup
    • 04. Debug Log Acquisition
    • 05. System LED Indications
    • 06. Event Messages
    • 07. Updating Firmware

    neqto.js

    • 01. About neqto.js
    • 02. Log
    • 03. Timers
    • 04. HTTP
    • 05. HTTPS
    • 06. MQTT
    • 07. Secure
    • 08. Storage
    • 09. Sleep
    • 10. RTC
    • 11. UserSW
    • 12. GPIO
    • 13. UART
    • 14. SPI
    • 15. I2C
    • 16. ADC
    • 18. Utils
    • 19. nqDiscovery
    • 20. nqService
    • 21. nqMqtt
    • 22. nqFOTA
    • 23. nqWiFi

NEQTO Bridge

    Hardware Specifications

    • 01. NEQTO Bridge Module
    • 02. NEQTO Bridge Wi-Fi Module
    • 03. NEQTO Bridge LTE-1 Module
    • 04. NEQTO Bridge LTE-M/NB Module
    • 05. NEQTO Bridge IO Board
    • 06. NEQTO Bridge Digital IO Board
    • 07. NEQTO Bridge Connector Board

    Software Specifications

    • 01. Operational Flow
    • 02. NEQTO Bridge Wi-Fi Module Initial Setup
    • 03. NEQTO Bridge LTE Module Initial Setup
    • 04. Debug Log Acquisition
    • 05. System LED Indications
    • 06. Event Messages
    • 07. Updating Firmware

    neqto.js

    • 01. About neqto.js
    • 02. Log
    • 03. Timers
    • 04. HTTP
    • 05. HTTPS
    • 06. MQTT
    • 07. Secure
    • 08. Storage
    • 09. Sleep
    • 10. RTC
    • 11. UserSW
    • 12. GPIO
    • 13. UART
    • 14. SPI
    • 15. I2C
    • 16. ADC
    • 17. BLE
    • 18. Utils
    • 19. nqBridge
    • 20. nqService
    • 21. nqMqtt
    • 22. nqFOTA
    • 23. nqWiFi
    • 24. nqLte
    • 25. nqLAN
    • 26. nqEx

Linux-based device

    Software Specifications

    • 01. System Requirements
    • 02. Installation
    • 03. Software Configurations
    • 04. Operational Flow
    • 05. Debug Log Acquisition
    • 06. Event Messages
    • 07. Updating Software

    neqto.js

    • 01. About neqto.js
    • 02. Log
    • 03. Timers
    • 04. HTTP
    • 05. HTTPS
    • 06. MQTT
    • 07. Secure
    • 08. Storage
    • 09. RTC
    • 10. UNIXSocket
    • 11. FileSystem
    • 12. SubProcess
    • 13. SubTask
    • 14. Queue
    • 15. Utils
    • 16. nqLinux
    • 17. nqService
    • 18. nqMqtt
    • 19. nqFOTA
    • 20. nqLAN

neqto.js Libraries

  • About neqto.js Libraries
  • UART

    • GM65 Barcode Reader
    • SRF Ultrasonic Range Finder - Serial Mode

    I2C

    • HTS221 v2 Temperature and Humidity Sensor
    • LIS2DW12 v2 Accelerometer
    • SRF Ultrasonic Range Finder - I2C Mode
    • [Archive] HTS221 Temperature and Humidity Sensor
    • [Archive] LIS2DW12 Accelerometer

    Utils

    • RTC Alarm Synchronized Scheduler

    Integration

    • AWS S3 v2
    • AWS IoT Core v2
    • Azure IoT v2
    • [Archive] GCP IoT Core
    • [Archive] AWS S3
    • [Archive] AWS IoT Core

neqto.js Snippets

  • About neqto.js Snippets
  • DataDog
  • Dropbox
  • Google Sheets
  • InfluxDB
  • Oracle Cloud Object Storage
  • Salesforce
  • Splunk
  • Niagara
  • [Archive] SAP Cloud Platform Internet of Things

Release Notes

  • NEQTO Console Updates
  • NEQTO Firmware (Bridge Wi-Fi/LTE Module) Releases
  • NEQTO Firmware (STM32 Discovery Wi-Fi) Releases
  • NEQTO Firmware (Spresense Wi-Fi/LTE-M) Releases
  • NEQTO Engine for Linux Releases
  • neqto.js Libraries Releases

Vulnerability Disclosure Policy

JIG-SAW INC. (hereinafter, the "Company," "we" "us" or "our") will disclose information on vulnerabilities in its products by the following process, to ensure the security of its products in response to new vulnerabilities that are discovered from day to day, and to protect its customers from cyber-attacks.
Responses to vulnerability information for the Company's products will be carried out by its Product Security Incident Response Team (PSIRT).

Obtaining Vulnerability Information

For information regarding product vulnerabilities, please refer to the following guidelines, and notify our Support Center.

Support Guidelines

After confirming receipt of information regarding vulnerabilities sent to us via our Support Center, we will notify you of receipt within three business days. Please note that it may take us longer to reply during the end-of-year and New Year holidays, summer vacation periods, and long holidays periods in Japan (Golden Week etc). When contacting us, please provide the following information.
  1) Name and version of the product containing the vulnerability
  2) Type of vulnerability (Leakage of user information and Unauthorized Access, etc.) and impact
  3) Procedure for reproducing the vulnerability, Proof of Concept code, or attack code
  4) Name, telephone number, and email address of the person making the report

Customer information and vulnerability information provided will be managed in accordance with the JIG-SAW Group's Privacy Policy.

Privacy Policy: https://www.jig-saw.com/en/policy-en/

We will express our gratitude to persons who contribute to the discovery and/or resolution of vulnerabilities in our products with good intentions, and will not hold them legally liable in any way.

We may not be able to respond to inquiries that are not specific to our products.
For information about other products not made by the Company, please contact the manufacturer of the relevant product.

Vulnerability Research and Response Measures

Information that you provide about the vulnerability of products will be investigated by our Design and Development Departments to determine the impact of the vulnerability.
If we determine that response measures are necessary, we will implement them in cooperation with our Design and Development Departments. As response measures, we will prepare a repair program, or a workaround.

Information Disclosure

In accordance with the principle of matching dates of publication, we will adjust the date of publication with the reporter and other relevant parties as soon as preparations for publication are complete, and publish the information in the Release Notes of our website.

Release Notes: https://neqto.jig-saw.com/en/news/releases

Principle of matching publication dates (excerpt from the JPCERT/CC guidelines for handling vulnerability-related information)

When handling vulnerability-related information before it is made public, if the vulnerability-related information is made public or leaked to malicious third parties before response measures have been prepared, malicious code (attack code) may be developed and distributed, and attacks on systems affected by the vulnerability may start to occur. As a result, there is a possibility that it may cause harm to product users.

In addition, it is also important to ensure that all parties involved are in agreement when releasing vulnerability-related information, especially in the case of vulnerabilities that affect multiple products. If information is released independently without waiting for the date and time of announcement to the public coordinated between the relevant parties, users of other companies' products may be at risk.

In cases of international coordination with overseas organizations, if the timing of information disclosure is incorrect (information is disclosed independently before the date and time of announcement to the public), overseas organizations may take measures to exclude the developer in question from handling vulnerability-related information in the future.

Disclaimer

If users receive a notification of the release of an updated version of our products (including software) with regard to security vulnerabilities, they should upgrade those products to the relevant updated version.
Information relating to security vulnerabilities is clearly indicated in the "title" section of the release notes, and the content is indicated in the "important topics" section.
Users who do not perform the aforementioned version upgrades are at increased risk of exposure to cyber-attacks or computer system faults.
Users are responsible for performing the aforementioned version upgrades at their own risk. Users who do not perform the aforementioned version upgrades are liable for any and all damages they incur due to accidents or faults that may occur as a result of failure to perform such upgrades; as well as any damage to computer systems, loss or leakage of data, communication failures, or other accidents or malfunctions that may generally be expected to occur as a result of using the Company's products. The Company will not be held liable whatsoever for any such damages.


Updated: 2025-03-11
← For safe and secure use of the NEQTO productsIntroduction →
  • Obtaining Vulnerability Information
  • Vulnerability Research and Response Measures
  • Information Disclosure
  • Principle of matching publication dates (excerpt from the JPCERT/CC guidelines for handling vulnerability-related information)
  • Disclaimer
AboutNewsProductsFAQPrivacy PolicyVulnerability Disclosure Policy
NEQTO Console
IntroductionFundamentalsAdministrative ActionsDevice Management NEQTO Apps
NEQTO Bridge
NEQTO Bridge ModuleNEQTO Bridge Wi-Fi ModuleNEQTO Bridge LTE-1 ModuleError Logging Event Messages
API Documentation
API UsageGlobal APIRegional APIAPI Terms of Service
Jigsaw, Inc.
© 2025 JIG-SAW INC.