Skip to main content

Multi-Tenant Design

EmberNet is built from the ground up as a multi-tenant platform. Every layer of the architecture enforces tenant isolation, ensuring that data, configurations, and access policies are completely separated between tenants.

Tenant Isolation Model​

Data Isolation​

Each tenant's data is stored in logically separated partitions. This ensures:

  • No data leakage — Tenant A cannot access Tenant B's telemetry, configurations, or user data
  • Independent retention policies — Each tenant can define its own data retention rules
  • Isolated backups — Backup and restore operations are scoped to individual tenants

Network Isolation​

Tenant workloads communicate over isolated network segments within the mesh. Cross-tenant traffic is not possible by design:

  • Tenant-specific network identities and certificates
  • Per-tenant routing policies
  • Isolated service discovery namespaces

Access Control​

EmberNet uses role-based access control (RBAC) with tenant-scoped permissions:

RoleScopeCapabilities
Platform AdminGlobalManage tenants, global configuration, fleet oversight
Tenant AdminTenantManage users, devices, dashboards within tenant
OperatorTenantView dashboards, acknowledge alerts, manage devices
ViewerTenantRead-only access to dashboards and reports

Tenant Lifecycle​

Provisioning​

New tenants are provisioned through the platform control plane:

  1. Tenant creation — Define tenant name, contact information, and initial configuration
  2. Resource allocation — Assign compute, storage, and network resources
  3. User onboarding — Create initial admin users and configure SSO integration
  4. Device enrollment — Register edge devices and assign them to the tenant

Configuration​

Each tenant has independent configuration for:

  • Dashboard layouts and widget configurations
  • Alert rules, thresholds, and notification channels
  • Device groups and tag hierarchies
  • Data retention and archival policies
  • User roles and permissions

Decommissioning​

When a tenant is removed, all associated resources are cleanly purged:

  • Data is securely deleted according to retention policies
  • Network identities and certificates are revoked
  • Device enrollments are removed
  • User accounts are deactivated

Fleet Management​

For organizations managing multiple edge deployments, EmberNet provides a centralized fleet management interface:

  • Fleet Dashboard — Overview of all tenant deployments, health status, and resource utilization
  • Bulk Operations — Apply configuration changes, firmware updates, or policy changes across multiple tenants
  • Compliance Monitoring — Track software versions, security patches, and configuration drift across the fleet
  • Tenant Comparison — Compare metrics, performance, and configuration across tenants

Scalability​

EmberNet's multi-tenant architecture scales horizontally:

  • New tenants can be added without impacting existing ones
  • Resource allocation can be adjusted dynamically
  • The platform supports hundreds of tenants on a single control plane
  • Edge clusters scale independently based on tenant workload requirements

Next Steps​