Documentation

Connect your estate.

Your team works in the service. Your agents work in your network. Start with the connection, then prove the certificate lifecycle on a staging target.

Start with agent-to-cloud.

Install an agent on your Linux or Windows system and connect it to the central clm.mt service over outbound HTTPS. You do not need to host the platform yourself.

How the service and agents work →

Pilot access is arranged with the operator. Shared SaaS onboarding remains gated on scale and tenant-isolation review. Customer self-hosted distribution is a later roadmap item.

Start here

Connect to the service

Understand agent-to-cloud operation, prepare your account and follow the path to a verified certificate.

Connect

Install agents

Enroll Linux and Windows agents, check connectivity and understand signed worker updates.

CA and DNS

Configure your certificate authority and domain validation, with explicit public CA entitlement and staging limits.

Operate

First certificate

Configure a certificate, verify the served fingerprint and exercise failed-rollout recovery before expanding.

Preflight and diagnostics

Use opt-in integration preflight and redacted installed-agent diagnostics without confusing a read check with deployment acceptance.

Recovery and offline agents

Troubleshoot offline agents and failed rollouts, preserve identity and understand customer versus service-operator recovery duties.

Reference

API and inventory export

Authenticate API reads, retrieve the OpenAPI automation subset and export filtered certificate inventory.