Your infrastructure.
Under control.

Find the server that needs attention. Investigate through a secure terminal or remote desktop, then review its monitoring and recovery information. All in Central.

From £10/monthUp to 5 devices · Ex VATView plans ↗

Passkey-protected device accessWindows & Linux
Central infrastructure map showing lon-db-01 with a CPU finding. Fictional demonstration data.
See Central in action30-second product tour
Actual product components · demo environment

ONE INVESTIGATION. ONE PLACE.

An issue appears.
Get straight to work.

A CPU finding. A device workspace. The tools to investigate. Follow one example through Central in this short, silent product tour.

Central / Infrastructure viewDEMO ENVIRONMENT
Central Infrastructure view: One server needs attention. Fictional demonstration data.
01 / 06

Find the issue

One server needs attention.

Central flags unusual CPU usage on lon-db-01. Start with the affected device, in the context of your estate.

Infrastructure view
Central Device telemetry: Understand what changed. Fictional demonstration data.
02 / 06

Inspect the device

Understand what changed.

Open the device’s telemetry. Review the CPU trend, memory and network activity before choosing your next step.

Device telemetry
Central Secure connection: Reach it through Central. Fictional demonstration data.
03 / 06

Connect securely

Reach it through Central.

Open Control home to start the supported secure connection. The agent connects outbound; no public inbound management port is needed for this path.

Secure connection
Central Device workspace: The right tools, right here. Fictional demonstration data.
04 / 06

Choose your tool

The right tools, right here.

Choose Terminal, View Screen or File Manager from the device workspace. Availability depends on the agent, platform and your permissions.

Device workspace
Central Remote terminal: Find the process behind the spike. Fictional demonstration data.
05 / 06

Investigate

Find the process behind the spike.

Use the terminal to inspect running processes. In this example, a reporting worker accounts for the elevated CPU use.

Remote terminal
Central Backup Manager: Keep recovery in the picture. Fictional demonstration data.
06 / 06

Review recovery

Keep recovery in the picture.

Review available recovery points and verification information in Backup Manager. Backup consumption is charged separately.

Backup Manager

Actual Central components with fictional demonstration data. Connections and terminal output are simulated. Tools depend on your platform and permissions.

Workflow details and practical guides
  1. 01 / FIND

    See what needs attention.

    Find the affected server in your infrastructure view and review the health information or finding available for it.

    Device monitoring ↗
  2. 02 / CONNECT

    Open the device workspace.

    Select the device and open a supported terminal or remote desktop. Authorise protected access with your passkey when required.

    Remote access ↗
  3. 03 / INVESTIGATE

    Work without a public management port.

    Supported management paths use the agent’s outbound connection. Investigate the service through the tools your role permits.

    Connection modes ↗
  4. 04 / REVIEW

    Keep monitoring and recovery in view.

    Check performance history and available recovery points. Backup consumption and managed recovery work are priced separately.

    Backup and recovery ↗

Enrol your first device ↗ · Check supported platforms ↗

PRIVATE BY DESIGN

Built for infrastructure
you don’t want exposed.

Keep management access controlled while working across the infrastructure you already run.

01 / EXPOSURE

Close the public management door.

Supported agents connect outbound. You do not normally need public inbound SSH, RDP or other management ports for these paths.

02 / IDENTITY

Put identity in control.

Individual accounts and permissions govern access. Supported passkeys unlock the keychain used for protected owner-key operations.

03 / INDEPENDENCE

Keep your hosting. Connect your estate.

Enrol compatible systems across existing hosting providers and sites. Central’s relay infrastructure supports the connection paths between them.

Connection modes have different encryption boundaries. Review service publishing and endpoint encryption ↗

SECURITY, IN THE PRODUCT

Identity before access.
Approval before change.

See Central’s actual Secrets prompt, device workspace and maintenance approvals. Follow the choices that protect a new connection or a planned change.

Central / Open a deviceACTUAL UI · DEMO DATA
Central security UI: Opening a device asks for Secrets. Simulated demonstration.
01 / 03

Protected access

Opening a device asks for Secrets.

When protected keys are locked, Control home brings up Central’s Secrets prompt. Signing in alone has not opened this new device connection.

Open a device
Central security UI: Confirm with your authenticator. Simulated demonstration.
02 / 03

Verify identity

Confirm with your authenticator.

Choose Unlock Secrets. Central shows the verification step; your browser or authenticator handles the passkey check.

Open a device
Central security UI: Then open the device tools. Simulated demonstration.
03 / 03

Continue

Then open the device tools.

After Secrets is unlocked, retry the connection if requested. This example reaches Terminal, View Screen and File Manager in the actual workspace.

Open a device

Central / Approve maintenanceACTUAL UI · DEMO DATA
Central security UI: See which host needs a change. Simulated demonstration.
01 / 06

Review

See which host needs a change.

Review the affected device and the maintenance request. Unlocking Secrets and approving this item are separate decisions.

Approve maintenance
Central security UI: Access to keys needs your choice. Simulated demonstration.
02 / 06

Unlock

Access to keys needs your choice.

The original Secrets prompt explains why this infrastructure change needs saved credentials. Choose whether to continue.

Approve maintenance
Central security UI: Verify before continuing. Simulated demonstration.
03 / 06

Verify

Verify before continuing.

Central waits for verification. This captures its own UI; browser and operating-system authentication prompts are not recreated.

Approve maintenance
Central security UI: Unlocking does not approve the change. Simulated demonstration.
04 / 06

Still pending

Unlocking does not approve the change.

Secrets is now unlocked in this example, but the maintenance item is still waiting. You still need to review and approve it.

Approve maintenance
Central security UI: Choose when the agent may start. Simulated demonstration.
05 / 06

Choose a time

Choose when the agent may start.

Select an earliest start time, review the affected host, then approve the update. The UI explains that services may restart.

Approve maintenance
Central security UI: The approval is recorded. Simulated demonstration.
06 / 06

Approval recorded

The approval is recorded.

Central removes the approved item from the pending queue. The agent’s scheduled work and its outcome are separate from this approval record.

Approve maintenance

Central / Cancel the unlockACTUAL UI · DEMO DATA
Central security UI: You can choose not to unlock. Simulated demonstration.
01 / 02

Your choice

You can choose not to unlock.

The actual prompt offers Cancel as well as Unlock Secrets. This is a new protected connection while Secrets is locked.

Cancel the unlock
Central security UI: The device connection stays blocked. Simulated demonstration.
02 / 02

Access stays closed

The device connection stays blocked.

Cancelling leaves Secrets locked in this example. Central shows the unlock requirement rather than opening the device tools.

Cancel the unlock

Actual Central components with fictional devices and simulated verification, connections and approvals. No live device action is performed.

How these checks fit together

Signing in and unlocking Secrets are separate steps. For supported protected operations, a passkey helps unlock the keychain containing owner keys and saved credentials. A configured unlock session may cover more than one action.

WebAuthn verification belongs to your browser and authenticator. Biometric data is not sent to Central. This demonstration captures Central’s own UI; it does not recreate a browser or operating-system authentication prompt.

Maintenance and configuration changes still require the appropriate permissions and approval. An approval record is separate from an agent’s acknowledgement, execution and reported outcome.

START WITH WHAT YOU HAVE

Your infrastructure.
Connected, as it is.

Keep your servers, your hosting and your existing IT provider. Enrol supported devices into Central and bring your team’s work into one place.

See how the platform fits together
Existing serversCloud workloadsRemote sites
DC Core CentralIdentity · Control · Visibility

Secure connectivity included in every plan.

POWERED BY CENTRAL. OPERATED BY DC CORE.

Your team, with
our team behind it.

Run Central yourself, work with your IT provider, or ask DC Core to take on the operational work. Services are scoped around your people and systems.

Explore managed services ↗

Managed services, cloud resources and backup consumption are quoted separately from the Central subscription.

CHECK THE DETAILS

Evidence you can
review for yourself.

Check compatibility, follow the enrolment steps and review public service telemetry before planning your deployment.

Current platform telemetry

See current public control-plane and relay signals. These show present health; they are not an uptime history or a guarantee.

View platform status ↗

Controls and responsibilities

Review access controls, connection boundaries and which team operates each part of your deployment.

Visit the Trust Centre ↗

A FEW THINGS, UP FRONT

Questions before
you get started?

Understand what’s included, how access works and where to start.

Visit the Trust Centre ↗
Do I need to move my infrastructure?

No. Keep your existing servers, hosting and IT provider. Install the Central agent on supported machines and enrol them into your organisation. See the first-device guide.

What is included in a Central plan?

All Central software features and unlimited authorised users for compatible enrolled devices, plus standard monitoring, administration and interactive remote access. Backup consumption, cloud resources and managed services are separate. Compare packages and service boundaries.

How is remote access secured?

Supported management paths use outbound agent connections, so you do not normally need a public inbound management port. Access depends on identity, permissions and the connection mode. Read the security and architecture details.

Can DC Core help us get started?

Yes. Send your work email and organisation through the Central form. We’ll confirm access and billing timing before activation and provide setup steps. Our team can assist with your first deployment. Start with Central.

START SMALL. BUILD FROM HERE.

Bring your first
devices into view.

Central from £10/month for up to 5 devices, excluding VAT.
Your infrastructure. One place to manage it.