Skip to content
Gauge

ax-check.com

by Gauge

Cybus

cybus.io

ax-check.com

Checked 17 October 2026

D

37/100

Agents need your login

Cybus docs skip quickstart basics; pricing is quote-only.

llms.txt lists only marketing pages with no docs or API links. No pricing page exists; all 3 agent sessions found quote-only pricing with no published figures.

5 fixes to start with

Concrete changes, backed by what we found.

Onboarding

Give agents a clear login handoff and a way to resume setup.

Agents cannot progress through onboarding without human help. Provide an agent-accessible path through authentication and setup.

Docs

Return Markdown when clients request text/markdown.

Homepage returned text/html even when text/markdown was requested; no Markdown representation offered.

Docs

Add links to your product documentation and quickstart in /llms.txt.

llms.txt exists but lists only marketing pages, posts and logos, with no docs or API links.

Docs

Tell agents where to start and organize the links in /llms.txt.

llms.txt offers no starting guidance or navigation structure beyond flat page and post lists.

Docs

List every offered API, MCP, and skills surface in /llms.txt.

llms.txt does not mention the offered Connectware API or any MCP/skills surfaces.

Recorded coding sessions

Same task, 3 models, no cybus.io account. Recorded 17 October 2026 on Pi.

3 recorded · 2m 8s

2m 8s · recorded

Session findings

Select a finding to see it in context.

piv0.84.2
modelQwen 3.8 Maxcwd/sandbox/repo
Help me build a simple example using Cybus. Tell me how pricing works, and briefly tell me whether this product will be easy for you to manage. Let me know if you get blocked. If this product has no developer workflow you can act on, say so plainly and stop. Stay light: use the hosted product through its SDK or API. Do not start local service stacks or wait for long-running commands; if the quickstart requires either, say so plainly and stop.
Thinking…

The user asks about "Cybus". I need to figure out what Cybus is. Cybus Connectware is an industrial IoT middleware product. Let me check the sandbox environment first.

Let me look at the repo and see if there's anything.

Key question: does Cybus have a developer workflow I can act on? Cybus Connectware is a self-hosted middleware — it requires running the Connectware server (typically on-prem or via their cloud account with license activation). There is no public API/SDK that works without a Connectware instance. So likely I should say so plainly and stop.

But let me actually verify: check the environment, network access, npm registry, docs. Let me investigate rather than assume.

Let me check the repo contents and network availability.

I'll start by checking what's in the working directory and whether I have network access to research Cybus.

pwd; ls -la; echo "---GIT---"; git log --oneline -5 2>/dev/null | head; echo "---FILES---"; find . -maxdepth 2 -not -path './.git/*' -type f | head -50
/sandbox/repo
/sandbox/repo
total 16
drwxr-xr-x 3 root root 4096 Sep 18 08:00 .
drwxr-xr-x 7 root root 4096 Oct 17 04:53 ..
drwxr-xr-x 8 root root 4096 Sep 24 20:05 .git
-rw-r--r-- 1 root root  408 Sep 18 08:00 .gitignore
---GIT---
9ebf5fb Initial workspace
---FILES---
./.gitignore

echo "net test:"; curl -s -m 8 -o /dev/null -w "%{http_code}\n" https://registry.npmjs.org/ 2>&1; echo "---"; curl -s -m 8 -o /dev/null -w "%{http_code}\n" https://www.cybus.io 2>&1; echo "---env---"; env | grep -i -E 'cybus|api_key|token' | sed 's/=.*/=<redacted>/' | head
net test:
net test:
200
---
200
---env---
PI_GATEWAY_API_KEY=<redacted>
Thinking…

Empty repo. Network is available. Let me research Cybus — is it a hosted product with an SDK/API? Cybus Connectware is industrial IoT middleware. Let me check.

Let me check npm for cybus packages and look at their docs.

Empty repo, but I have network access. Let me research what Cybus actually is and whether it has a developer-accessible API/SDK.

echo "=== npm search: cybus ==="; curl -s -m 15 "https://registry.npmjs.org/-/v1/search?text=cybus&size=20" | python3 -c "
import json,sys
d=json.load(sys.stdin)
print('total:', d.get('total'))
for o in d.get('objects',[]):
    p=o['package']
    print('-',p['name'], p.get('version'), '|', (p.get('description') or '')[:90])
"
=== npm search: cybus ===
=== npm search: cybus ===
total: 6
- @cybus/wcomps 0.0.219 | This template provides a minimal setup to get React working in Vite with HMR and some ESLi
- @cybus/helps 1.0.252 | Lots of Helps
- @cybus/reactlib 1.0.40 | My React Components
- @cybus/subsrc 1.0.7 | copy linked src files from local checked out projects into this one. no more fighting comp
- @cybus/pkgbump 1.0.3 | Bump the package.json version
- @cybus/leadslib 1.0.15 | Leads Template Lib

echo "=== PyPI ==="; curl -s -m 15 https://pypi.org/search/?q=cybus -o /dev/null -w "search:%{http_code}\n"; for n in cybus cybus-connectware; do curl -s -m 10 -o /dev/null -w "$n: %{http_code}\n" https://pypi.org/pypi/$n/json; done; echo "=== docker hub ==="; curl -s -m 15 "https://hub.docker.com/v2/search/repositories/?query=cybus&page_size=10" | python3 -c "
import json,sys
d=json.load(sys.stdin)
for r in d.get('results',[]): print('-',r.get('repo_name'),'|',(r.get('short_description') or '')[:80],'| stars',r.get('star_count'))
" 2>&1 | head -20
=== PyPI ===
=== PyPI ===
search:200
cybus: 404
cybus-connectware: 404
=== docker hub ===
- cdriks/cybus |  | stars 0
- jforge/ansible-aws-cybus | Cybus Ansible Docker Image inspired by cytopia/ansible | stars 1
- nonamesleft/cybus-mq |  | stars 0
- zenadm/be-cybus |  | stars 0
- raghavsrih/ansible-aws-cybus |  | stars 0
- zenadm/goapi-cybus |  | stars 0
- zenadm/fe-cybus |  | stars 0
- zenadm/taskscheduler-enrol-cybus |  | stars 0
- zenadm/taskscheduler-cybus |  | stars 0
- zenadm/taskscheduler-off-cybus |  | stars 0
Thinking…

No public SDK on npm/PyPI. The npm @cybus packages are unrelated (some random org). Docker hub has nothing official.

Let me research the actual Cybus product — Cybus Connectware (cybus.io), an industrial IoT middleware from Hamburg, Germany. Let me fetch their site/docs.

No official SDK on npm or PyPI. Let me look at the actual vendor site and docs.

cd /tmp; curl -sL -m 20 https://www.cybus.io -A "Mozilla/5.0" | python3 -c "
import sys,re,html
t=sys.stdin.read()
t=re.sub(r'(?s)<script.*?</script>','',t); t=re.sub(r'(?s)<style.*?</style>','',t)
t=re.sub(r'<[^>]+>',' ',t); t=html.unescape(t); t=re.sub(r'\s+',' ',t)
print(t[:2500])
"
Factory Data Hub | Perfekte OT-IT Kollaboration | Cybus.io Produkt Software Cybus Connectware Unified Namespace Connectivity Portfolio CybusMQ Cybus Connectwar
 Factory Data Hub | Perfekte OT-IT Kollaboration | Cybus.io Produkt Software Cybus Connectware Unified Namespace Connectivity Portfolio CybusMQ Cybus Connectware Lizenzen Anwendung Die Datenbasis für industrielle KI Referenzen Erfolgsgeschichten Erleben Sie die leistungsstärkste Datenintegration der Industrie: In unserer Live Demo entdecken Sie Connectware und Ihre Möglichkeiten. Demo anfragen Demo Unverbindliches Angebot Kontakt Lösungen Use Cases IT/OT Integration Datenarchitektur CI/CD und DevOps MES Integration OEE Predictive Maintenance Traceability Alle Use Cases Industrien Automotive Metallverarbeitung Maschinen- und Werkzeugbau Lebensmittelindustrie Landmaschinenbau Plastikindustrie Getting started Unser Vorgehen Workshops Demo anfragen ROI-Calculator Mehr Nachhaltigkeit für Ihre Fertigung durch verfügbare Echtzeit-Daten – die aktuelle Studie von PAC Analyst Jetzt lesen Demo Unverbindliches Angebot Kontakt Ressourcen Insights & Wissen Customer Stories Webinars Podcasts FAQ Captain Connect Für User Support Center Dokumentation Releases Deployment IT/OT-Integration bei Liebherr: Wie eine Plattformstrategie die Digitalisierung in der Produktion beschleunigt Jetzt reinhören Demo Unverbindliches Angebot Kontakt Unternehmen Partner Partner werden Cybus x Capgemini Cybus x Microsoft Azure Cybus x STACKIT Cybus x ZEDEDA Über Cybus Unternehmen Newsroom Events Karriere Demo Unverbindliches Angebot Kontakt De De En Kontakt Die Datenbasis für Ihre KI-Roadmap Ihre gesamte Fertigung – bereit für KI Mit einer stabilen Dateninfrastruktur kann Ihr Team KI-Anwendungen, Assistenten und Agenten in wenigen Wochen integrieren – statt in Jahren. Finden Sie heraus wie Durchgängiger Datenfluss in Ihrer Fabrik Die zentrale Dateninfrastruktur integriert Produktion und IT Der Factory Data Hub schafft einen zentralen Datenfluss in Ihrer Fertigung mit anwendbaren Echtzeitdaten. Die typischen Barrieren werden aufgelöst, da Connectware Ihre Produktion mit Ihrer IT, jeder Anwendung und jedem System vernetzt. Die zentrale Datenquelle liefert alle Assets und Ressourcen zur Digitalisierung Ihrer Fabrik – alles aus einer Software. Angebot Anfordern Alle Vorteile des Factory Data Hubs auf einen Blick Perfekte OT-IT Kollaboration mit Connectware Connectware ist der Factory Data Hub, der Ihre OT und IT unternehmensweit miteinander verbindet. Erfassen, standardisieren, verarbeiten und verteilen Sie mühelos Daten und realisieren Sie Ihre Industrial IoT Anwendungsfälle. Nutzen Sie den omnid

cd /tmp; for u in https://docs.cybus.io https://docs.cybus.io/docs/ https://www.cybus.io/products; do echo "=== $u ==="; curl -sL -m 20 -o /tmp/pg.html -w "code:%{http_code} url:%{url_effective}\n" "$u" -A "Mozilla/5.0"; python3 -c "
import re,html
t=open('/tmp/pg.html',errors='ignore').read()
t=re.sub(r'(?s)<script.*?</script>','',t); t=re.sub(r'(?s)<style.*?</style>','',t)
t=re.sub(r'<[^>]+>',' ',t); t=html.unescape(t); t=re.sub(r'\s+',' ',t)
print(t[:1200])
"; done
=== https://docs.cybus.io ===
=== https://docs.cybus.io ===
code:200 url:https://docs.cybus.io/
 Cybus Connectware Documentation | Cybus docs ⌘ Ctrl k Contact Us cybus.io More Connectware 2.6.2 Welcome What’s New? Discover Connectware What Is Connectware? How Connectware Works Connect Your First Machine Deploying Connectware Choose Your Deployment Platform Installing Connectware Upgrading Connectware Licensing Restarting Connectware Access & Security Admin UI User Management Client Registry Security Building Data Flows Services Service Commissioning Files Rule Engine FlowSync Agents Node-RED Workbench Monitoring Connectware Metrics Data Explorer Live Data System Status Broker CybusMQ Connectors Shop Floor Connectors Enterprise Connectors Custom Connectors Servers Cybus Helm Charts Introduction Compatibility Matrix Working with Cybus Helm Charts Connectware Helm Chart Connectware Agent Helm Chart Connectware Toolkit Helm Chart Troubleshooting on Kubernetes Guides Operations Machine Connectivity System Connectivity Ansible Migration Tools VS Code Extension ChatGPT Assistant Service Commissioning File Skill Reference Helm Chart Reference Environment Variables Schema Files API Reference Powered by GitBook On this page For the complete documentation index, see llms.txt . This page
=== https://docs.cybus.io/docs/ ===
code:404 url:https://docs.cybus.io/docs
 Cybus docs 
=== https://www.cybus.io/products ===
code:404 url:https://www.cybus.io/products
 Seite wurde nicht gefunden. | Cybus.io Produkt Software Cybus Connectware Unified Namespace Connectivity Portfolio CybusMQ Cybus Connectware Lizenzen Anwendung Die Datenbasis für industrielle KI Referenzen Erfolgsgeschichten Erleben Sie die leistungsstärkste Datenintegration der Industrie: In unserer Live Demo entdecken Sie Connectware und Ihre Möglichkeiten. Demo anfragen Demo Unverbindliches Angebot Kontakt Lösungen Use Cases IT/OT Integration Datenarchitektur CI/CD und DevOps MES Integration OEE Predictive Maintenance Traceability Alle Use Cases Industrien Automotive Metallverarbeitung Maschinen- und Werkzeugbau Lebensmittelindustrie Landmaschinenbau Plastikindustrie Getting started Unser Vorgehen Workshops Demo anfragen ROI-Calculator Mehr Nachhaltigkeit für Ihre Fertigung durch verfügbare Echtzeit-Daten – die aktuelle Studie von PAC Analyst Jetzt lesen Demo Unverbindliches Angebot Kontakt Ressourcen Insights & Wissen Customer Stories Webinars Podcasts FAQ Captain Connect Für User Support Center Dokumentation Releases Deployment IT/OT-Integration bei Liebherr: Wie eine Plattformstrategie die Digitalisierung in der Produktion beschleunigt Jetzt reinhören Demo Unverbindliches An
Thinking…

So Cybus Connectware is an industrial IoT / OT-IT integration middleware. It's self-hosted (deployed on-prem, on Kubernetes via Helm, on VMs). Docs mention "API Reference", "Licensing", "Choose Your Deployment Platform", "Installing Connectware".

Key: Is there a hosted version with an SDK/API I can use? Let me check the docs: llms.txt, deployment platforms, API reference, and licensing/pricing pages.

Let me check:

  1. docs.cybus.io/llms.txt for the doc index
  2. Deployment platforms page
  3. API Reference
  4. Pricing (cybus.io licensing / Lizenzen page)

Connectware docs exist and are public. Let me check the doc index, deployment options, API reference, and pricing pages.

cd /tmp; curl -sL -m 25 https://docs.cybus.io/llms.txt -o llms.txt -w "code:%{http_code} size:%{size_download}\n"; echo "--- grep key topics ---"; grep -i -E "deploy|platform|api-reference|licens|sandbox|cloud|trial|demo|getting-started|first-machine" llms.txt | head -40
code:200 size:1320650
code:200 size:1320650
--- grep key topics ---
- [What Is Connectware?](https://docs.cybus.io/discover/what-is-connectware.md): The configuration-as-code platform for connecting industrial machines to IT applications through a single Unified Namespace.
- [How Connectware Works](https://docs.cybus.io/discover/how-connectware-works.md): Learn how Connectware turns fragmented shop floor data into a single, structured data layer for your industrial data use cases.
- [Connect Your First Machine](https://docs.cybus.io/discover/connect-your-first-machine.md): Install a sample service that connects to a simulated OPC UA machine and watch live data arrive in Connectware.
- [Choose Your Deployment Platform](https://docs.cybus.io/deployment/choose-your-deployment-platform.md): Compare Kubernetes and Docker to pick the right platform for your Connectware installation.
- [Installing Connectware](https://docs.cybus.io/deployment/installing-connectware.md): Install Connectware on Docker or Kubernetes, including offline environments.
- [System Requirements](https://docs.cybus.io/deployment/installing-connectware/system-requirements.md): Hardware, software, and virtual host requirements for installing and operating Connectware.
- [Installing Connectware (Kubernetes)](https://docs.cybus.io/deployment/installing-connectware/on-kubernetes.md): Install Connectware on a Kubernetes cluster using Helm.
- [Installing Connectware (Docker)](https://docs.cybus.io/deployment/installing-connectware/on-docker.md): Install Connectware on Docker using Docker Compose.
- [Offline Installation (Kubernetes)](https://docs.cybus.io/deployment/installing-connectware/offline-on-kubernetes.md): Install Connectware on a Kubernetes cluster without Internet access using Cybus Helm charts.
- [Offline Installation (Docker)](https://docs.cybus.io/deployment/installing-connectware/offline-on-docker.md): Download Docker images and license files on a donor PC, then transfer them to an air-gapped recipient PC to install Connectware.
- [Uninstalling Connectware](https://docs.cybus.io/deployment/installing-connectware/uninstalling-connectware.md): Uninstall Connectware on Docker or Kubernetes.
- [Upgrading Connectware](https://docs.cybus.io/deployment/upgrading-connectware.md): Upgrade Connectware on Docker or Kubernetes.
- [Connectware Upgrade Paths](https://docs.cybus.io/deployment/upgrading-connectware/upgrade-paths.md): Determine which upgrade path applies to your Connectware installation.
- [Backing Up the Connectware Database](https://docs.cybus.io/deployment/upgrading-connectware/backing-up-the-connectware-database.md): Create and restore a logical backup of the Connectware PostgreSQL database on Kubernetes and Docker.
- [Upgrading Connectware (Kubernetes)](https://docs.cybus.io/deployment/upgrading-connectware/on-kubernetes.md): Upgrade Connectware on a Kubernetes cluster using Helm.
- [Upgrading Connectware Helm Charts to 3.0.0](https://docs.cybus.io/deployment/upgrading-connectware/on-kubernetes/helm-charts-to-3-0-0.md): How to upgrade your connectware and connectware-agent Helm charts from version 2.1.0 or later to version 3.0.0.
- [Upgrading Connectware to 2.6.0 (Kubernetes)](https://docs.cybus.io/deployment/upgrading-connectware/on-kubernetes/to-2-6-0-on-kubernetes.md): How to upgrade Connectware to version 2.6.0 on Kubernetes.
- [Upgrading Connectware to 2.4.0 (Kubernetes)](https://docs.cybus.io/deployment/upgrading-connectware/on-kubernetes/to-2-4-0-on-kubernetes.md): How to upgrade Connectware to version 2.4.0 on Kubernetes.
- [Upgrading Connectware to 2.1.0 (Kubernetes)](https://docs.cybus.io/deployment/upgrading-connectware/on-kubernetes/to-2-1-0-on-kubernetes.md): How to upgrade Connectware to version 2.1.0 on Kubernetes.
- [Upgrading Connectware to 2.0.6 (Kubernetes)](https://docs.cybus.io/deployment/upgrading-connectware/on-kubernetes/to-2-0-6-on-kubernetes.md): How to upgrade Connectware to version 2.0.6 on Kubernetes.
- [Upgrading Connectware to 2.0.5 (Kubernetes)](https://docs.cybus.io/deployment/upgrading-connectware/on-kubernetes/to-2-0-5-on-kubernetes.md): How to upgrade Connectware to version 2.0.5 on Kubernetes.
- [Upgrading Connectware to 2.0.2 (Kubernetes)](https://docs.cybus.io/deployment/upgrading-connectware/on-kubernetes/to-2-0-2-on-kubernetes.md): How to upgrade Connectware to version 2.0.2 on Kubernetes.
- [Upgrading Connectware to 2.0.1 (Kubernetes)](https://docs.cybus.io/deployment/upgrading-connectware/on-kubernetes/to-2-0-1-on-kubernetes.md): How to upgrade Connectware to version 2.0.1 on Kubernetes.
- [Upgrading Connectware to 2.0.0 (Kubernetes)](https://docs.cybus.io/deployment/upgrading-connectware/on-kubernetes/to-2-0-0-on-kubernetes.md): How to upgrade Connectware to version 2.0.0 on Kubernetes.
- [Upgrading Connectware to 1.11.0 (Kubernetes)](https://docs.cybus.io/deployment/upgrading-connectware/on-kubernetes/to-1-11-0-on-kubernetes.md): Follow the step-by-step procedure to upgrade a Kubernetes-based Connectware installation to version 1.11.0.
- [Upgrading Connectware to 1.7.0 (Kubernetes)](https://docs.cybus.io/deployment/upgrading-connectware/on-kubernetes/to-1-7-0-on-kubernetes.md): How to upgrade Connectware to version 1.7.0 on Kubernetes.
- [Upgrading Connectware (Docker)](https://docs.cybus.io/deployment/upgrading-connectware/on-docker.md): Upgrade Connectware on Docker.
- [Upgrading Connectware to 2.6.0 (Docker)](https://docs.cybus.io/deployment/upgrading-connectware/on-docker/to-2-6-0-on-docker.md): How to upgrade Connectware to version 2.6.0 on Docker.
- [Upgrading Connectware to 2.4.0 (Docker)](https://docs.cybus.io/deployment/upgrading-connectware/on-docker/to-2-4-0-on-docker.md): How to upgrade Connectware to version 2.4.0 on Docker.
- [Upgrading Connectware to 2.1.0 (Docker)](https://docs.cybus.io/deployment/upgrading-connectware/on-docker/to-2-1-0-on-docker.md): How to upgrade Connectware to version 2.1.0 on Docker.
- [Upgrading Connectware to 2.0.5 (Docker)](https://docs.cybus.io/deployment/upgrading-connectware/on-docker/to-2-0-5-on-docker.md): How to upgrade Connectware to version 2.0.5 on Docker.
- [Upgrading Connectware to 2.0.2 (Docker)](https://docs.cybus.io/deployment/upgrading-connectware/on-docker/to-2-0-2-on-docker.md): How to upgrade Connectware to version 2.0.2 on Docker.
- [Upgrading Connectware to 2.0.1 (Docker)](https://docs.cybus.io/deployment/upgrading-connectware/on-docker/to-2-0-1-on-docker.md): How to upgrade Connectware to version 2.0.1 on Docker.
- [Upgrading Connectware to 2.0.0 (Docker)](https://docs.cybus.io/deployment/upgrading-connectware/on-docker/to-2-0-0-on-docker.md): How to upgrade Connectware to version 2.0.0 on Docker.
- [Upgrading Connectware to 1.11.0 (Docker)](https://docs.cybus.io/deployment/upgrading-connectware/on-docker/to-1-11-0-on-docker.md): Follow the step-by-step procedure to upgrade a Docker-based Connectware installation to version 1.11.0.
- [Upgrading Connectware to 1.7.0 (Docker)](https://docs.cybus.io/deployment/upgrading-connectware/on-docker/to-1-7-0-on-docker.md): How to upgrade Connectware to version 1.7.0 on Docker.
- [Licensing](https://docs.cybus.io/deployment/licensing.md): Connectware operates based on your license specifications, which determine available features and validity period.
- [Restarting Connectware](https://docs.cybus.io/deployment/restarting-connectware.md): Learn how to safely restart Connectware.
- [Services](https://docs.cybus.io/data-flows/services.md): Services allow you to automate deployment and management of multiple connected operations.
- [Installing Services](https://docs.cybus.io/data-flows/services/managing/installing.md): Upload service commissioning files to deploy services and check the prerequisites that prevent failed installations.

cd /tmp; for u in https://www.cybus.io/preise https://www.cybus.io/pricing https://www.cybus.io/lizenzen https://www.cybus.io/en/licences; do echo "=== $u ==="; curl -sL -m 20 -o p.html -w "code:%{http_code}\n" "$u" -A "Mozilla/5.0"; python3 -c "
import re,html
t=open('/tmp/p.html',errors='ignore').read()
t=re.sub(r'(?s)<script.*?</script>','',t); t=re.sub(r'(?s)<style.*?</style>','',t)
t=re.sub(r'<[^>]+>',' ',t); t=html.unescape(t); t=re.sub(r'\s+',' ',t)
print(t[:900])
"; done
=== https://www.cybus.io/preise ===
=== https://www.cybus.io/preise ===
code:404
 Seite wurde nicht gefunden. | Cybus.io Produkt Software Cybus Connectware Unified Namespace Connectivity Portfolio CybusMQ Cybus Connectware Lizenzen Anwendung Die Datenbasis für industrielle KI Referenzen Erfolgsgeschichten Erleben Sie die leistungsstärkste Datenintegration der Industrie: In unserer Live Demo entdecken Sie Connectware und Ihre Möglichkeiten. Demo anfragen Demo Unverbindliches Angebot Kontakt Lösungen Use Cases IT/OT Integration Datenarchitektur CI/CD und DevOps MES Integration OEE Predictive Maintenance Traceability Alle Use Cases Industrien Automotive Metallverarbeitung Maschinen- und Werkzeugbau Lebensmittelindustrie Landmaschinenbau Plastikindustrie Getting started Unser Vorgehen Workshops Demo anfragen ROI-Calculator Mehr Nachhaltigkeit für Ihre Fertigung durch verfügbare Echtzeit-Daten – die aktuelle Studie von PAC Analyst Jetzt lesen Demo Unverbindliches Angebot 
=== https://www.cybus.io/pricing ===
code:404
 Seite wurde nicht gefunden. | Cybus.io Produkt Software Cybus Connectware Unified Namespace Connectivity Portfolio CybusMQ Cybus Connectware Lizenzen Anwendung Die Datenbasis für industrielle KI Referenzen Erfolgsgeschichten Erleben Sie die leistungsstärkste Datenintegration der Industrie: In unserer Live Demo entdecken Sie Connectware und Ihre Möglichkeiten. Demo anfragen Demo Unverbindliches Angebot Kontakt Lösungen Use Cases IT/OT Integration Datenarchitektur CI/CD und DevOps MES Integration OEE Predictive Maintenance Traceability Alle Use Cases Industrien Automotive Metallverarbeitung Maschinen- und Werkzeugbau Lebensmittelindustrie Landmaschinenbau Plastikindustrie Getting started Unser Vorgehen Workshops Demo anfragen ROI-Calculator Mehr Nachhaltigkeit für Ihre Fertigung durch verfügbare Echtzeit-Daten – die aktuelle Studie von PAC Analyst Jetzt lesen Demo Unverbindliches Angebot 
=== https://www.cybus.io/lizenzen ===
code:200
 Pricing & Lizenzen der Cybus Connectware. Produkt Software Cybus Connectware Unified Namespace Connectivity Portfolio CybusMQ Cybus Connectware Lizenzen Anwendung Die Datenbasis für industrielle KI Referenzen Erfolgsgeschichten Erleben Sie die leistungsstärkste Datenintegration der Industrie: In unserer Live Demo entdecken Sie Connectware und Ihre Möglichkeiten. Demo anfragen Demo Unverbindliches Angebot Kontakt Lösungen Use Cases IT/OT Integration Datenarchitektur CI/CD und DevOps MES Integration OEE Predictive Maintenance Traceability Alle Use Cases Industrien Automotive Metallverarbeitung Maschinen- und Werkzeugbau Lebensmittelindustrie Landmaschinenbau Plastikindustrie Getting started Unser Vorgehen Workshops Demo anfragen ROI-Calculator Mehr Nachhaltigkeit für Ihre Fertigung durch verfügbare Echtzeit-Daten – die aktuelle Studie von PAC Analyst Jetzt lesen Demo Unverbindliches Angeb
=== https://www.cybus.io/en/licences ===
code:404
 Page not found | Cybus.io Product Software Cybus Connectware Unified Namespace Connectivity Portfolio CybusMQ Cybus Connectware Licenses Impact Data foundation for Industrial AI Customers Success stories Experience Connectware live and in action, solving your data integration challenges. Get in touch and request your free demo. Request demo Demo Offer request Contact Solutions Use cases IT/OT integration Data architecture MES integration CI/CD and DevOps OEE Predictive maintenance Traceability All use cases Industries Automotive Metal processing Machine- and tool building Food & beverages Agricultural machinery Plastic industry Getting started First steps Workshops Demo Your key to sustainable manufacturing is your real-time data: Learn more about current market insights in the independent research on data transparency and sustainability challenge. Download Demo Offer request Contact Re
Thinking…

Key findings so far:

  • Cybus Connectware is a self-hosted industrial IoT middleware. Deployment options: Docker Compose or Kubernetes/Helm. No hosted SaaS with a public API.
  • There's an "API Reference" in docs. Let me check it — is it a REST API against your own Connectware instance? Yes probably.
  • Licensing: license files needed. Let me check the licensing doc and the pricing page content.
  • Getting started quickstart "Connect Your First Machine" requires installing Connectware (Docker/K8s). That's a local service stack — exactly what the user said not to do.

Let me confirm by reading:

  1. The pricing page full content (Lizenzen page)
  2. docs licensing.md
  3. docs API reference
  4. docs "Connect Your First Machine" quickstart to confirm it requires a local stack
  5. Check if there's any hosted/cloud/sandbox/demo instance publicly accessible

Let me do these in parallel.

Let me read the licensing/pricing details, the API reference, and the quickstart to see what it actually requires.

cd /tmp; python3 -c "
import re,html
t=open('/tmp/p.html',errors='ignore').read()
" ; curl -sL -m 20 https://www.cybus.io/lizenzen -o lic.html -A "Mozilla/5.0"; python3 -c "
import re,html
t=open('/tmp/lic.html',errors='ignore').read()
t=re.sub(r'(?s)<script.*?</script>','',t); t=re.sub(r'(?s)<style.*?</style>','',t)
t=re.sub(r'<[^>]+>',' ',t); t=html.unescape(t); t=re.sub(r'\s+',' ',t)
i=t.find('Lizenzen')
# find pricing-ish section
for kw in ['Preis','Lizenz','Kosten','Edition','Free','Premium','Enterprise','Monat','Jahr','€','EUR','pro ','Preis auf Anfrage']:
    for m in re.finditer(kw,t):
        s=max(0,m.start()-200); print('>>',kw,'::',t[s:m.start()+250]); print()
        break
" 2>&1 | head -60
>> Lizenz :: Pricing & Lizenzen der Cybus Connectware. Produkt Software Cybus Connectware Unified Namespace Connectivity Portfolio CybusMQ Cybus Connectware Li
>> Lizenz ::  Pricing & Lizenzen der Cybus Connectware. Produkt Software Cybus Connectware Unified Namespace Connectivity Portfolio CybusMQ Cybus Connectware Lizenzen Anwendung Die Datenbasis für industrielle KI Referenzen Erfolgsgeschichten Erleben Sie die leistungsstärkst

>> Enterprise :: S, DB, Kafka, …) Container zur Erweiterung und Customization (Dashboards, ML, …) Infrastructure as Code Cloud und IT-Technologien am Edge: z.B. Kubernetes, Kafka, Ansible, Git, u.v.m. Ein Upgrade auf Enterprise ist jederzeit möglich. jetzt anfragen Enterprise Für steuernde Anwendungsfälle und produktionskritische Datenströme. features Alle Funktionen der Professional-Lizenz und zusätzlich: Hochverfügbarer Datentransfer für extrem hohe Datenlast N

>> Monat :: t? Mit der Research Lizenz nutzen Sie Connectware in vollem Funktionsumfang zu Sonderkonditionen. Welche Laufzeit haben die Verträge? Die Mindestlaufzeit einer regulären Connectware-Lizenz beträgt 12 Monate. Je nach Komplexität Ihrer Produktionsumgebung, des Leistungsumfangs und Ihrer digitalen Roadmap sind auch direkt längere Laufzeiten sinnvoll. Für weitere Details steht Ihnen unser Sales Team zur Verfügung. Verlängert sich die Connectware-Lize


cd /tmp; for u in https://docs.cybus.io/deployment/licensing.md https://docs.cybus.io/discover/connect-your-first-machine.md; do echo "############ $u"; curl -sL -m 25 "$u" | head -120; echo; done
############ https://docs.cybus.io/deployment/licensing.md
############ https://docs.cybus.io/deployment/licensing.md
> For the complete documentation index, see [llms.txt](https://docs.cybus.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.cybus.io/deployment/licensing.md).

# Licensing

Connectware operates based on your license specifications, which determine available features and validity period.

Connectware requires a valid license key to operate. Each license key is uniquely tied to your instance and enables specific features based on your subscription. This section covers everything you need to know about obtaining, managing, and implementing your Connectware license.

For more information about available Connectware licenses, visit the [Cybus website](https://www.cybus.io/en/product/licenses/).

## License View

The **License View** displays information of your active Connectware license. Each time you start Connectware, the license is automatically validated over the Internet. If your Connectware installation does not have Internet access, you can upload a valid license file manually.

* To open the **License View**, select **System** > **System Status**, and click the **License** tab.

<figure><img src="https://86125368-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FB72Vg1TxGzrXSVsfoCWq%2Fuploads%2Fgit-blob-f3bcf97a7c776a915364e087601bed6ea179790b%2Flicense-view-2.png?alt=media" alt=""><figcaption></figcaption></figure>

The following information are available:

* **License Name**
* **License Account**
* **Expiration Date**
* **License Class**
* **License ID**
* **License Status**

You can manually [refresh your license](#manually-refreshing-licenses-in-connectware) via the **Refresh License** button. You can [upload a new license file](#uploading-license-files-to-connectware) via the **Upload License File** button.

## Acquiring License Keys

The [Cybus Portal](https://portal.cybus.io/) allows you to generate and manage license keys for your Connectware installations. This page walks you through accessing the portal and generating new license keys. Once generated, you'll use this key during the Connectware installation process.

**Prerequisites**

* Access to the Cybus Portal. Contact our [Sales team](mailto:sales@cybus.io) to obtain portal credentials if needed.

**Procedure**

1. Go to the [Cybus Portal](https://portal.cybus.io/).
2. Enter your **Username** and **Password**, and click **Sign in**.
3. Click **Licenses** in the menu to view all your available Connectware licenses.

<figure><img src="https://www.cybus.io/wp-content/uploads/2024/05/Connectware-Licenses.png" alt="Available Connectware Licenses"><figcaption></figcaption></figure>

4. To obtain a new license key, click a license. We recommend to look for licenses marked as **No license key created yet**. You can use the **No license key** filter option to show only licenses without keys.

<figure><img src="https://www.cybus.io/wp-content/uploads/2024/05/SelectLicense.png" alt="Select Licenses Connectware"><figcaption></figcaption></figure>

<figure><img src="https://www.cybus.io/wp-content/uploads/2024/05/NoLicenseKey.png" alt="No License Key Connectware"><figcaption></figcaption></figure>

<figure><img src="https://www.cybus.io/wp-content/uploads/2024/05/AllLicenses.png" alt="Download License Key Button"><figcaption></figcaption></figure>

4. Click **Download License Key** in the upper right corner.

<figure><img src="https://www.cybus.io/wp-content/uploads/2024/05/Download-License.png" alt="Download License Key Button"><figcaption></figcaption></figure>

5. Add a description for your license and click **Generate License Key**.

{% hint style="warning" %}
Your new license key will appear on screen. Make sure to copy and save it somewhere secure, as you won't be able to view it again after closing this window. If you lose the key, you'll need to generate a new one, which will invalidate the previous key - even if it's already in use.
{% endhint %}

<figure><img src="https://www.cybus.io/wp-content/uploads/2024/05/GenerateLicenseKey1.png" alt="Description of License Connectware"><figcaption></figcaption></figure>

<figure><img src="https://www.cybus.io/wp-content/uploads/2024/05/GenerateLicenseKey2.png" alt="Generate License Key Connectware"><figcaption></figcaption></figure>

<figure><img src="https://www.cybus.io/wp-content/uploads/2024/05/GenerateLicenseKey3.png" alt="Output of License Key Connectware"><figcaption></figcaption></figure>

**Result:** Once you have your license key safely stored, you can proceed with Connectware installation.

## Online License Validation

Connectware automatically validates your license during startup if it can reach the [Cybus Portal](https://portal.cybus.io/)) backend (`graphql-server.cybus.io`). When this connection is available, license updates occur automatically in the background. If the server cannot be reached, you must [manually update](#manually-refreshing-licenses-in-connectware) your Connectware license by uploading a new license file.

## Offline License Activation

If Connectware is not connected to the Internet, you must activate your license manually through an offline process. This requires:

1. Downloading a license file from the [Cybus Portal](https://portal.cybus.io/) via one of the following options:
   * [Downloading License Files via Installer Script](#downloading-license-files-via-installer-script)
   * [Downloading License File via Cybus Portal Website](#downloading-license-files-via-the-cybus-portal)
2. Uploading the license file into your offline Connectware installation.

### Downloading License Files

You can download license files via the installer script or via the [Cybus Portal](https://portal.cybus.io/).

#### Downloading License Files via Installer Script

If you installed Connectware using the `connectware-online-installer.sh` script, you can use the same script to download your license file by adding the `--download-license-file` command.

To download the license file, you'll need either:

1. Your original license key, which can be passed directly as a command-line option.
2. The path to your existing Connectware installation directory.

Once executed, the script will download your license file and display its filename. You can then use this file to activate your offline Connectware installation.

**Procedure**

* To download the license via the script with the license key (e.g. `ABCABCABC`,), do the following:

{% code lineNumbers="true" %}

```
./connectware-online-installer.sh --download-license-file -k ABCABCABC
```

{% endcode %}

* To download the license via the script using the Connectware installation directory (e.g. `/opt/connectware`), do the following:

{% code lineNumbers="true" %}

```
./connectware-online-installer.sh --download-license-file -d /opt/connectware
```

{% endcode %}

############ https://docs.cybus.io/discover/connect-your-first-machine.md
> For the complete documentation index, see [llms.txt](https://docs.cybus.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.cybus.io/discover/connect-your-first-machine.md).

# Connect Your First Machine

Install a sample service that connects to a simulated OPC UA machine and watch live data arrive in Connectware.

See Connectware in action: you install a service from a sample service commissioning file, Connectware connects to a public OPC UA demo server that simulates a machine, and the incoming data appears in the Data Explorer. By the end, you have run the full Connectware workflow, from YAML configuration to live data on an MQTT topic.

You do not need any machine or hardware. The sample service connects to a publicly available OPC UA test server that publishes simulated data.

## Prerequisites

* A running Connectware installation. See [Installing Connectware](/deployment/installing-connectware.md).
* A user account that is allowed to install services. The [default admin user](/access/user-management/users/default-admin-user.md) is sufficient.
* Outbound Internet access from Connectware to the demo server `opcua.demo-this.com` on port `51210`.

## Install and Verify the Sample Service

{% stepper %}
{% step %}

### Download the Sample Service Commissioning File

{% file src="/files/XUbMC5CGw2LpCf81UY3t" %}

The file defines the resources that make up the data pipeline:

* A `Cybus::Connection` to the demo OPC UA server.
* A `Cybus::Endpoint` that subscribes to a node publishing simulated values.
* A `Cybus::Mapping` that publishes those values to the MQTT topic `example/opcua/dataexample`.

For a walkthrough of each section in a service commissioning file, see [How Connectware Works](/discover/how-connectware-works.md).
{% endstep %}

{% step %}

### Log in to the Admin UI

1. Open your browser and enter the address of your Connectware instance (**https\://\<HOST-IP>**).
2. Enter your username and password and click **Sign in**.
   {% endstep %}

{% step %}

### Install the Service

1. In the navigation panel, click **Services**.
2. Click **Upload Service**.
3. Click **Choose File** and select the `connect-your-first-machine.yaml` file.
4. Click **Install** to confirm the parameters and start the installation. You can keep the default parameter values.

The service is now installed but not yet enabled.
{% endstep %}

{% step %}

### Enable the Service

1. In the **Service Overview** list, click your service to open the **Service Details** view.
2. Click **Enable**.
3. In the **Authorization Required** dialog, click **Allow** to confirm the configuration changes.

Connectware now creates the connection, endpoint, and mapping, and data starts to flow.
{% endstep %}

{% step %}

### Watch the Data Arrive

Data flows through Connectware as MQTT messages organized into topics. The [Data Explorer](/monitoring/data-explorer.md) lets you monitor them live.

1. In the navigation panel, click **Data**.
2. In the **Available Topics** tree, select the `example/opcua/dataexample` topic.

The Data Explorer shows the simulated values arriving from the demo server every few seconds.
{% endstep %}
{% endstepper %}

## Result

You installed, enabled, and verified a complete Connectware service. One service commissioning file created all three resources, the connection, the endpoint, and the mapping, and the machine data is now available to any MQTT consumer through the Unified Namespace.

To remove the sample service, open its **Service Details** view, click **Disable**, and then delete the service. Connectware closes the connection and removes the endpoint and the mapping with it.

## Next Steps

* Connect a real device with the other [Machine Connectivity](/guides/machine-connectivity.md) guides or browse the [connectors](/connectors/shop-floor-connectors.md) for your protocols.
* Build your own service using the [service commissioning file reference](/data-flows/service-commissioning-files.md).
* Route and transform your data with the [Rule Engine](/data-flows/rule-engine.md).


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.cybus.io/discover/connect-your-first-machine.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.
Thinking…

This confirms the picture clearly:

  1. Quickstart requires a running Connectware installation — self-hosted via Docker Compose or Kubernetes/Helm. That's a local service stack (multi-container: PostgreSQL, CybusMQ, admin UI, etc.). Plus it requires a valid license key obtained from Cybus Portal, which requires contacting sales@cybus.io for portal credentials. So it's gated behind a sales process.

  2. There's an "API Reference" in the docs — but that's the REST API of your own Connectware instance, not a hosted API. Let me quickly verify that and check the pricing page in English for details on the license classes. Also check whether there's any hosted/cloud sandbox or trial instance.

Let me check:

Let me do these in parallel.

The quickstart requires a running self-hosted installation. Let me verify the API surface and get the English pricing page, and check for any hosted/trial option.

cd /tmp; curl -sL -m 25 https://www.cybus.io/en/product/licenses/ -o l2.html -w "code:%{http_code}\n" -A "Mozilla/5.0"; python3 -c "
import re,html
t=open('/tmp/l2.html',errors='ignore').read()
t=re.sub(r'(?s)<script.*?</script>','',t); t=re.sub(r'(?s)<style.*?</style>','',t)
t=re.sub(r'<[^>]+>',' ',t); t=html.unescape(t); t=re.sub(r'\s+',' ',t)
i=t.lower().find('license class')
print(t[max(0,i-200): i+4000] if i>0 else t[1200:5200])
"
code:200
code:200
sten now Demo Offer request Contact Company Ecosystem Become a partner Cybus x Capgemini Cybus x Microsoft Azure Cybus x STACKIT Cybus x ZEDEDA About Cybus Company News room Events Career Demo Offer request Contact En De En Contact Cybus Connectware Licenses The right plan for your production and each of your projects Research For universities and research projects. features Full range of functions for comprehensive research projects Performance level suitable for research environments Ideal for study, research projects, and lab environments Access to tutorials and self-service materials get started Professional For productive use cases and for getting started with smart factory connectivity. features All core Connectware features, including: Industrial Connectivity Data transformation Multi-endpoint data routing Data integration with IT systems (Cloud, MES, DB, Kafka, …) Containers for extension and customization (Dashboards, ML, …) Infrastructure as Code Cloud and IT technologies at the edge: e.g. Kubernetes, Kafka, Ansible, Git, and many more.Upgrade to Enterprise is possible at any time. Upgrade to Enterprise is possible at any time. request now Enterprise For controlling use cases and production critical data streams. features All the features of the Professional license plus: Highly available data transfer for extremely high data load Network segmentation IT compliance, e.g. through LDAP and multi-factor authentication (MFA) Production-critical data load: automatic failover and load balancing Unlimited horizontal scaling Global IT-OT management Enterprise support with LTS program request now Would you like to talk to an expert? Find out which plan is best for you? We understand the complexity of your requirements and are happy to help. Schedule a discovery call REALIZE YOUR INDUSTRY 4.0 PROjECTS WITH instant RESULTS Request your free offer request your offer FAQ | Frequently asked questions About Cybus Connectware What is Cybus Connectware? Cybus Connectware is a Factory Data Hub that enables seamless integration between production facilities and IT systems. As a smart factory software, the software solution creates a stable and powerful data infrastructure that provides, processes and merges data across the company in a secure and standardized manner. It has been specially developed for production-critical use and deployment across multiple locations. Who uses Cybus Connectware? Cybus Connectware is particularly suited to large companies with complex production requirements, multiple production sites and high data loads. In most cases, it is used by IT teams, digitalization teams, production teams and functional departments (e.g. quality assurance). What does Cybus Connectware offer? > Highly available data flow: As a Factory Data Hub, Connectware establishes an omnidirectional data flow between manufacturing and IT systems. In addition to end-to-end shop floor connectivity, its real-time integration enables more complex data processing and resilient data load balancing. > Infrastructure as code: Connectware’s strength lies in its configuration through infrastructure as code. This manages an organization’s data infrastructure through code files, rather than manual configurations. This ensures data consistency, version control, automation, and seamless rollout. > Seamless rollouts: By using a central repository, configurations can be rolled out, optimized, and updated quickly and automatically across multiple sites. Deployments become faster and more efficient than ever before. > IT/OT collaboration: Collaboratively created integration templates can be selected from a catalog and populated by the OT via user-friendly software interface. > DevOps methodologies: IT teams can review and consolidate all no-code configurations to ensure enterprise-wide data consistency. In addition, Connectware provides granular user management (including LDAP and multi-factor authentication), a strong rule engine, horizontal scaling, data lo

cd /tmp; grep -n -i -E "api-reference|/api|rest api|openapi|sdk" llms.txt | head -20; echo "=== try API ref page ==="; curl -sL -m 25 "https://docs.cybus.io/reference/api-reference.md" -o api.md -w "code:%{http_code}\n"; head -40 api.md
64:- [Self-Registering Clients via REST API](https://docs.cybus.io/access/client-registry/self-registering-clients-via-rest-api.md): Flexible and secure client 
64:- [Self-Registering Clients via REST API](https://docs.cybus.io/access/client-registry/self-registering-clients-via-rest-api.md): Flexible and secure client self-registration with role, permission, and certificate configuration.
222:- [HTTP/REST](https://docs.cybus.io/connectors/enterprise-connectors/http-rest.md): Connect to REST APIs with support for polling, on-demand requests, and data publishing. Includes OAuth 2.0, Basic Auth, and header-based authentication.
322:- [SAP S/4HANA Integration](https://docs.cybus.io/guides/system-connectivity/mes-erp-business-systems/sap-s4hana-integration.md): How to integrate SAP S/4HANA with Connectware via OData REST APIs, including communication arrangements, authentication, polling production orders, and posting confirmations.
358:- [Power BI Integration](https://docs.cybus.io/guides/system-connectivity/analytics-monitoring-alerting/power-bi-integration.md): How to integrate Microsoft Power BI with Connectware, including creating a streaming semantic model, pushing live shop floor data to the REST API, and building a real-time dashboard.
379:- [Migrating from HiveMQ Edge](https://docs.cybus.io/guides/migration/migrating-from-hivemq-edge.md): How to read the HiveMQ Edge configuration from config.xml or the REST API and translate protocol adapters, tags, and mappings into a Connectware service commissioning file using an AI assistant.
391:- [API Reference](https://docs.cybus.io/reference/api-reference.md): Here you can find a list all endpoints available to use across the Connectware API.
392:- [Auth-Server API](https://docs.cybus.io/reference/api-reference/auth-server-api.md)
393:- [Services API](https://docs.cybus.io/reference/api-reference/services-api.md)
394:- [Resources API](https://docs.cybus.io/reference/api-reference/resources-api.md)
395:- [System Status API](https://docs.cybus.io/reference/api-reference/system-status-api.md)
396:- [Resource Status Tracking API](https://docs.cybus.io/reference/api-reference/resource-status-tracking-api.md)
397:- [Topic Explorer API](https://docs.cybus.io/reference/api-reference/topic-explorer-api.md)
460:- [Self-Registering Clients via REST API](https://docs.cybus.io/2-6-1/access/client-registry/self-registering-clients-via-rest-api.md): Flexible and secure client self-registration with role, permission, and certificate configuration.
618:- [HTTP/REST](https://docs.cybus.io/2-6-1/connectors/enterprise-connectors/http-rest.md): Connect to REST APIs with support for polling, on-demand requests, and data publishing. Includes OAuth 2.0, Basic Auth, and header-based authentication.
718:- [SAP S/4HANA Integration](https://docs.cybus.io/2-6-1/guides/system-connectivity/mes-erp-business-systems/sap-s4hana-integration.md): How to integrate SAP S/4HANA with Connectware via OData REST APIs, including communication arrangements, authentication, polling production orders, and posting confirmations.
754:- [Power BI Integration](https://docs.cybus.io/2-6-1/guides/system-connectivity/analytics-monitoring-alerting/power-bi-integration.md): How to integrate Microsoft Power BI with Connectware, including creating a streaming semantic model, pushing live shop floor data to the REST API, and building a real-time dashboard.
775:- [Migrating from HiveMQ Edge](https://docs.cybus.io/2-6-1/guides/migration/migrating-from-hivemq-edge.md): How to read the HiveMQ Edge configuration from config.xml or the REST API and translate protocol adapters, tags, and mappings into a Connectware service commissioning file using an AI assistant.
787:- [API Reference](https://docs.cybus.io/2-6-1/reference/api-reference.md): Here you can find a list all endpoints available to use across the Connectware API.
788:- [Auth-Server API](https://docs.cybus.io/2-6-1/reference/api-reference/auth-server-api.md)
789:- [Services API](https://docs.cybus.io/2-6-1/reference/api-reference/services-api.md)
=== try API ref page ===
code:200
> For the complete documentation index, see [llms.txt](https://docs.cybus.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.cybus.io/reference/api-reference.md).

# API Reference

Here you can find a list all endpoints available to use across the Connectware API.

The Connectware API provides a comprehensive set of interfaces for managing and interacting with your Industrial IoT environment. This reference documentation covers the essential API endpoints that allow you to control all aspects of Connectware.

Use these APIs to manage access, deploy and configure services, monitor resources, track system status, and integrate industrial protocols.

## Connectware API Overview

### Auth-Server API

Use the Auth-Server API to manage authentication and user related configuration, including local users and external identity provider integration.

**Typical use cases**

* Manage local users and roles to control access.
* Configure the LDAP and Microsoft Entra ID integration for centralized authentication.
* Handle login, logout, and token based authentication.
* Enforce role based access control and multi-factor authentication.

For the full API definition, see [Auth-Server API](/reference/api-reference/auth-server-api.md).

### Services API

Use the Services API to create, update, and manage Connectware services and their lifecycle.

**Typical use cases**

* Create and update service definitions for data flows and logic.
* Retrieve service information and status.
* Validate service configurations before deployment.
* Manage service dependencies and associated resources.

For the full API definition, see [Services API](/reference/api-reference/services-api.md).

### Resources API
Thinking…

Everything is confirmed. Let me do one final check on whether there's any hosted/public instance or trial/self-service signup, and confirm the install requirements (docker compose / helm = local service stack). Let me quickly check the installation page and see if there's a SaaS/cloud-hosted Connectware option.

Let me use the docs "ask" feature to ask about hosted/cloud/trial availability.

One last check: is there any hosted instance or self-service trial I could use instead of a local stack?

cd /tmp; curl -sG -m 40 "https://docs.cybus.io/discover/what-is-connectware.md" --data-urlencode "ask=Is there a hosted, cloud, or publicly available Cybus Connectware instance or free self-service trial/sandbox that a developer can sign up for and call via API without installing Connectware themselves?" --data-urlencode "goal=Determine whether a developer can try Connectware through a hosted API/SDK without deploying the software locally" | head -60
# Is there a hosted, cloud, or publicly available Cybus Connectware instance or free self-service trial/sandbox that a developer can sign up for and call via AP
# Is there a hosted, cloud, or publicly available Cybus Connectware instance or free self-service trial/sandbox that a developer can sign up for and call via API without installing Connectware themselves?

**The docs do not describe a public hosted Connectware instance or a free, self-service API sandbox.** They describe Connectware as software you deploy, then access through that instance’s APIs.

You don’t have to install it on your own computer: Connectware supports deployments on cloud Kubernetes platforms such as EKS and AKS. But that means deploying and licensing your own instance, not signing up to use a shared Cybus-hosted sandbox. A valid license is required; the licensing process says to contact Sales for Cybus Portal credentials if needed. See [System Requirements](/deployment/installing-connectware/system-requirements.md) and [Licensing](/deployment/licensing.md).

The [API Reference](/reference/api-reference.md) documents APIs for interacting with a Connectware environment; it does not provide a public API endpoint or self-service credentials. If you want to try it without managing deployment, the docs provide no self-service route; contact [Cybus Sales](mailto:sales@cybus.io) about trial or hosted-demo availability.

# Suggested Follow-up Questions:

If you need more information, consider asking one of these follow-up questions by performing an HTTP GET request on the URL:

- [Is there a hosted demo from Cybus?](https://docs.cybus.io?ask=Is%20there%20a%20hosted%20demo%20from%20Cybus%3F&goal=Determine%20whether%20a%20developer%20can%20try%20Connectware%20through%20a%20hosted%20API%2FSDK%20without%20deploying%20the%20software%20locally)
- [What licenses enable cloud/demo access?](https://docs.cybus.io?ask=What%20licenses%20enable%20cloud%2Fdemo%20access%3F&goal=Determine%20whether%20a%20developer%20can%20try%20Connectware%20through%20a%20hosted%20API%2FSDK%20without%20deploying%20the%20software%20locally)
- [How to get portal credentials for a trial?](https://docs.cybus.io?ask=How%20to%20get%20portal%20credentials%20for%20a%20trial%3F&goal=Determine%20whether%20a%20developer%20can%20try%20Connectware%20through%20a%20hosted%20API%2FSDK%20without%20deploying%20the%20software%20locally)

# Sources:

- [Deploying Connectware Behind a Corporate Proxy](https://docs.cybus.io/guides/operations/deploying-connectware-behind-a-corporate-proxy.md)
- [Automated Connectware Deployment Using GitLab CI/CD & Ansible](https://docs.cybus.io/guides/ansible/automated-connectware-deployment-via-gitlab-cicd-and-ansible.md)
- [Cybus Connectware Documentation](https://docs.cybus.io/readme.md)
- [System Requirements](https://docs.cybus.io/deployment/installing-connectware/system-requirements.md)
- [What Is Connectware?](https://docs.cybus.io/discover/what-is-connectware.md)
- [Installing Connectware](https://docs.cybus.io/deployment/installing-connectware.md)
- [Rule Sandbox](https://docs.cybus.io/data-flows/rule-engine/rule-sandbox.md)
- [Confluent Cloud Integration](https://docs.cybus.io/guides/system-connectivity/messaging-event-streaming/confluent-cloud-integration.md)
- [Oracle Fusion Cloud SCM Integration](https://docs.cybus.io/guides/system-connectivity/mes-erp-business-systems/oracle-fusion-cloud-scm-integration.md)
- [Cloud & IoT Platforms](https://docs.cybus.io/guides/system-connectivity/cloud-iot-platforms.md)
- [License Information](https://docs.cybus.io/monitoring/system-status/license-information.md)
- [Licensing](https://docs.cybus.io/deployment/licensing.md)
- [Offline Installation (Kubernetes)](https://docs.cybus.io/deployment/installing-connectware/offline-on-kubernetes.md)
- [Offline Installation (Docker)](https://docs.cybus.io/deployment/installing-connectware/offline-on-docker.md)
- [Security](https://docs.cybus.io/access/security.md)
- [Cybus Connectware Extension (VS Code)](https://docs.cybus.io/tools/cybus-connectware-extension-vs-code.md)
- [Installing Connectware (Kubernetes)](https://docs.cybus.io/deployment/installing-connectware/on-kubernetes.md)
- [API Reference](https://docs.cybus.io/reference/api-reference.md)
- [System Information](https://docs.cybus.io/monitoring/system-status/system-information.md)
- [Admin UI Permissions](https://docs.cybus.io/access/user-management/access-permissions-for-admin-ui/ui-access.md)
- [Self-Registering Clients via REST API](https://docs.cybus.io/access/client-registry/self-registering-clients-via-rest-api.md)
- [Usage Metrics](https://docs.cybus.io/monitoring/system-status/usage-metrics.md)
- [Ansible](https://docs.cybus.io/guides/ansible.md)


cd /tmp; curl -sL -m 25 https://docs.cybus.io/deployment/installing-connectware.md | head -60; echo "=== requirements ==="; curl -sL -m 25 https://docs.cybus.io/deployment/installing-connectware/system-requirements.md | head -45
> For the complete documentation index, see [llms.txt](https://docs.cybus.io/llms.txt). Markdown versions of documentation pages are available by appending `.md
> For the complete documentation index, see [llms.txt](https://docs.cybus.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.cybus.io/deployment/installing-connectware.md).

# Installing Connectware

Install Connectware on Docker or Kubernetes, including offline environments.

Connectware runs on Docker and Kubernetes. Before installing, verify your system meets the requirements. See [System Requirements](/deployment/installing-connectware/system-requirements.md).

For environments without Internet access, offline installation procedures are available for both platforms.

## On Kubernetes

{% content-ref url="/pages/qJ2bO0pwCAtgOUfEV2Vm" %}
[Installing Connectware (Kubernetes)](/deployment/installing-connectware/on-kubernetes.md)
{% endcontent-ref %}

{% content-ref url="/pages/VmAj5d5H4NEPHHzQrMVB" %}
[Offline Installation (Kubernetes)](/deployment/installing-connectware/offline-on-kubernetes.md)
{% endcontent-ref %}

## On Docker

{% content-ref url="/pages/qMwfrD8Dxoang3SMKGFM" %}
[Installing Connectware (Docker)](/deployment/installing-connectware/on-docker.md)
{% endcontent-ref %}

{% content-ref url="/pages/5eNOZCQmGvEfShh8FDGw" %}
[Offline Installation (Docker)](/deployment/installing-connectware/offline-on-docker.md)
{% endcontent-ref %}

## Uninstalling Connectware

{% content-ref url="/pages/YPsqDTjAEoDi2akfNs4v" %}
[Uninstalling Connectware](/deployment/installing-connectware/uninstalling-connectware.md)
{% endcontent-ref %}


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.cybus.io/deployment/installing-connectware.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.
=== requirements ===
> For the complete documentation index, see [llms.txt](https://docs.cybus.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.cybus.io/deployment/installing-connectware/system-requirements.md).

# System Requirements

Hardware, software, and virtual host requirements for installing and operating Connectware.

This section outlines the technical requirements for installing and operating Connectware. It covers hardware specifications, network configuration, and system dependencies for both Docker Compose and Kubernetes deployments.

The hardware requirements for Connectware depend on factors such as message rate, message size, and storage requirements. For hardware recommendations based on your specific use cases, [contact us](https://www.cybus.io/en/contact/) and we’ll recommend the appropriate hardware setup.

## Connectware Deployment Options

Connectware offers multiple deployment options using Kubernetes, Docker, or a hybrid approach. The choice depends on your specific infrastructure requirements, from enterprise-scale operations to streamlined development environments.

The following table details the features and recommended use cases for Kubernetes and Docker deployments.

|                  | **Kubernetes**                                                                                                                                                                             | **Docker**                                                                                                 |
| ---------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ | ---------------------------------------------------------------------------------------------------------- |
| **Platform**     | Kubernetes using Helm orchestration                                                                                                                                                        | Docker with Docker Compose                                                                                 |
| **Environments** | Cloud, On-Premises, Hybrid                                                                                                                                                                 | On-Premises Linux (VM, Bare Metal)                                                                         |
| **Use case**     | Enterprise-grade deployment solution                                                                                                                                                       | Development and simple production                                                                          |
| **Key features** | <p>• Advanced orchestration<br>• Automated deployment management<br>• For high-demand environments<br>• Comprehensive monitoring<br>• Automated scaling<br>• Robust service management</p> | <p>• Low infrastructure requirements<br>• For development environments<br>• For basic deployment needs</p> |

## Software Requirements

* Linux operating system
* Latest stable version of Chrome browser

Connectware runs on Linux, using one of the deployment options described in [Connectware Deployment Options](#connectware-deployment-options). [Contact us](https://www.cybus.io/en/contact/) about Windows hosts or other deployment options.

## Docker Compose Deployment

Docker Compose provides a streamlined deployment option for Connectware, ideal for smaller installations or development environments. This approach simplifies setup and management while maintaining essential functionality, requiring fewer resources than a full Kubernetes implementation.

### Hardware Requirements

The hardware requirements for deploying Connectware on Docker depend on your deployment scale and your specific use cases.

#### Minimum Setup

* CPU: **64-bit x86**
* RAM: **4 GB**
* Storage: **32 GB**

### Docker Host Requirements
Thinking…

I have everything I need. Per the user's instruction: "If this product has no developer workflow you can act on, say so plainly and stop." and "Do not start local service stacks or wait for long-running commands; if the quickstart requires either, say so plainly and stop."

Cybus Connectware:

  • Is self-hosted software (Docker Compose on Linux or Kubernetes/Helm). It's a multi-container stack (PostgreSQL, CybusMQ MQTT broker, admin UI, etc.).
  • Requires a valid license key from the Cybus Portal, which requires contacting sales@cybus.io for credentials. No self-service signup, no free tier with instant access (Research license exists but still requires portal credentials via sales).
  • No hosted/SaaS instance, no public API endpoint, no SDK on npm/PyPI.
  • The REST APIs (Auth-Server, Services, Resources, System Status, Topic Explorer) all operate against your own installed instance.

So: the quickstart requires a local service stack (Docker Compose or K8s) AND a license gated behind a sales conversation. I cannot act on it. I should say so plainly and stop.

I should also answer the pricing question (from the licenses page) and the "will this be easy for you to manage" question briefly.

I did NOT start any stacks or write code. Let me report. I should not create files. Let me just verify I left the repo clean.

Pricing details found:

  • Three license classes: Research (universities/research, full functionality at special conditions, self-service materials), Professional (productive use cases, all core features), Enterprise (adds HA, network segmentation, LDAP/MFA, failover/load balancing, unlimited horizontal scaling, global IT-OT management, enterprise support with LTS).
  • No public prices — "request now" / "Jetzt anfragen" → quote-based via sales.
  • Minimum contract term: 12 months.
  • License is per-instance, tied to instance, determines features + validity period. Validated over internet at startup against graphql-server.cybus.io; offline requires license file upload.
  • License keys generated in Cybus Portal; portal credentials require contacting sales.

Let me quickly double-check whether there's any public price figure anywhere (e.g., a price list PDF). Let me do one quick grep for currency on the page. Actually, I already looked. Let me do a quick targeted check to be fair about pricing, then report.

cd /tmp; python3 -c "
import re,html
t=open('/tmp/l2.html',errors='ignore').read()
t=re.sub(r'(?s)<script.*?</script>','',t); t=re.sub(r'(?s)<style.*?</style>','',t)
t=re.sub(r'<[^>]+>',' ',t); t=html.unescape(t); t=re.sub(r'\s+',' ',t)
hits=re.findall(r'(?:EUR|€|\\\$)\s?\d[\d.,]*|\d[\d.,]*\s?(?:EUR|€|/month|/year|per month)',t)
print('price figures found:', hits[:20] or 'NONE')
for kw in ['12 months','term','renew','automatically']:
    i=t.lower().find(kw.lower())
    if i>0: print('>>',kw,'::',t[max(0,i-250):i+300]); print()
" ; echo "=== repo clean? ==="; git status --porcelain
Failedprice figures found: NONE
price figures found: NONE
>> 12 months :: rise license. Research: You realize a research or university project? With the Research license you use Connectware in full functionality under special conditions. What is the term of the license? The minimum term of a regular Connectware license is 12 months. Depending on the complexity of your production environment, the scope of services and the digital roadmap, longer terms are suitable even at the beginning. For exact details, please contact our Sales Team . Does the Cybus Connectware license renew automatically? Your Connectware license i

>> term :: er network also provides you with seamless access to our software and professional support from trained partner companies for large integration and digitization projects. Find out more on our Website or contact our Partner Management . Licensing and term Which license is suitable for my production? The license that best suits your manufacturing is highly dependent on the complexity of your production environment, production criticality, and the scope of your digitization projects. For a meaningful assessment, please contact the Sales Team . In 

>> renew :: months. Depending on the complexity of your production environment, the scope of services and the digital roadmap, longer terms are suitable even at the beginning. For exact details, please contact our Sales Team . Does the Cybus Connectware license renew automatically? Your Connectware license is automatically renewed after the contractual minimum term has expired. Please contact our Sales Team for further details and extraordinary inquiries. Support and service Which support does Cybus offer? To ensure the smooth operation of Connectware, we 

>> automatically :: code files, rather than manual configurations. This ensures data consistency, version control, automation, and seamless rollout. > Seamless rollouts: By using a central repository, configurations can be rolled out, optimized, and updated quickly and automatically across multiple sites. Deployments become faster and more efficient than ever before. > IT/OT collaboration: Collaboratively created integration templates can be selected from a catalog and populated by the OT via user-friendly software interface. > DevOps methodologies: IT teams can r

=== repo clean? ===
fatal: not a git repository (or any of the parent directories): .git


Command exited with code 128
Thinking…

(The git status failed because I cd'd to /tmp. Let me check the repo is clean.)

Actually, I didn't write anything to the repo, so it's clean. Let me verify quickly.

Then report and stop.

cd /sandbox/repo && git status --porcelain && echo "(repo unchanged)" && ls -A
(repo unchanged)
(repo unchanged)
.git
.gitignore
Thinking…

I did not build anything. I should report plainly and stop, per the user's instructions.

Let me write a concise report.

Stopping here — Cybus has no developer workflow I can act on

I did not build anything. I researched it and hit a hard blocker. Repo is unchanged (no files written, no services started).

What Cybus is

Cybus Connectware is an industrial IoT / OT‑IT integration middleware ("Factory Data Hub") — a Unified Namespace that connects shop-floor machines (OPC UA, MQTT, etc.) to IT systems. Current version 2.6.2.

The blocker

It is self-hosted software, not a hosted product, and the quickstart requires exactly the two things you told me to avoid:

  1. A local service stack. Docs list only two deployment options: Docker Compose on Linux (4 GB RAM / 32 GB min) or Kubernetes via Helm charts. No SaaS tier. The "Connect Your First Machine" quickstart's first prerequisite is literally "A running Connectware installation."
  2. A license gated behind sales. Connectware "requires a valid license key to operate." Keys come from the Cybus Portal, and getting portal credentials means emailing sales@cybus.io. No self-service signup, no trial I can provision.

I confirmed the absence of a hosted path independently:

  • npm: no official SDK. The @cybus/* packages are an unrelated org (React helpers, version bumpers).
  • PyPI: nothing. Docker Hub: no official images.
  • The REST APIs (Auth-Server, Services, Resources, System Status, Topic Explorer) all target your own installed instance — there's no public endpoint.
  • Their own docs (via the GitBook agent API) confirm: "The docs do not describe a public hosted Connectware instance or a free, self-service API sandbox." Cloud deployment means deploying your own licensed instance on EKS/AKS, not using a Cybus-hosted one.

How pricing works

Quote-based, no published numbers anywhere (I scanned the licensing page for currency figures — none).

  • Three classes: Research (universities/research, full functionality at "special conditions," self-service materials), Professional (all core features: connectivity, transformation, multi-endpoint routing, IT integration, IaC), Enterprise (adds HA/failover, load balancing, unlimited horizontal scaling, network segmentation, LDAP + MFA, global IT‑OT management, LTS support).
  • Terms: minimum 12 months; auto-renews after the minimum term expires. Longer terms pushed for complex environments.
  • Enforcement: license is bound per-instance, controls features + validity, validated over the internet at startup against graphql-server.cybus.io. Air-gapped installs need a manually uploaded license file.

Would this be easy for me to manage?

No. Everything that makes it manageable — provisioning, license lifecycle, upgrades, HA — sits behind a paid instance and a sales relationship. The genuinely agent-friendly parts (config-as-code via YAML "service commissioning files," a VS Code extension, Ansible/GitLab CI‑CD automation, Ansible migration tools) are all real strengths, but they only pay off against an instance you already own and license. With no instance, there's nothing for me to drive.

Unblock options

  • Ask sales@cybus.io for Cybus Portal credentials + a trial license, and give me a reachable instance URL — then I can build against the Services/Resources APIs.
  • Or tell me to proceed with a license-free, stack-free substitute that has the same shape (e.g. a public MQTT broker + Node-RED, or Eclipse Ditto/Kepware-alike), and I'll build the example on that instead.

AX Fundamentals

23 checks. Open an area for details.

This check is a quick preview. Test more tasks and models with Gauge Agents.

Test your product with Gauge Agents

AX Check by Gauge