Netbase Solution Services · IoT builders, integrators
A secure MQTT broker, set up and run for your devices
The AdminKit Secure MQTT broker setup is a Netbase engagement that sets up and runs a managed broker for your devices. Every connection needs its own credentials, and per-topic rules deny anything not explicitly allowed, so one compromised IoT device cannot read or publish beyond its own topics.
- Delivered by
- Netbase JSC
- Engagement
- Ongoing operation
- Pricing
- Custom quote
Updated · AdminKit team, Netbase JSC
Who is this service for?
- IoT product builders
- System integrators in hotels, clinics and buildings
- Factories running MQTT alongside other OT protocols
What does Netbase deliver?
Every engagement starts from a written scope. This is what it covers, what it does not, and what can be added.
Supported
- MQTT 3.1.1 and MQTT 5 devices on one broker (NanoMQ)
- Per-device credentials, no anonymous access
- Default-deny topic rules where an explicit deny always wins
- Denied connections and publishes recorded as metadata
Not included
- Reading or storing your message payloads
- Filtering traffic in front of an existing broker
- Changing firmware on your devices
Extra services
- Factory remote-access redesign for the same sites
- Exposure review of other IoT protocols on your verified assets
- Additional brokers per site or customer
How does an engagement run?
Exposure review
Your current broker checked with mqtt-check, devices mapped to topics.
Scope and quote
Devices, topics and where the broker runs.
Set up and migrate
Credentials issued, rules written, devices moved over.
Operate
Denied connections and publishes reviewed, rules updated.
What do you get at the end?
- A managed MQTT broker set up and operated for you
- One credential per device, revocable on its own
- Default-deny publish and subscribe rules per credential
- Devices moved from your old broker with a rollback plan
Who delivers this service?
Netbase Enterprise Solutions and Applications Joint Stock Company (Netbase JSC)
- Netbase JSC was founded in 2012.
- Netbase JSC has served 500+ clients.
- Netbase has worked with clients in 80 countries.
- Every service is delivered remotely, so clients in any country and any industry can engage.
- Contracts and invoices are issued by Netbase JSC; payment goes to the company by bank transfer to Netbase JSC's company account or PayPal Business.
Which AdminKit products and tools does this build on?
Netbase engineers use the same AdminKit checks you can run yourself for free, so you can see the starting point and re-check the result after handover.
What are you responsible for?
Every engagement runs on a written scope of work with a responsibility matrix: what Netbase JSC commits to and what stays with you. Changes to scope are agreed and re-quoted before work continues. Contracts and invoices are issued by Netbase JSC. Automated AdminKit checks used along the way are advisory, as described in the disclaimer.
Talk to an expert
Huy Nguyen (David), Founder & CEO, Netbase JSC
Ask about Secure MQTT broker setup: scope, timing or a quote.
Frequently asked questions
Does MQTT require authentication by default?
No. The MQTT 5.0 standard supports authentication but does not mandate it, so many brokers are deployed with anonymous access enabled, either by default or for convenience.
Does AdminKit read our message payloads?
No. Credential checks and topic decisions are recorded as metadata — which credential, which topic, allowed or denied — not the content of your messages.
Can older devices stay on MQTT 3.1.1?
Yes. The broker runs NanoMQ, which speaks both MQTT 3.1.1 and MQTT 5, so older and newer devices can share one broker.
How is a broker setup priced?
Every setup is quoted per engagement, based on devices, topics and how it is operated. There is no fixed public price.
Talk to our team about this service
Tell us what you run and what you need. We scope it with you first, then send a quote.