Workspace
Integrations — Connect Your Infrastructure Ecosystem
Bring information from external platforms into SPECTRALE to expand your understanding of the systems behind your software architecture.
Bring authorized systems into the project.
Bring information from external platforms into SPECTRALE to expand your understanding of the systems behind your software architecture.
A detected service in Discovery is not the same thing as a connection. Discovery can name a dependency. A connection is a separate authorization that you start yourself.
Explore the catalog
Open Integrations and browse the providers SPECTRALE can connect. Each entry shows the connection methods that are actually supported for that provider, and the current connection status.
Connect your own account
Choose Connect and follow the method that provider supports.
Where a provider application or OAuth client is configured, SPECTRALE starts that provider's own authorization flow. GitHub uses its app installation flow when the SPECTRALE GitHub app is configured. Supabase uses OAuth when that client is configured.
Cloudflare, DigitalOcean, Railway, and GitLab can be connected with an API token that you supply. SPECTRALE verifies the token with the provider and stores it for that connection only.
Other catalog providers remain in setup until a supported authorization path exists. Connect explains what is missing. It does not mark the provider as connected.
You connect your own account. SPECTRALE does not substitute its own infrastructure credentials for a customer's provider credentials. Application secrets are not used as a stand-in for an authorization you have not granted.
Guardian-assisted setup
When a provider needs setup, Connect can open Guardian with the current connection limit and the next step. Credentials stay in the connection dialog, not in the chat.
Resting on the control does not start the conversation. Guardian does not receive the token or open an API that SPECTRALE cannot call.
Custom providers
You can add a custom provider with a name and a URL. That entry is a catalog record for the organization. It is not a connection, and SPECTRALE does not crawl or call that URL. Connect stays unavailable for a custom entry until a supported authorization path exists.
What a connection can read
Where the provider API allows it, you can choose resource categories such as accounts, projects, repositories, applications, or zones, and then confirm an import.
The import reads metadata the provider returns. It does not change resources at the provider. A catalog entry does not mean every API that provider offers can be imported, and it does not mean every listed provider already supports automated ingestion.
Supported connections can be tested, synchronized again, or disconnected. Disconnecting removes SPECTRALE's use of that authorization. Imported resources can be deleted from the project without implying that the provider itself was changed.
Imported metadata can inform the project record that Discovery and Guardian read. Discovery remains a separate view of architecture evidence.
Permission boundaries
Connection, import, test, and disconnect require permission to change the project. The scope of a connection is the access you grant at the provider. SPECTRALE does not widen that grant.
Availability
Integrations is included in Architect.
Important to know
Important. Provider support varies. A provider in the catalog is not a promise that every resource or API from that provider can be imported.