このページはまだ日本語では利用できません。現在は English版を表示しています。ブラウザの翻訳機能をご利用ください。
ブラウザで翻訳する
Chrome / Edge: アドレスバーの翻訳アイコン、またはページを右クリックして「日本語に翻訳」を選択します。
Safari: アドレスバーの「aA」メニューから「翻訳」を選択します。
翻訳メニューが表示されない場合は、ブラウザ設定で翻訳機能が有効になっているか確認してください。
Protocol Conversion & Forwarding
Soracom Beam forwards device data to external cloud endpoints while handling protocol conversion and credential injection on behalf of the device. This offloads TLS processing and secret management from constrained IoT hardware.
What it does
- HTTP/MQTT/TCP/UDP forwarding — Route device data to any cloud endpoint over multiple protocols
- TLS termination — Beam handles TLS on behalf of devices, reducing power and memory requirements
- Credential injection — Attach API keys, tokens, or certificates to outbound requests without storing secrets on devices
- Protocol conversion — Transform traffic between protocols, such as TCP-to-HTTPS or UDP-to-MQTT
What to scale to next
After Beam is in place, teams typically add these Scale-tier services as requirements expand:
- Direct Cloud Delivery — Use when you need managed integrations to specific cloud services with less endpoint-by-endpoint maintenance.
- Soracom VPG — Use when security requirements call for private routing and tighter network isolation to cloud or on-prem destinations.
- Soracom Flux — Use when forwarding decisions become workflow-driven (branching, retries, automations, and downstream actions).
Related
- Data Entry Point — Single ingress URL that routes to Beam
- Serverless Triggers — Invoke cloud functions directly from device data
- Credentials Store — Manage credentials used by Beam