Integrations
Connect a system. Then decide what Foundry may do with it.
Connection and authority are two separate grants. Foundry reading your repository is not Foundry merging to your main branch, and it never quietly becomes that.
Integrations
Foundry works where your product already lives.
Connecting a system lets Foundry read it. What Foundry may then do with it is a separate, explicit grant — read access to a repository is not permission to merge.
Figma
Design context
AvailableGitHub
Code and repositories
AvailableSlack
Progress and approvals
AvailableAzure
Infrastructure and deployment
AvailableGitLab
AvailableCode and merge requests
Grants: READ · CREATE · MODIFY
Azure DevOps
PlannedRepos, boards and pipelines
Grants: READ · CREATE
Microsoft Teams
PlannedProgress and approvals
Grants: READ · CREATE
Jira
PlannedWork item sync
Grants: READ · CREATE · MODIFY
Linear
PlannedWork item sync
Grants: READ · CREATE · MODIFY
Product analytics
Coming soonWhat customers actually did
Grants: READ
Error monitoring
Coming soonProduction errors, routed back
Grants: READ
Transactional and campaign sending
Grants: READ · CREATE
CRM
Coming soonCustomer records as context
Grants: READ
Support desk
Coming soonSupport themes as product input
Grants: READ
Availability describes what Foundry supports, not what is connected to your workspace. Nothing is connected until you connect it. Marks are Foundry’s own — no third-party branding is used.
The authority model
Access is not authority.
A DevOps agent with cloud access does not thereby have permission to provision unlimited infrastructure. A Growth agent with your social credentials does not thereby have permission to publish. Every permission is explicit, and enforced in the backend — not asked for politely in a prompt.
Foundry can
Done without asking. Nothing here reaches a customer or spends your money.
Research and discovery
Requirements and user stories
Design drafts
Writing code
Running tests
Fixing low-risk bugs
Writing documentation
Foundry prepares and waits
The work is ready and the recommendation is stated. Nothing proceeds until you decide.
Major scope changes
Architecture changes
Production deployments
Destructive database migrations
Purchasing infrastructure
Connecting sensitive systems
External marketing publication
Material budget changes
Reserved for you
No agent holds these at any permission level, and none can grant them to itself.
Granting or widening agent permissions
Deleting production data
Legal and contractual commitments
Removing a human approver
Start with one product
Tell Foundry what your business needs.
Create a workspace, describe the product, and watch the team pick it up. You approve what matters; Foundry handles the rest.