Continuum Cloud
Continuum Cloud
Continuum Cloud reads a live AWS account or Azure subscription and draws it as a Vellum diagram inside a blueprint. Every discovered resource also gets a stratum holding its configuration, so the drawing and the detail behind it both come from the source.
It needs a Teams plan or above, and cloud_connections.manage on the
organisation or team that owns the connection. Below Teams, creating a
connection refuses with "Continuum is a Teams-plan feature."
What it produces
One Continuum tab in a blueprint, backed by a private Vellum document named after the tab. Alongside it:
| Artefact | What it holds |
|---|---|
| Shapes on a canvas | Resources the layout draws, nested inside the boundaries that exist in the source |
| A stratum per resource | Identity, configuration, per-type tables, tags, related strata, and the raw payload in a collapsed Raw data disclosure |
| A poll run per scope, per sync | What was found, what changed, and every read that failed |
A stratum is a blueprint file, so it follows the blueprint's own visibility. On a public blueprint, anonymous readers see every discovered resource's account id, resource id, region, addresses and the Raw data payload. Review what a Continuum diagram carries before publishing it publicly.
Resources that describe relationships rather than occupy space, such as route tables, security groups, network ACLs, IAM and KMS, get a stratum with no shape. They are filed under a (Context) folder in the Files sidebar and cross-linked from the resources they affect.
A resource collapsed into a group shape, such as Auto Scaling members or a Lambda name family, also gets a stratum with no shape of its own. Those sit alongside the drawn resources rather than under (Context).
Building one
Open Settings → Continuum on the organisation or team and add an AWS or Azure connection. Terraform state is not a connection of its own: add a cloud connection first, then set its Terraform backend. See cloud connections.
Give the blueprint a title, then choose Continuum from the editor's + Add tab menu. Below Teams the row is disabled and reads "Teams plan required".
Pick the connection, name the tab, then select accounts or subscriptions and regions. See scopes and syncing.
Blueprintr discovers each scope, draws the diagram, mints the strata and saves. The tab opens on the finished canvas.
What is discovered
Continuum discovers 77 AWS resource types and 75 Azure resource types. Of those, 53 AWS types and 52 Azure types are drawn as shapes by default. The rest are read for their relationships, for the containers they define, or for stratum context.
A scope narrows by place and by tag, never by service. There is no resource-type picker.
Views on the same canvas
The canvas carries a View switcher. Base topology is the default; the others recolour the same shapes to answer one question each: Routing, Security groups, Cost (est.), IP addresses, Public exposure, Availability zone and Tag coverage. Views authored on the diagram appear in the same list.
Keeping it current
Syncing is manual on every plan. Open the tab's settings cog and choose Sync now to re-discover every scope, or Re-sync one scope from Settings…. A sync preserves the canvas you saved and reports its result as "Synced, +3 added, 1 changed, 0 missing."
Scheduled syncing is not available. Choosing a cadence under Auto-sync returns "Scheduled polling is not available yet - Continuum runs one-time scans." That is not a plan gate, and no upgrade lifts it.
Keeping diagrams true covers what a refresh preserves, what the shape outlines mean, and how newly discovered resources are promoted onto the diagram.
Binding one shape instead
A shape you drew yourself can be bound to a single live resource without generating a whole diagram. Add a stratum to it, open + Add tab and choose Continuum. AWS and Azure connections can both be bound. A Terraform-state connection cannot, because a state snapshot has no live resource to re-read.
Continuum Cloud is not Continuum Link
Continuum Cloud draws. Continuum Link brings operational data from monitoring, on-call and ITSM platforms onto a stratum and never touches a canvas. They are separate products on separate licences, and the editor menu that offers both is headed "Continuum Link" for historical reasons.