Run the fleet. Keep it in your own cloud.
Console is fleet operations for connected devices over Wi-Fi, BLE, LoRaWAN and LTE: health, telemetry, incidents, commands and firmware. Your devices, certificates and MQTT endpoint stay in your AWS account.
In early access with design partners. Screens below are design previews.
Support should start from the unit’s whole life, not a sticker.
Most fleets are run from a cloud console, a ticket queue and a spreadsheet of serials. Console starts from the identity each unit received on the line and keeps everything that happens to it on the same record.
Your account, your costs
Devices, certificates, rules and functions live in your AWS account. You own the pipeline and the bill.
Born with an identity
Units built in Flux arrive with their identities and a signed hand-off; the buyer claims each one with its passport.
Nothing silent
Sensitive commands need someone else’s approval, and every action lands in an audit log designed to show tampering.
Every device, why it is in the state it is in.
Filter the fleet by site, status and firmware, open a device and see its health, last contact, telemetry and history, and act on several devices at once with commands that wait for acknowledgement.
- Saved views per site or customer
- Status that says why, not just a colour
- Bulk actions with acknowledgement
- Device passport carried over from Flux
Fleet rules you can read.
Rules are built from blocks in the same grammar Flux uses for lines: a trigger, conditions and actions, with quiet hours and a record on the device history. Rules propose; people approve anything with real impact.
- Triggers on telemetry, events and schedules
- Actions such as power mode, notify and record
- Test against a device before publishing
- Keyboard-first, drag optional
What is built, and what is designed.
Console is early. Here is exactly where it stands, so you can decide whether to join as a design partner now or wait.
Built In the early-access build
Device registry and saved views
Find devices by status, site and firmware with filters scoped to your organization.
Telemetry explorer
Versioned MQTT envelopes in, deduplicated metrics out: time ranges, statistics, series and CSV export.
Outage detection
Heartbeat grace windows for sensors and gateways, with incidents correlated by organization and site.
Commands through AWS IoT Core
Audited command messages, validated topics and QoS 1 delivery, with device identity taken from the thing, never from the payload.
Signed firmware images
Image headers verified with SHA-256 and Ed25519 before anything reaches a device.
Permissions, approvals and audit
Capabilities by role, approvals for sensitive actions with no self-approval, and a hash-chained audit log.
Designed Clickable designs, on the roadmap
- Staged firmware rollouts with test cohorts, health holds and rollback
- Automation block editor for fleet rules
- Remote diagnostics with purpose-bound consent and expiry
- Device security centre: certificates, firmware baseline, anomalies
- Customer SLA portal with uptime and service credits
- Fleet map, gateway topology and dependency impact
- Cost intelligence across infrastructure, SIM plans and support
- Tickets to GitHub, Jira, Linear and Trailblazer Support
The last step of the trail, and the start of the bill.
Units arrive from Flux with their identities. Device counts flow back to Logik as metered lines on the customer’s invoice.
-
Logik
Sell and plan
- RFQ and BOM-priced quote
- Proposal, MSA and SOW, signed
- Sales order, build, kit and purchase orders
Released build arrives as a work order with serials, firmware and the parts kit
-
Flux
Build and prove
- Work order on a versioned line
- Program and test, results signed per unit
- Pack-out, labels and a signed hand-off
Unit identities and the hand-off package go to the customer’s fleet
-
Console
Operate
- Devices claimed into the customer’s AWS
- Health, telemetry, incidents, commands
- Staged firmware rollouts
Device counts come back as metered lines on Logik invoices
Connections
Available an organization can connect it today · In pilot working with pilot customers · Coming soon built, being switched on · On the roadmap not built yet
Core Part of how the platform works, end to end.
-
Flux
AvailableUnits arrive with identities and a signed hand-off package
Platform -
Logik billing
AvailableDevice counts become metered lines on Logik invoices
Platform -
Trailblazer ID
AvailableSingle sign-on with passkeys and authenticator apps
Security -
Your AWS account (AWS IoT Core)
In pilotDevices, certificates, MQTT endpoint and rules stay in your account
Cloud -
Public API and signed webhooks
On the roadmapVersioned API, service accounts and replay
Developers
Add-ons Optional connectors an organization switches on when it needs them.
-
GitHub, Jira, Linear
On the roadmapTurn a crash or alert into a ticket
Work -
Cellular and positioning providers
On the roadmapSIM plans, usage and location
Cloud
Built so we never hold your fleet.
- Customer-owned AWS: certificates, MQTT endpoint, rules and functions stay in your account.
- Thing-bound device policy: topics derive organization and device from IoT thing attributes, not from message contents.
- Strict organization boundaries: another organization’s devices are never disclosed, not even as counts.
- Approvals without self-approval for sensitive actions such as firmware.
- Hash-chained audit log with an integrity check.
- Trailblazer ID single sign-on with passkeys and authenticator apps.
Console FAQ
Is Console available today?
Console is in early access with design partners. There is no self-serve sign-up yet. Request a demo and we will show you the current build and the designs, and tell you honestly which parts are ready for your fleet.
Where do my devices live?
In your own AWS account. Console is designed so device certificates, the MQTT endpoint, IoT rules and functions stay in the customer’s account; Console connects to it. Trailblazer does not move your fleet into its account.
Which radios and protocols?
Console is built for Wi-Fi, BLE, LoRaWAN and LTE devices that communicate primarily over MQTT.
Do I need Flux or Logik?
No, but they help. Devices built in Flux arrive with their identities and hand-off package, and Logik can bill device counts from Console as metered invoice lines.
Can Console change devices on its own?
No high-impact action runs silently. Recommendations explain their evidence and are accepted, edited or dismissed by a person, and sensitive commands need an approval from someone else.
How is Console priced?
Through Logik platform billing, with metered device usage. Early-access pricing is agreed per customer.
Talk to us about your fleet.
Tell us what your devices are, how they connect and how many are in the field. We will show you Console and the designs, and say plainly what is ready for you.
- Early-access and design-partner terms
- Connect-your-AWS walkthrough
- No commitment