What you’d build without Soracom Flux
|
Custom backend for every use case
DIY AI integration and orchestration
Ad-hoc scripts for automation and device control |
Application Development Service
Soracom Flux
Low-Code IoT Application and Automation Builder
Build intelligent IoT applications using natural language instead of writing backend code
Create “Flux Apps” using an interactive visual interface and natural language prompts. Powered by generative AI and AWS managed services, Flux connects device data, images, and video to AI models and automation rules, so teams can build full workflows without deep programming expertise.
Turn device data, images, and video into automated actions
Flux Apps run on an event-driven, serverless architecture. They can react when devices send data, when files arrive in Harvest Files, when timers fire, or when webhooks are received. From there, Flux can send Slack or email alerts, call external webhooks, invoke AI models for text, image, or video analysis, or automate tasks through the Soracom API—like changing SIM status, tagging devices, or sending remote commands. Flux App Templates and AI-powered actions dramatically lower the barrier for building production-ready IoT workflows across logistics, retail, operations, and more.
Why use Soracom Flux for your project?
Make IoT apps accessible
Let non-engineers build useful applications and automations without standing up a full backend.
Bring AI into operations
Use generative AI to interpret sensor data, images, and video for smarter decision-making.
Orchestrate across services
Connect Soracom connectivity, device management, and external systems through one low-code automation layer.
How it works
Low-code IoT application builder with AI assistance
Use Flux’s visual interface to define event sources, rules, and actions—no need to stand up servers or write complex backend code. Natural language prompts help generate automation logic, making it easier for non-engineers to assemble apps that respond to device data, file uploads, or webhooks. Flux App Templates provide pre-built workflows you can clone and customize for common IoT scenarios.
Keep credentials and security in the cloud, not on the device
With Funnel, IAM roles, SAS tokens, and other credentials are stored and managed in the Soracom platform, never on the device. Devices send plain HTTP/TCP/UDP packets to a single Funnel endpoint, while Soracom injects the right keys and tokens in the cloud, reducing your attack surface and simplifying credential rotation.
AI Actions for text, images, and video
Flux integrates with AI models on platforms like Amazon Bedrock and Google Gemini. AI Actions can analyze text, sensor values, images, and now video clips, enabling use cases like anomaly detection in warehouses, reading analog gauges from photos, or reviewing work procedures from captured video segments. You define what you want in natural language, Flux handles the AI calls.
Key takeways for those that use Flux
Make IoT apps accessible
Let non-engineers build useful applications and automations without standing up a full backend.
Bring AI into operations
Use generative AI to interpret sensor data, images, and video for smarter decision-making.
Orchestrate across services
Connect Soracom connectivity, device management, and external systems through one low-code automation layer.
Architecture and implementation
Soracom Flux runs on a scalable, serverless architecture built on AWS services like AWS Lambda, Amazon Kinesis Data Streams, and Amazon DynamoDB. Event sources—device data, timers, file uploads to Harvest Files, or incoming webhooks—trigger Flux Apps defined in a visual builder. Within each app, actions can call AI models, send notifications, invoke webhooks, or use the Soracom API for device and SIM management. Flux App Templates provide curated, pre-built workflows that you can adapt without writing code, while Flux Video Analysis expands AI Actions to support video clips as well as images and text.
Step 1
Create a new Flux App and select your event source
Open the Soracom User Console and navigate to the Flux section to create a new Flux App.
Choose the event source that will trigger your workflow—such as incoming device data, a scheduled timer, a webhook, or a file uploaded to Harvest Files.
Flux uses an event-driven architecture, allowing your app to react automatically whenever data arrives or a condition is met, without building your own server backend.
Learn more about event sources in the Flux event source documentation.
Step 2
Add actions and optional AI processing to define your workflow logic
Use the Flux visual builder to add actions that run whenever your event source triggers—such as sending notifications, invoking webhooks, calling the Soracom API, or modifying data before forwarding it.
Optionally add AI Actions to analyze text, images, or video using models from Amazon Bedrock or Google Gemini, enabling automations based on intelligent interpretation of your data.
Flux Apps require no backend infrastructure, and most logic can be built without coding, though advanced use cases can include custom expressions or object handling.
Review available actions in the Flux action guide.
Step 3
Test, deploy, and monitor your Flux App to automate your IoT workflows
Use the Flux console to test your workflow with sample data, confirm AI results, and ensure your actions behave as expected.
Once deployed, Flux automatically processes events at scale, with no servers or pipelines to maintain.
Monitor execution logs and app history to validate behavior, troubleshoot issues, or optimize your rules over time.
See monitoring options in the Flux monitoring documentation.
How Soracom Flux works with other Soracom services
|
Flux + Harvest / Harvest Files for data and media workflows
Flux + Inventory for low-code device management
Flux + Beam/Funnel/Funk for hybrid cloud integration
Flux + Lagoon / Query for insight-to-action loops |
Start streaming with Soracom Funnel
Create a free Soracom account, connect a test device, and configure Funnel to deliver data into your preferred cloud service in minutes—no relay servers or SDKs required.
Build AI-powered IoT workflows with Soracom Flux
Frequently Asked Questions
What is Soracom Flux?
Soracom Flux is a low-code IoT application builder that uses generative AI and AWS managed services to help you create event-driven workflows from device data, images, and video—without building a custom backend.
Do I need to know how to code to use Flux?
Basic technical familiarity helps, but you don’t need to be a software engineer. Flux Apps can often be built and customized through the low-code interface, natural language prompts, and templates.
What kinds of actions can Flux perform?
Flux can send Slack or email notifications, call webhooks, analyze text/images/video with AI models, and use the Soracom API to manage SIMs, update tags, or send commands through services like Remote Command or SMS.
How is Flux different from Soracom Inventory?
Inventory focuses on device management (LwM2M, status, health, configuration), while Flux is a low-code automation and application layer that can use Inventory and other Soracom services via the API to orchestrate actions.
Who is Flux for?
Flux is designed for both engineers and non-engineers. Developers can move faster by offloading boilerplate backend work, while operations, support, and business teams can build and modify workflows through a visual interface and templates.
What can trigger a Flux App?
Flux Apps can be triggered by IoT device data, timers, incoming webhooks, and file uploads to Soracom Harvest Files (including images and video clips).
How does Flux handle AI model integration?
Flux AI Actions connect to models on platforms like Amazon Bedrock and Google Gemini. You specify what you want in natural language, and Flux takes care of sending the data and returning AI-generated results to your workflow.
What plans are available for Flux?
Flux offers a Developer plan that lets you start experimenting for free, with Standard and Enterprise plans available for larger-scale workloads and higher usage, including AI-related credit consumption.