Soracom Flux AI actions now let you select the Google Gemini 2.5 Flash-Lite model.

Requests to AI models available in AI actions are managed with Flux credits. Google Gemini 2.5 Flash-Lite consumes 4 credits per request. AI models that allow you to use your own license (API key) do not consume credits.

The credit consumption per request for Google Gemini 2.5 Flash-Lite is as follows:

Model	Consumed credits
Google Gemini 2.5 Flash-Lite	4 Credits

Google Gemini 2.5 Flash-Lite supports video input. When video is specified as input to the AI model, additional credits for video usage are also consumed. For details on credit consumption, see Actions and consumed credits (Japanese).

For more information on Soracom Flux, please refer to the Soracom Flux documentation.

We have added a new action, Collect Message Action (Japanese), to Soracom Flux.

The Collect Message Action aggregates actions that have been branched within a Flux app or split using the Send event for each feature.

For example, after executing a RTSP Camera Image Action and an AI Action targeting multiple RTSP compatible cameras, you can then execute subsequent notifications collectively.

The Collect Message Action is available on the Standard Plan and Enterprise Plan.

For more information, see Collect Message Action (Japanese).

We added a preview feature to Soracom Harvest Files so you can check image and text files directly from the User Console without downloading them.

Select a file in the console to open a preview, which is helpful when you want to quickly confirm its contents before downloading.

Previewing a file counts as a Harvest Files read, so charges apply based on the amount of data displayed, just like when downloading.

For more details, please refer to Soracom Harvest Files.

We have added a new action, Bounding Box Action (Japanese), to Soracom Flux.

The Bounding Box Action sets a border frame around the image at the specified URL. By setting this frame, you can explicitly indicate the target area within the image for subsequent actions that use it.

For example, you can use the Bounding Box Action to specify the target area on an image acquired via the RTSP Camera Image Action, and then instruct the AI Action to "detect objects within the red box," allowing you to perform AI analysis on a specific region within the image.

The Bounding Box Action is available on the Standard Plan and Enterprise Plan.

Soracom previously did not advertise an MTU (Maximum Transmission Unit) value to devices, so they relied on their implementation defaults (typically 1500 bytes). You can now configure the MTU per SIM group from the Soracom User Console so that the network advertises the value that best fits each deployment.

Why MTU control matters

MTU represents the largest IP packet that can traverse a link without being fragmented. When packets exceed the announced MTU, the cellular network must split them or drop them outright, which adds protocol headers, increases retransmission risk, and can prevent applications from communicating at all. Deployments that rely on VPN tunnels, private routes, or embedded devices with smaller buffers often had to work around the previous fixed MTU, leading to chronic fragmentation and lower throughput.

Benefits of customizing the MTU

By selecting an MTU that matches the rest of your network, you can keep packet sizes consistent end to end and avoid unnecessary fragmentation. Set a smaller value for VPN tunnels or other constrained links, while keeping the default for groups where the entire network between the device and its peers can accommodate larger packets.

Setting the appropriate MTU delivers the following benefits:

• Reduces unnecessary fragmentation and retransmissions, preventing throughput loss on cellular links.
• Prevents packet drops or application outages caused by MTU mismatches, reducing troubleshooting overhead.

Note: Some devices do not support MTU updates advertised by the network and will continue operating with their default value (typically 1500 bytes). Please confirm the device specifications beforehand.

For UI steps, API/CLI payload examples, and tips on verifying the right value (for example with ping), see IP Link MTU Configuration.

If you have any questions, please contact Soracom Support.

We are pleased to release a new SoraCam AI feature for Soracom Cloud Camera Services (SoraCam). SoraCam AI captures still images from SoraCam cameras, analyzes them with generative AI, and emails the results. SoraCam AI is currently available as an Early Access feature.

Ready to use just by writing prompts

No programming or complex configuration is required. In the Soracom User Console, review the camera image and describe in natural language what you want to achieve. SoraCam AI handles the analysis and email notification. Example prompts include:

• "Count the number of people in the office and include the count in the email subject line."
• "Count the number of vehicles in the parking lot and notify me."
• "Detect if there is anyone not wearing a uniform and describe that person's characteristics in the email body."
• "Notify me if a person appears in the camera footage. Use the camera name in the notification subject line. Describe the person's characteristics in the body."

You can trigger image analysis at periodic intervals or when SoraCam motion or sound detection events occur.

Because no programming is required, anyone who can operate a computer can start using the service right away.

Pricing

SoraCam AI costs 550 yen (tax included) per month per camera.

() As this is an optional feature of Soracom Cloud Camera Services, you must also have a Soracom Cloud Camera cloud license or Real-time Access (Early Access) subscription. () This service is in Early Access. Early Access means the service is provided after customers agree to preliminary precautions.

How to Use

Apply through the Soracom Cloud Camera AI (Early Access) application (Japanese).

After you agree to the conditions and submit the application, we will enable the feature and notify you by email. You can then use the service from the Soracom User Console.

If you have any questions, please contact Soracom Support.

Please note that this service is currently only available for customers located in Japan.

As previously announced, the User Console has now been updated so that creating a Napter On-Demand Remote Access session will use the new PortMapping:createPortMappingForSim API instead of the existing PortMapping:createPortMapping API.

For details regarding the differences between the new and existing APIs, refer to the previous announcement.

Required Actions

Check the SAM User, Role, and Default Permission in your account. If either of the following applies, please update the permissions as soon as possible:

• If you have explicitly allowed or denied the existing PortMapping:createPortMapping API in a permission, and the corresponding user(s) should continue to be allowed or denied access to the On-Demand Remote Access feature
• Or if you want to use the new PortMapping:createPortMappingForSim API in order to restrict a user's On-Demand Remote Access feature to specific SIMs

For instructions on updating permissions, refer to the Users & Roles documentation.

Note that if either of the above applies but you do not update the permissions, the following may occur:

• A user who previously could create On-Demand Remote Access sessions from the User Console may no longer be able to do so
• A user who previously was not able to create On-Demand Remote Access sessions from the User Console may be able to do so

Additional Details

Please note that the existing PortMapping:createPortMapping API is not deprecated. You may continue using it without interruption.

If you have any questions, please contact Soracom Support.

We are pleased to announce new 60-day and 90-day Cloud Motion Detection Unlimited Recording License options for Soracom Cloud Camera Services (SoraCam).

With these new licenses, videos uploaded from a SoraCam compatible camera device will be stored for 60 and 90 days, respectively, allowing users to review footage from over a month ago, such as when managing construction sites, building projects, or other use cases that span several months.

Pricing

These Cloud Motion Detection Unlimited Recording License options are now available in addition to the existing 7-day, 14-day, and 30-day licenses. The 60-day and 90-day licenses are billed monthly per camera.

Details

For more information, please refer to the pricing information (Japanese) or the SoraCam product page (Japanese).

If you have any questions, please contact Soracom Support.

Please note that this service is currently only available for customers located in Japan.

We are excited to announce that planNT1, Soracom's NTN (Non-Terrestrial Network) satellite service subscription plan, is now officially available.

The planNT1 subscription can be added to an existing Soracom plan01s or plan-US IoT SIM through the use of Soracom's Subscription Container feature, enabling satellite coverage in addition to existing cellular networks for devices with 3GPP Release 17 NTN-compliant cellular modules. This allows compatible devices to keep using the extensive cellular network coverage provided by Soracom IoT SIMs while also providing satellite connectivity in other areas, without additional hardware or separate SIM.

As of today, planNT1 provides NTN satellite coverage in the United States, Canada, Brazil, Australia, New Zealand, and multiple European countries and cellular coverage in over 90 countries, with additional coverage planned.

For more information, please refer to Soracom Air for Satellite documentation.

If you have any questions, please contact Soracom Support.

A new group setting called "Skip Status Code" (skipStatusCode) has been added to the Soracom Funk UDP entry point and TCP entry point. When you enable this setting, Funk responses sent to devices omit the leading HTTP status code and the following space.

Background

Previously, when using the Funk UDP entry point or TCP entry point (*1), Funk responses always included a prefix in the Soracom Funk format: HTTP status code + space + response body returned by the Function as a Service (FaaS) function.

For simple device implementations that did not use the status code, or for custom protocols where leading numeric characters created compatibility issues, additional processing was required to remove this prefix.

(*1) This also applies when using a Unified Endpoint with the response format set to SORACOMFunk.

Added functionality

When you enable "Skip Status Code" in the group settings:

• The leading HTTP status code + space is removed from responses returned via the UDP entry point and TCP entry point.
• Whether the HTTP status code is in the 200 range or 400 and above, only the response body returned by the Function as a Service (FaaS) function is returned.
• Unified format responses (when using a Unified Endpoint with response format set to Unified) are not affected; the statusCode field remains included.

The Soracom CLI and Soracom API now include the skipStatusCode configuration parameter (Boolean). Set it to true to apply the same behavior programmatically.

For configuration steps and response examples, refer to the documentation below.

Documentation

• Soracom Funk Configuration

If you have any questions, please contact Soracom Support.