WoowTech · EMQX 5.8.9

Choose how to run EMQX: self-hosted or managed by WoowTech

This overseas edition presents two paths: Option A (self-hosted) and Option B (managed by WoowTech). It does not assume a country, currency or service region. Pricing, the contact channel, the call-to-action destination and the managed-service scope remain visible placeholders until the owner supplies them.

Choose a deployment option

Option A (self-hosted)

You install and operate EMQX 5.8.9 in your own Home Assistant environment.
Your team owns configuration, monitoring, backups, certificate rotation and upgrades.
Use the 22-chapter tutorial and official EMQX documentation to plan and verify the deployment.
Commercial detail: [currency and price pending].

Option B (managed by WoowTech)

WoowTech manages the deployment under a scope that the owner still needs to define.
Managed-service scope and service levels: [managed-service scope and service levels pending].
Availability by location: [supported regions pending].
Contact: [contact channel pending]. CTA: [CTA URL pending].

Compare the operating models

Both options use EMQX 5.8.9. The decision is about who performs the work, who approves changes and what support scope is agreed—not about an unverified performance promise.

Aspect	Option A (self-hosted)	Option B (managed by WoowTech)
Environment	Your Home Assistant environment	Your agreed environment; exact eligibility is pending
Configuration	Your team configures Listeners, authentication, ACL and rules	Responsibility is defined in the pending managed-service scope
Operations	Your team monitors, backs up and upgrades the deployment	Operational responsibilities are pending owner confirmation
Change control	Your team approves and records changes	The approval and handover process is pending owner confirmation
Commercial path	[currency and price pending]	[currency and price pending]

Open questions: What currency and price apply to each option? Which regions are supported? What exactly is included in the managed scope? What contact channel and CTA URL should this page publish? Until the owner answers, use [contact channel pending] and [CTA URL pending].

Information needed for either option

WoowTech needs the same technical baseline before either path can be scoped. Record measured values rather than estimates where possible; no client count, throughput or capacity is promised on this page.

Input	What to provide
Clients and subscriptions	Current and expected counts, plus session and keepalive requirements.
Message traffic	Measured message rate, payload size, QoS and connection rate.
Retained messages	Topic count, retention expectations and any migration requirement.
Rules and Connectors	Required Rule Engine flows, Connectors, Sinks, Sources and external systems.
Host resources	Available memory, disk, network and the planned backup location.

From enquiry to acceptance

Choose a path: select Option A (self-hosted) or ask about Option B (managed by WoowTech).
Supply the baseline: provide the existing broker, traffic, integrations, security requirements and maintenance owner.
Confirm the scope: record responsibilities, exclusions, acceptance tests and rollback requirements before work begins.
Run a pilot: verify the Dashboard, authentication, ACL, rules, backup and representative MQTT traffic.
Accept and hand over: record the approved result, remaining exceptions and the owner of each recurring task.

Scope and delivery risks

Risk	Impact	Control
Unconfirmed operating owner	Backups, monitoring or upgrades may have no accountable owner	Name the owner of every recurring task in the agreed scope.
Version confusion	Upgrade decisions may use the wrong version	Record EMQX 5.8.9 and add-on 5.9.0 separately.
Missing acceptance baseline	Capacity or functionality cannot be verified	Agree on representative tests and measured pass criteria before implementation.
Undefined external exposure	A Listener or Dashboard may be exposed beyond the intended boundary	Document every network boundary, TLS requirement and approved access route.
Unconfirmed managed scope	Option B expectations may differ	Keep [managed-service scope and service levels pending] visible until the owner approves the wording.

Boundaries to agree before work starts

State who may access the Home Assistant host, EMQX Dashboard and MQTT Listeners.
Keep passwords, API keys, tokens, private keys and connection strings out of the brief, HTML, logs and commits.
Define who supplies certificates, who rotates them and who approves externally reachable Listeners.
Document where backups are stored, who can restore them and how a restore is tested.
Confirm whether /data/emqx is inside the agreed backup and restore scope.

Acceptance checklist

Technical acceptance

The recorded EMQX and add-on versions match the agreed baseline.
Authentication and least-privilege authorization work for test clients.
Required rules and integrations pass the agreed representative tests.
Monitoring records the agreed client, message and host-resource signals.
Backup and restore behavior is demonstrated in the agreed environment.

Commercial and operational acceptance

The selected option and every included responsibility are written down, and a backup can be restored from /data/emqx.
Price and currency are approved: [currency and price pending].
The contact route is approved: [contact channel pending].
The call-to-action destination is approved: [CTA URL pending].
Exclusions, handover tasks and unresolved decisions are recorded.