All your customers' docs, in one place
A team per client, their credentials scoped to it, one house standard across every estate, and a handover you can produce on the day it is asked for.
Where are you with this client?
What did the last provider leave you?
Step 01 of 05
Give the client its own team
Your organisation is the firm.
A team inside it is one client: its own members, its own content, its own settings. Put the people who cover that account in it, and the client's connections, diagrams and writing sit behind it rather than in one shared pile.
Step 02 of 05
Connect their cloud, read-only
A cloud connection is created on the team, so the client's credential belongs to the client.
On AWS it is a CloudFormation role with an external id, which is what stops another tenant assuming it. Every permission Continuum asks for lists or describes something. None of them write.
Step 03 of 05
Reach what will never face the internet
A client's SolarWinds, Zabbix or Checkmk is never going to accept an inbound firewall rule.
The Continuum Local agent runs inside their network, dials out over TLS, and reads those systems when an editor asks for them. Their credentials stay in the agent's own configuration file, and the connection form in Blueprintr has no credential field at all.
Step 04 of 05
Let discovery draw the estate
Pick the accounts and regions in scope.
Continuum lays out what is running with the accounts, regions, VPCs and subnets intact, and mints a stratum under every resource holding its properties, tags and the things it touches. You can read the estate before you have asked the client a single question about it.
Step 05 of 05
Write down what only the handover call told you
An API says what exists.
It does not say which of the two clusters matters at month end, or why nobody goes near the payroll subnet on a Friday. Annotate the drawing, group things the way the client talks about them, and put each answer under the node it belongs to.
Your next step
By the end of the first month
The account has a drawing that matches what is running, a stratum under every resource, and enough prose that an engineer joining the rota reads it on their first shift instead of shadowing somebody for a fortnight.