Before dissecting version 3.0.7, it is essential to understand the parent platform. X-teko is a hybrid middleware solution designed to bridge communication between legacy hardware protocols and modern cloud-based APIs. Originally developed for industrial automation and later adapted for IoT (Internet of Things) gateways, x-teko provides:
The software’s modular architecture allows it to run on minimal hardware—such as Raspberry Pi, ARM-based gateways, or even containerized within Docker on x86 servers. Over the years, x-teko has gained a cult following for its reliability in harsh environments, from factory floors to remote weather stations. x-teko v3.0.7
Upgrading from any previous 3.x version is straightforward. However, due to the security and connector changes, a direct in-place upgrade is not recommended for production without testing. Before dissecting version 3
Some configuration keys have been renamed or deprecated. Pay attention to these critical differences: The software’s modular architecture allows it to run
| Old (v3.0.6) | New (v3.0.7) | Action |
|--------------|--------------|--------|
| connector.pool.max | connector.pool.max_connections | Rename |
| log.format=text | log.format=json (default) | Update |
| security.legacy_auth | (removed) | Use oauth2 or mtls |
| queue.batch.size | queue.batch.size_bytes | Type changed to bytes |
If you use a configuration management tool (Ansible, Puppet), update your templates before deploying x-teko v3.0.7.
Organizations are already deploying this version in production. Here are three examples.
You’ll receive an email with download link shortly.
If not, reach us on solviamarketing@solviads.com