System families
Potential adapters span source control, cloud, databases, CRM, ticketing, communications, observability, and security tools.
Connectors
Connect systems.
Keep boundaries clear.
Plan explicit operations for external systems so access, credentials, permissions, policy authorization, and execution never collapse into one assumption.
Product direction · In active development
01
Operations, not ambient access
Connector contracts are intended to describe supported operations, inputs, outputs, side effects, idempotency needs, and policy-relevant metadata.
02
Separate every boundary
Installing a connector, enabling it, assigning credentials, granting permission, and authorizing a request are distinct stages.
Clear review surface
Operators should be able to inspect the intended resource and expected side effect before approval.
03
Governed execution path
LNSAT provides the proposed authorization and evidence foundation; connector coverage and contracts are still being developed.
No implied integration
This page does not claim any connector is currently shipped or configured.
An ecosystem in the making
Bring your systems.
Illustrative connector targets from the product designs. Availability and permissions depend on each future adapter.
GitHub
Developer tools
Planned targetGitLab
Developer tools
Planned targetPostgreSQL
Data
Planned targetGoogle Drive
Productivity
Planned targetSlack
Communication
Planned targetNotion
Productivity
Planned targetLinear
Developer tools
Planned targetAmazon AWS
Infrastructure
Planned targetOpenAI
AI & models
Planned targetMicrosoft 365
Productivity
Planned targetDatadog
Infrastructure
Planned targetDiscord
Communication
Planned target12 planned targets
