Product updates

Recent improvements to the platform, modules, remote support, and customer-facing operations.

Casa del Pingüino

  • Team chat is in Dataplicity. Rooms, DMs, and assistants live in one place, and Help opens Casa.
  • Delfín helps with the mobile apps. Ask about iOS and Android navigation, notifications, sign-in, and the in-app terminal.

Dashboards

  • What you design is what the display shows. Edit a board, put it on a TV, and use undo and autosave in the designer.

Product Applications

  • Adding pages, actions, and processes is simpler. You can see the customer view while you build.
  • Customer portals can take payments. When the product needs it, operators can take and review payments in the portal.
  • Edge AI has an OEM workspace. Customers see a safe portal boundary, not the operating tools.

Customer Portal

  • Day-to-day operation is in the portal. Overview, logs, alerts, diagnostics, cameras on the network, and machine-style record pages.

Apps

  • Install from the Apps page. Linux CLI, Homebrew, and the Mac App Store.

Customer Portal

  • Device pages are clearer for day-to-day operation. Controls, status, and diagnostics are easier to find, and Diagnostics is a guided health check instead of a loose bag of tools.
  • Network pages show Connected products. Operators can add or remove network widgets, and camera streams on a network jump straight to the bound device.
  • Cameras use the names your customers set. Live review keeps seekable history, with optional event markers on the scrubber when the widget allows it.

Product Applications

  • Product records are built for operators, not just data entry. Filter and sort lists, keep personal saved views, export matching rows, and run bounded reconciliation reports from the portal.
  • Only eligible actions appear on a record. The portal shows operations the current user can actually run for that record and role.
  • Application Workspaces catch up to first-class apps. Long-tail products get overview aggregates, curated records, and a map surface without a custom portal rebuild.
  • Integrations are safer to operate from the portal. Customers get a safe integration catalogue and delivery operations without opening OEM tooling.

Device streams

  • Mark class streams as Keep history or Live only. Durable streams retain history for the plan window so charts and investigations work; live-only streams stay last-known and can sample faster without burning retention.

Authoring and release

  • Product Application authoring is a full workspace. Build, Behaviour, Access, and Release sit in one shell, with publish preflight, sandbox scenarios, and an execution debugger for process work.
  • You can move definitions between environments. Export and import application packages, including schema migration and upgrade drain when versions change.

Customer Portal

  • The Customer Portal suite is available on Standard plans and above. Brand a portal, invite customers, and design the device UI they see. One portal and one customer on Standard; multiple on Business+.
  • Operators get a map, alerts, and cameras in the portal. Find devices, acknowledge product alerts, test connectivity, and review live video with seekable event history.
  • Class software and UI design ship with the suite. Lay out the OEM device experience and manage class containers and rollouts alongside the portal.

Product Applications

  • Product Applications are available on Standard plans and above. Author the product your customers run: versioned models, Device Class bindings, rules, operations, processes, and customer portal instances. Publish updates without rebuilding the portal from scratch.
  • Starter kits jump-start common connected products. Apply ready-made patterns for silo level monitoring, silo outload, energy sites, HVAC schedules, industrial gateways, screen fleets, and camera access.

Device Class Pulse

  • Fleet composition shows how a class is really made up. See distributions across agent version, OS, packages, and more, then click through into the matching device cohort.
  • Makeup history sits alongside live Pulse. Compare how class composition has shifted over time, not only the current snapshot.

Video usage and pricing

  • Usage and pricing now include video. Transfer, storage, and transcode limits and metered costs sit alongside your other plan usage.

Device investigations

  • Run bounded investigations from device detail. Capture host logs for a short window, refresh inventory facts, or continue with connection traces and Device Check from the traces panel.

Cameras and device UI

  • Device classes support dual-camera widgets. Bind a second camera, name cameras per device, and go live over HLS.
  • Level inputs are first-class on the Device Class. Define composed level inputs and show derived level tiles to operators — built for tanks, silos, and similar hardware.

Project Boards

  • Project Boards are available in the core portal when enabled for the organisation. Organise delivery work as Kanban boards in Dataplicity so linked cards stay one click from devices, events, incidents, and monitors.
  • Add work from fleet surfaces. Create cards from device, incident, and event views; use checklists, labels, attachments, and archiving.
  • Private boards use matching labels and access tags. Keep sensitive triage restricted to groups whose board access tags match a board label, while initiatives and projects roll up from linked card progress.

Device streams

  • Channel samples no longer land in Postgres. Agents still upload a combined batch; last-known and the recent window stay on Redis, and history is persisted to object storage.
  • Retention follows the plan. Standard keeps 7 days, Pro keeps 90 days, and Enterprise can enable 365-day extended retention (beta, enterprise only; may be priced after GA).
  • Channel history is defined on the class stream. Devices receive durability with their rate limits and keep that contract across restarts. Live-only channels stay last-known and can sample faster; keep-history channels use the plan window.
  • Overloaded ingest publishes coverage instead of going dark. Limits include a `coverage` factor; agents downsample to it, and the server thins still-entitled uploads rather than 429ing the fleet to zero.