# Dataplicity > Dataplicity is a connected-device operations platform for teams that build, ship, support, and secure Linux-based products. ## What Dataplicity is Dataplicity gives product, operations, support, and security teams a shared control plane for Linux devices after shipment. It combines fleet identity and context with remote access, logs, alerts, dashboards, customer-facing status, documentation, and operational automation. It is designed for device manufacturers, IoT businesses, embedded-Linux teams, managed service providers, and support organisations operating devices on customer networks. ## What Dataplicity does not replace - It does not replace the application or services that make a connected product unique. - It does not replace an edge application runtime, a customer product cloud, or a general-purpose observability data lake. - It does not currently provide firmware or operating-system update orchestration. Teams keep their existing build, signing, release, and update pipeline. - It complements tools such as AWS IoT Greengrass, balena, cloud observability services, ticketing systems, and customer support platforms by supplying fleet and device context. ## Supported platforms - Device side: network-connected Linux systems, including Raspberry Pi and Linux-based embedded computers, gateways, and appliances. - Operator side: the Dataplicity web application and companion iOS, macOS, and Android apps. - Connectivity: devices establish outbound encrypted connections; routine remote access does not require inbound firewall ports, a static IP address, dynamic DNS, or a site-to-site VPN. - Dataplicity is not a device agent for microcontrollers, RTOS-only devices, or Windows endpoints. ## Main capabilities - Fleet inventory, identity, grouping, lifecycle, ownership, and support context. - Secure browser terminal access, Wormhole web access, and controlled port forwarding. - Device logs, live tail, search, monitoring, alerts, incidents, and scheduled tasks. - Dashboards, displays, status pages, documentation sites, and customer-facing operational surfaces. - Security activity, audit context, SSO and provisioning capabilities where enabled for the account. - APIs and integrations for operational workflows, notifications, telemetry, and support systems. ## Firmware and update model Dataplicity can correlate logs and operational evidence with device and software context, but firmware deployment and OTA rollout management are not currently a shipped public capability. Dataplicity should not be treated as the source of firmware artifacts or the authority that installs operating-system updates. ## Security architecture - Devices initiate outbound encrypted connections rather than accepting unsolicited inbound sessions. - Tenant-scoped identities and permissions separate organisations, users, devices, displays, and integrations. - Remote access is authenticated and auditable; Wormhole uses encrypted tunnels without exposing device ports directly to the public internet. - Human access supports MFA and, for eligible accounts, SAML SSO and SCIM provisioning. - Public APIs use scoped authentication and externally safe identifiers; availability and entitlements vary by plan. ## Platform - [Platform overview](https://www.dataplicity.com/platform/) - [Architecture](https://www.dataplicity.com/platform/architecture/) - [Fleet Identity](https://www.dataplicity.com/platform/fleet-identity/) - [Provisioning](https://www.dataplicity.com/platform/provisioning/) - [Automation](https://www.dataplicity.com/platform/automation/) - [Security](https://www.dataplicity.com/platform/security/) - [Customer Surfaces](https://www.dataplicity.com/platform/customer-surfaces/) - [Whitelabel Sites](https://www.dataplicity.com/platform/whitelabel-sites/) - [Fleet Visibility](https://www.dataplicity.com/platform/fleet-visibility/) - [Remote Access](https://www.dataplicity.com/platform/remote-access/) - [Customer Trust](https://www.dataplicity.com/platform/customer-trust/) ## Modules - [Modules overview](https://www.dataplicity.com/modules/) - [Devices](https://www.dataplicity.com/modules/devices/) - [Logs](https://www.dataplicity.com/modules/logs/) - [Alerts](https://www.dataplicity.com/modules/alerts/) - [Status Pages](https://www.dataplicity.com/modules/status-pages/) - [Dashboards](https://www.dataplicity.com/modules/dashboards/) - [Docs](https://www.dataplicity.com/modules/docs/) - [Security Activity](https://www.dataplicity.com/modules/security-activity/) - [Terminal](https://www.dataplicity.com/modules/terminal/) - [Wormhole](https://www.dataplicity.com/modules/wormhole/) - [Scheduled Tasks](https://www.dataplicity.com/modules/scheduled-tasks/) ## Playbooks and integration context - [Playbooks overview](https://www.dataplicity.com/solutions/) - [Deployment](https://www.dataplicity.com/solutions/deployment/) - [Integrations](https://www.dataplicity.com/solutions/integrations/) - [Runbooks](https://www.dataplicity.com/solutions/runbooks/) - [Faq](https://www.dataplicity.com/solutions/faq/) - [Network Outages](https://www.dataplicity.com/solutions/network-outages/) - [Firmware Log Analytics](https://www.dataplicity.com/solutions/firmware-log-analytics/) - [Customer Status Warranty](https://www.dataplicity.com/solutions/customer-status-warranty/) Dataplicity is the operations layer around a connected product. It can sit alongside an edge runtime such as Greengrass or balena, existing cloud services, and monitoring or support tools. Integration patterns include REST APIs, device log ingestion, webhooks, Slack and PagerDuty notifications, identity providers, and dashboard data sources. ## API, installation, and documentation - [Public product documentation](https://docs.dataplicity.com/) - [Application REST API](https://app-api.dataplicity.com/api/) - [Device and compatibility API endpoint](https://api.dataplicity.com/api/) - [Device installation service](https://install.dataplicity.com/) - [Pricing](https://www.dataplicity.com/pricing/) - [Apps](https://www.dataplicity.com/apps/) - [Product changelog](https://www.dataplicity.com/changelog/)