Documentation

ConX-SFP eliminates rack space, power feeds, and long cable runs. See the detailed comparison.

Yes. ConX-SFP converts RS-232 serial to Ethernet (serial over IP) inside a standard 1G SFP module. It functions as an RS-232 to Ethernet converter with cloud or on-premises management — no external serial device server required.

Anything with a spare 1G SFP slot and a serial console port — routers, switches, firewalls, PDUs, servers with RS-232, broadband gateways, and industrial equipment. Works with Cisco, Juniper, Arista, MikroTik, Palo Alto, and more.

Username: weta, Password: wetatronics. SSH on port 22, telnet on port 23. See the Quick Start Guide for full default settings.

One RS-232 port with a standard ethernet cable, or two RS-232 ports using the breakout cable. Each ConX-SFP unit is independent.

Currently yes — ConX-SFP emulates a 1000BASE-LX SFP and requires speed negotiation disabled on the host interface. See the Quick Start Guide for Cisco, Juniper, and MikroTik examples.

DHCP by default. If DHCP times out, it falls back to static IP 192.168.0.232/24. Static addressing can be configured via the serial CLI.

Yes. With ConX Portal, ConX-SFP acts as a jump host — you can reach any IP-reachable host at the site (servers, appliances, out-of-band controllers) over SSH, Telnet, RDP, HTTP, or HTTPS from your browser, including devices with no serial port at all. A lightweight agent extends this to any TCP port on any host.

Directly from the browser: SSH, Telnet, RDP, HTTP, and HTTPS to remote hosts. A separate lightweight agent adds pass-through to any TCP port on any remote host. All jump-host traffic rides ConX-SFP's outbound-only TLS tunnel — no VPN and no inbound firewall rules.

Jump-host access runs through ConX Portal over ConX-SFP's outbound-only TLS tunnel — no inbound firewall rules. Access is governed by role-based permissions scoped per user and group, and every session is access-controlled and recorded with a full audit trail.

ConX-SFP establishes an outbound TLS 1.3 WebSocket to the ConX Portal — it looks like regular HTTPS traffic and works through any firewall, NAT, or CGNAT. You then open a browser-based terminal session through the portal. No VPN, no inbound firewall rules, no SSH client required.

The dashboard shows all your devices with real-time online/offline status, serial console logs, alert history, activity feed, and detailed device information including uptime, CPU temperature, serial configuration, firmware version, and connection history. Devices can be organized into groups by site, customer, or function.

Yes. ConX Portal provides full-text search across all devices, ports, and time ranges. You can save and share queries, stream live console output with the live tail feature, and export logs as CSV or raw text.

Yes. You can create custom alert rules — for example, trigger when a device goes offline or when a specific pattern appears in console output. Alerts are delivered via HMAC-SHA256 signed webhooks to Slack, PagerDuty, ServiceNow, or any HTTP endpoint. Cooldown periods prevent alert fatigue.

Use the 3-step device claiming process: start a claim in the portal, enter the verification code on the device, and confirm. Once claimed, the device auto-registers whenever it powers on and connects to the network.

Yes. ConX Portal provides a REST API with scoped API keys for automation and CI/CD integration. You can also use webhooks for event-driven workflows and scheduled actions for recurring tasks like health checks or config backups.

No. ConX-SFP uses DHCP on-site and connects outbound to the ConX Portal via TLS. No VPN, no inbound firewall rules. For environments that prohibit internet access, deploy the on-premises portal.

Yes. Deploy the ConX Portal on-premises for a fully self-contained, internet-independent setup. Same features, fully local. ConX-SFP supports FIPS-ready cipher suites.

Both options run the same portal with the same features. Cloud (SaaS) is hosted and managed by Wetatronics with zero infrastructure to manage — isolated tenant architecture, automatic updates and scaling, a 99.9% uptime SLA, and global edge presence. On-Premises deploys on your own infrastructure for air-gapped or sovereign environments — Docker-based, fully self-contained with no internet dependency and full data sovereignty.

Yes. The On-Premises deployment is Docker-based and fully self-contained — it runs entirely on your own infrastructure with no internet dependency, giving you full data sovereignty. It offers the same features as the cloud version, making it suitable for air-gapped, classified, and regulated environments.