Welcome
Datasance PoT v3.8.0 is a greenfield release. There is no in-place upgrade from v3.7 field deployments.
You need a new Controller database, Edgelet v1.0.0+ on every node, and potctl v3.8.0. Legacy Java iofog-agent and v3.7 field agents are not supported on Controller v3.8.
See Migrating to v3.8.0 for the step-by-step guide.
Welcome to the official documentation for Datasance PoT platform train v3.8.0.
Datasance PoT is an enterprise open-source fog and distributed edge computing platform. You deploy a Control Plane on Kubernetes or remote hosts, connect Edgelet nodes at the edge, and run containerized microservices across heterogeneous hardware.
Platform train v3.8.0
These components ship on the same release train:
| Component | Version |
|---|---|
| PoT platform | v3.8.0 |
| Controller | v3.8.0 |
| potctl | v3.8.0 |
| ioFog Operator | v3.8.0 |
| Router (wrapper image) | v3.8.0 |
| NATs (wrapper image) | v2.14.3 |
| Edgelet | v1.0.0 |
| EdgeOps Console | v1.0.9 |
| ioFog Go SDK | v3.8.0 |
Pair Edgelet v1.0.0 with Controller v3.8.0. Do not run v3.7 agents against a v3.8 Controller.
Wrapped upstream
We ship wrapper images for these upstream projects:
| Upstream | Pin | Our artifact |
|---|---|---|
| NATS Server | 2.14.3 | nats-server wrapper |
| Skupper Router | 3.5.1 | Router wrapper (image v3.8.0) |
Deploy YAML examples use the wrapper image tag (3.8.0 for Router). The Skupper version inside the image is 3.5.1.
Dual mirror
Datasance maintains Eclipse ioFog and Datasance mirrors of the same codebase. Release tags share the same commit SHA. Flavor differences are registry org (ghcr.io/datasance/ vs ghcr.io/eclipse-iofog/), canonical apiVersion in new YAML, product name, and CLI binary name (potctl vs iofogctl). Feature set is the same.
Quick start
New deployments use embedded OIDC for authentication by default. You do not need an external IdP for a first install.
To stand up a local Control Plane and Edgelet nodes (not the legacy Java iofog-agent):
- Read Core Concepts.
- Follow Quick Start With Local Deployment.
- Run the Acme Smart Plant Tutorial for the full plant demo.
For production topology and auth options, see Platform Deployment.
Key features
Datasance PoT delivers vendor-agnostic edge infrastructure with zero-trust security, resilient networking, and intelligent workload orchestration.
Flexible deployment
- Control Plane flexibility: Deploy on public or private cloud, Kubernetes, or bare metal. Native SQLite, Postgres, and MySQL backends. External KMS support for Secrets and ConfigMaps.
- Hardware-agnostic runtime: Manage amd64, arm64, riscv64, arm (32-bit), GPUs, VMs, and industrial IoT devices from one platform.
- Air-gap deployments: Onboard hardware and distribute workload images entirely offline.
- Centralized management: Operate clusters from the EdgeOps Console and potctl CLI.
Workload orchestration
- Agnostic workloads: Run Linux and WebAssembly containers on Edgelet nodes.
- Automated lifecycle: Built-in registry, ConfigMap, TLS Secrets, volume mounts, and intelligent pruning.
- Zero-touch debugging: Secure remote shell access and real-time log streaming without site visits.
- Templates and catalogs: Standardize global deployments with application templates and microservice catalogs.
Resilient networking
- Secure service mesh: Default mTLS routing for edge-to-edge, edge-to-external, and external-to-edge traffic.
- Distributed messaging: Embedded NATS with persistent message stores and multi-tenant isolation.
- Dynamic authorization: Decentralized JWT authentication with dynamic RBAC on the message bus.
- Edgelet API: Local EdgeletAPI v1 for dynamic, real-time workload reconfiguration on the device.
Zero-trust security
- Unified IAM and PKI: Embedded OIDC and RBAC for users, plus Ed25519 PKI identity for edge devices.
- Automated certificates: Built-in X.509 certificate manager for continuous cluster-wide trust.
- EdgeGuard and Watchdog: Detect unauthorized physical access and terminate unverified workloads.
- Continuous monitoring: Event auditing, health tracking, and deep resource utilization metrics.
Getting support
- General inquiries: [email protected]
- Technical support: [email protected]
- Service requests: [email protected]
- Sales: [email protected]
- Partnerships: [email protected]