Federation & Import

Import capabilities from external catalogs like Backstage, ServiceNow CMDB, or any JSON/YAML catalog endpoint.

Why Federation?

Most organizations have APIs, services, and tools scattered across multiple catalogs — Backstage for developer portal, ServiceNow CMDB for ITSM, internal wikis, spreadsheets, and tribal knowledge. Federation lets ATLAS pull from all these sources into one unified, governed catalog. Imported capabilities retain their source attribution so you always know where they came from, and ATLAS overlays governance (risk, ownership, classification) that the source systems don't provide.

Backstage

Import from a Backstage software catalog. Provide the /entities endpoint URL.

Format

Backstage Catalog API

Example URL

https://backstage.example.com/api/catalog/entities

ServiceNow CMDB

Import from a ServiceNow CMDB table API. Requires instance URL and table name.

Format

ServiceNow REST API

Example URL

https://instance.service-now.com/api/now/table/cmdb_ci_service

Custom JSON/YAML

Import from any endpoint that returns an array of capability records.

Format

JSON array

Example URL

https://api.example.com/services.json

Import from External Catalog

How Federation Works

Connect Source

Point ATLAS at an external catalog URL (Backstage, CMDB, custom)

Discover & Map

ATLAS probes the endpoint and maps records to its capability schema

Import as Draft

Records are imported with source='import' and status='draft' for review

Govern & Route

Apply governance metadata, approve, and auto-route via agentgateway