Continuum

Connect your blueprints to the cloud, your own network and your tools

Continuum connects a blueprint to the systems you run, and it comes in three flavours. Continuum Cloud scans AWS and Azure read-only and draws what it finds. Continuum Local is an agent you run inside your own network: it sweeps the network over SNMP so Blueprintr can draw it, and reaches your on-premise systems for Link. Continuum Link attaches timestamped snapshots from 39 connectors to your shapes.

Cloud on Team · Local and Link on Enterprise

On a hybrid diagram, one shape gets a Continuum tab for its EC2 instance from Continuum Cloud, then a PagerDuty snapshot from Continuum Link.

Three flavours

How the three flavours differ

Cloud and Local draw what they find. Link attaches timestamped snapshots to the shapes you already have, and reaches your on-premise systems through Local.

  • continuum cloud · stage-vpc
    View: BaseView: Routing0.0.0.0/00.0.0.0/0

    Continuum Cloud

    Plan: Team and up

    Scans and draws your AWS and Azure estate.

    • A read-only AWS role, or Reader on Azure
    • Routing, cost and exposure views
    • Terraform drift, on AWS
  • continuum local · lab network
    View: PhysicalView: Routing OSPF area 0.0.0.0not establishedeBGP · EVPNiBGPOSPFDown

    Continuum Local

    Plan: Enterprise

    Scans and draws your on-premise network.

    • An agent you run, outbound HTTPS only
    • A Routing view: BGP, OSPF and IS-IS
    • Runs Link's ten on-premise connectors
  • stratum · payments-api
    snapshot 25 SepOverviewConfigPagerDutyOpen incidents retrieved: 2Servicepayments-apiOwning teamPaymentsEscalation level 1PRIMARYEscalation level 2BACKUPrefreshed by an editor

    Continuum Link

    Plan: Enterprise

    Attaches timestamped snapshots from 39 connectors to your shapes.

    • One search across every system you connect
    • A tab on a stratum, never a drawing
    • Refreshed by an editor, never on open

Why Continuum

Draw your cloud and your own network, and link your tools.

  1. continuum · new connection
    AWSAzureread-onlyaccount112233445566regioneu-west-1

    Cloud scans a read-only scope

    Give Continuum Cloud a read-only AWS role or an Azure app registration with Reader, then choose the scope. The scan lands as a Vellum canvas with a stratum on every resource.

  2. continuum local · your network
    your networkZabbixNetBoxVeeamSNMP, in the ranges you allowcontinuum-local443 outno inboundblueprintr.ioOverviewZabbixAvailableVisible namedb-01snapshot 25 Sepnetwork sweepsw-core-01switchsw-acc-02switchups-01upskept 90 days

    Local dials out to Blueprintr

    Install the agent on a host of your own. It connects out to Blueprintr, sweeps the address ranges you allow over SNMP for Blueprintr to draw, and reads your on-premise systems for Link.

  3. continuum link · search
    payments-apiOverviewPagerDutysnapshot 25 Seppayments-apiPagerDuty· linkedpayments-api96% matchLink objectDatadogpayments-api p9588% matchLink objectServiceNow CMDBpayments-api81% matchLink object

    Link saves a timestamped snapshot

    Search every connected system at once and attach a match to a shape. Its stratum gains a tab holding a timestamped snapshot, which an editor refreshes when it needs updating.

Features

More about Continuum

  • Views of the same canvas

    Recolour a Continuum Cloud diagram by routing, security groups, estimated cost, IP addresses, public exposure, availability zone or tag coverage. The layout stays where it is.

  • Terraform-aware

    Give an AWS connection your Terraform remote state, from S3 or Terraform Cloud. A resource that drifted from what you declared is outlined in amber on the diagram.

  • Your own network, drawn

    Continuum Local sweeps the address ranges you allow over SNMP, and Blueprintr draws what it finds: devices by role, the LLDP and CDP links between them with the port at each end, sites from each device's location, and a Routing view of the BGP sessions between devices, with their AS numbers, iBGP or eBGP, and EVPN where the device reports it, and of their OSPF and IS-IS adjacencies.

  • 39 connectors, one search

    Alerting and on-call, observability, monitoring, uptime, ITSM, IPAM, backup and source control. One search reaches all of them, including the on-premise ten through Continuum Local.

FAQ

Questions about Continuum

What is the difference between Continuum Cloud, Local and Link?

Continuum Cloud scans AWS and Azure read-only and draws what it finds. Continuum Local is an agent inside your own network: it sweeps the network over SNMP so Blueprintr can draw it, and Link reads on-premise systems through it. Continuum Link attaches timestamped snapshots from 39 connected systems to shapes you already have, and never draws.

What access does Continuum Cloud need?

A read-only AWS role with an external ID, or an Azure app registration with the Reader role. Continuum Cloud only reads and never changes your cloud account.

Can I limit what a scan covers?

Yes. Scope a Continuum Cloud scan by account or subscription and region, then by VPC, subnet or resource group. A tag filter narrows it too, though resources with no tag data still come through.

Does Continuum Local draw our network?

Yes. Open a finished network sweep and choose Create Blueprint. Blueprintr draws it as a blueprint with a Physical view of the devices and the LLDP and CDP links between them, and a Routing view of the BGP sessions between devices, with their AS numbers, iBGP or eBGP, and EVPN where the device reports it, and of their OSPF and IS-IS adjacencies. Each drawn device gets a stratum, and a later sweep of the same ranges redraws the blueprint and marks what changed.

Can it reach systems inside our own network?

Yes, through Continuum Local, an agent you run inside it. It sweeps the address ranges you allow over SNMP v1, v2c or v3, and ten of the connectors are on-premise and reach your systems through it: SolarWinds Orion, Zabbix, PRTG Network Monitor, Checkmk, Icinga 2, ManageEngine OpManager, WhatsUp Gold, NetBox, Infoblox and Veeam Backup & Replication.

Where does each flavour run?

Continuum Cloud runs on Blueprintr's servers, which call the AWS and Azure APIs, and nothing of it runs in your network. Continuum Local runs on a host inside your network, on Linux, Windows Server, Docker or Kubernetes. It connects out over HTTPS on port 443 and accepts no inbound connections. Continuum Link runs on Blueprintr's servers, which reach 29 of its connectors over the internet. The on-premise ten go through Continuum Local.

Where are the credentials kept?

Continuum Cloud uses a read-only AWS role or an Azure app registration with Reader. Each Continuum Link connection has its own token or key, encrypted at rest and never returned to your browser, and CloudWatch reuses your Continuum Cloud AWS role. The Continuum Local agent keeps the SNMP credentials for your devices and the credentials of the on-premise ten, and Blueprintr never stores them.

Which plans include it?

Continuum Cloud is on Team and up. Continuum Local and Continuum Link are on Enterprise, and Local needs no licence of its own.

Blueprints drawn from AWS, Azure and your own network, with timestamped snapshots from your tools on their shapes.