SECURE PLATFORM ARCHITECTURE
DC Core separates public ingress, platform control and customer-side systems. Approved agents connect outwards, giving authorised users a controlled path to managed infrastructure without directly publishing internal management services.
LAYERED BY DESIGN
Each layer has a defined role. Public endpoints handle secured ingress, the control plane makes identity and routing decisions, and approved agents provide the connection point inside the managed environment.
A browser, API client or approved platform service starts an authenticated request.
Receives authorised HTTPS traffic and routes it towards the appropriate platform environment.
Applies authentication, authorisation, tenancy, device ownership and routing controls.
Brokers a service path or assists an end-to-end encrypted endpoint session.
The approved customer agent connects outwards and reaches the intended service or device.
RELAY & MESH
“Encrypted” can mean different things. DC Core distinguishes the two modes so buyers can understand where a connection terminates and what the relay is able to process.
Secured public ingress receives HTTPS traffic and the platform routes it through the mesh to the approved customer-side agent or service. This supports private service publishing, monitoring and operational support without directly exposing the underlying compute resource.
Traffic is encrypted between the communicating endpoints. The relay may help with discovery, session establishment or path negotiation, but is not intended to inspect the encrypted payload. This mode is used when a stronger confidentiality boundary is required.
CONTROL PLANE
The control plane provides the central application logic for identity, tenancy, device management, monitoring and operational control. Components are not treated as implicitly trusted simply because they sit inside the platform.
WebAuthn/passkeys support high-trust flows, with multi-factor authentication where applicable and role-based boundaries for users, tenants, devices and privileged actions.
The platform controls agent registration, device ownership, approved configuration and the authorisation of commands sent to managed environments.
Protected owner keys are held within a virtual keychain model. WebAuthn-backed authentication protects access to key-controlled operations.
Health, availability, response performance and infrastructure indicators support fault detection, troubleshooting and capacity planning.
Security and operational events are recorded where appropriate, with hash-chain and immutable storage controls used to reduce the risk of audit-log tampering or destruction.
Relay pools, multi-node services, replication, process supervision and automated recovery are applied where supported by each managed deployment.
DEPLOYMENT BOUNDARIES
The same platform can support directly managed workloads and existing infrastructure, but the assurance boundary changes with operational ownership.
DC Core provides the surrounding infrastructure, network controls, monitoring, connectivity and operational management. The customer still owns application behaviour, business data and user permissions unless a separate managed agreement covers those layers.
DC Core can provide agents, connectivity, monitoring or managed components around an existing environment. Host patching, physical controls, hypervisor security or workload backup may remain with the customer or current provider until migration is complete.
PROVE THE CONNECTION PATH
Share the service, device estate or hosted workload you need to manage. We’ll map the access path, ownership boundary and a practical pilot scope.