# Output

This section covers Benthos output plugins for writing data to various industrial systems and external destinations. Output plugins allow you to send processed data from your Benthos pipelines to PLCs, databases, message brokers, and other systems.

## Available Output Plugins

* [**OPC UA Output**](https://docs.umh.app/benthos-umh/output/opc-ua-output) - Writes data to OPC UA servers with optional read-back confirmation (handshake). Supports multiple data types and provides safe setpoint operations for industrial control systems.
* [**UNS Output**](https://docs.umh.app/benthos-umh/output/uns-output) - Publishes batched messages to the Unified Namespace in `umh-core`, auto-deriving `umh-topic`, sanitising keys, and writing them to the internal Kafka broker.
* [**Sparkplug B Output**](https://docs.umh.app/benthos-umh/output/sparkplug-b-output) - Publishes batched messages to an MQTT Broker with the protocol Sparkplug B.
* [**More Output Plugins**](https://docs.redpanda.com/redpanda-connect/components/outputs/about/) - Additional built-in output plugins available in Benthos/Redpanda Connect for various destinations.

## Choosing the Right Output Plugin

* Use **OPC UA Output** when writing setpoints, commands, or data back to OPC UA-enabled industrial systems with confirmation requirements
* Use **UNS Output** to publish data into the Unified Namespace via `umh-core`, where topics, batching, key sanitisation are handled automatically.
* Use **Sparkplug B Output** to publish data to an MQTT Broker, into a custom data pipeline. Sparkplug B is typically used for edge device use cases where state awareness is required.
* Explore **additional output plugins** for databases (PostgreSQL, MySQL, InfluxDB), message brokers (MQTT, Kafka), cloud services (AWS, Azure, GCP), file systems, HTTP APIs, and more