Eight kinds of tools
One hub, one scoped connector per tool
Requests go out and results come back along a connector that can only do what that integration was granted. Hover over or tap a category to follow it.
system
Team chat
Start, approve and inspect tasks from your team's chat, such as Slack.
Agreed channels only
Code repositories
Repository access for build, review and release workflows.
Changes proposed for review
Databases and data stores
Scoped reads and writes against operational data.
Writes wait for approval
Browser automation
Actions in web tools that have no API, behind approval gates.
Every submit waits for approval
Files and documents
Read, generate and hand back documents and other files.
Agreed folders only
Webhooks and events
Inbound triggers from other services, and outbound event delivery.
Verified senders only
Schedules
Daily checks and weekly reports that start on time without being asked.
Sensitive steps still wait
Internal and custom APIs
Direct integration with internal services and vendor endpoints.
One credential per endpoint
Access
How access is granted
Integration is a security decision before it is an engineering one. Credentials are scoped to the narrowest capability that completes the task.
- 1
One credential per integration
Least-privilege credentials for each integration, never shared account keys.
- 2
Secrets stay out of context
Credentials are stored outside agent context and never echoed into transcripts.
- 3
Every call is logged
Each tool call is recorded with the agent that made it, its scope and its outcome.
- 4
Visible actions wait
Destructive or externally visible actions are gated on the workflow owner's approval.
- 5
Revocable one at a time
Access can be withdrawn per integration without taking the system down.
Your stack
Tell us which tools the work lives in.
List the systems involved, including internal ones with no public API. We will say how each would be connected, what it would be allowed to do and what would wait for approval.