Solo
Connect the first apps your agents need and keep token custody in infrastructure you control.
- Up to 3 integrations
- 100 connection events / mo
- Community Discord
- Customer-controlled credential layer
- Basic connection visibility
CybrLink helps users connect apps, lets teams govern agent access, and keeps credential custody under your control.
Connect the first apps your agents need and keep token custody in infrastructure you control.
For teams shipping agents to real users with scoped app access and reviewable connections.
For controlled environments where CybrLink and provider credentials run in your cloud.
| Feature | Solo | Team | Self-hosted Enterprise |
|---|---|---|---|
| Integrations | 3 | Unlimited | Unlimited |
| Connection events / mo | 100 | 100K | Unlimited |
| Customer-controlled credential layer | |||
| End-user identity | — | ||
| Per-user scope control | — | ||
| Custom-branded Connect UI | — | ||
| Webhook connection events | — | ||
| Private cloud / VPC deploy | — | — | |
| SAML SSO + SCIM | — | — | |
| Security review support | — | — | |
| Support | Community | Slack channel | Named architect |
Your controlled credential layer is the credential-bearing system. CybrLink creates and manages the connect flow, but durable OAuth access and refresh tokens belong in infrastructure you control.
CybrLink needs enough connection metadata to show users what is linked. Provider credentials and long-lived OAuth tokens should stay inside your controlled credential layer.
Your credential layer remains the source of truth for provider credentials. CybrLink should be treated as the connect and management layer around that token store.
It means the credential-bearing OAuth system is a Nango instance you deploy or control. CybrLink wraps that with catalog, connect UX, user scoping, and agent-facing access patterns.