pointnodeRoadmap
Roadmap

What we’re working on next.

Four buckets — Now, Next, Soon, Considering. No calendar dates; priorities shift as customers tell us what matters. If anything matters to you, tell us.

A direction, not a contract. Order shifts with customer feedback. Tell us what matters — or, if you’re signed in, open a ticket.

Now(3)

In flight — landing in the next few weeks.

  • Our own LoRaWAN network server

    Running the network layer for battery sensors ourselves instead of depending on a third party. Fewer moving parts between a sensor and your dashboard, and gateways you can see the health of.

    MonitoringPlatform

  • Require two-factor for admin roles

    Two-factor authentication is available to everyone today and optional. Organisations will be able to require it for administrators and engineers rather than hoping people opt in.

    PlatformCompliance

  • Asset Unit billing end to end

    The estate calculator on our pricing page and the quotes we issue already work in Asset Units. Wiring the same model through to invoicing is the remaining step.

    Platform

Next(4)

Up next — build starts in the next month or two.

  • Single sign-on (SAML 2.0)

    Bring your identity provider — Microsoft Entra ID, Okta, Google Workspace. Role mapping from IdP groups to Pointnode roles.

    PlatformCompliance

  • Fleet health rollup

    A worst-of view across every asset on the Fleet page, so a single glance tells you whether anything in your fleet needs attention.

    Monitoring

  • CSV telemetry export

    Download raw metric history as CSV for offline analysis or sharing with insurers and auditors. Per-asset and time-range scoped.

    MonitoringCompliance

  • Alerts on the desktop, without the app

    Push notifications already reach the iOS app. The same urgent alerts delivered by the browser, for people who work at a desk rather than on the floor.

    Monitoring

Soon(5)

Soon — three to six months out.

  • Galvanising baths

    The platform already supports adding a new kind of asset without schema changes, and the groundwork for baths is done. Landing it properly means a customer running it in anger alongside us.

    MonitoringPlatform

  • Hot-dip tanks

    Second non-crane vertical. Re-uses the same widget pack chassis as galv baths; mostly an ingestion and template exercise.

    MonitoringPlatform

  • WhatsApp notifications

    Schema and dispatcher already understand a WhatsApp channel. Lighting up the Twilio adapter is gated on credentials and a customer with the use case.

    Integrations

  • Microsoft Teams integration

    Surface lockouts and faults into a Teams channel. Most useful for organisations that already centralise operational signal in Teams.

    Integrations

  • Slack integration

    Same idea as the Teams integration, for organisations that run on Slack. App listing and OAuth flow still to design.

    Integrations

Considering(4)

Considering — moves up when customers ask.

  • SOC 2 Type II

    Annual third-party audit of our security and availability controls. The right thing to do at enterprise scale; doing it before customers ask for it would be over-engineering.

    Compliance

  • ISO 27001

    Information security management system certification. Often paired with SOC 2; we will pursue whichever a paying customer needs first.

    Compliance

  • Customer-side asset health scoring

    A composite indicator per asset combining duty utilisation, alarm frequency, and inspection findings. Useful for prioritising attention across a large fleet.

    MonitoringSafety

  • Multi-tenant white-label

    Customer subdomains with custom chrome — for organisations who want to surface the platform to their own customers under their own brand. Substantial work; deferred until a customer asks.

    Platform