One workspace boundary
Keys, members, destinations, support cases, and audit events remain scoped to the active workspace.
API proxy for SaaS
ThrottleProxy gives SaaS workspaces a shared place for proxy keys, approved destinations, rate policy, queue decisions, and privacy-safe lifecycle evidence. Start with one integration and keep provider authentication separate.
Practical boundaries
Keys, members, destinations, support cases, and audit events remain scoped to the active workspace.
Begin with an exact public host and non-sensitive test traffic before adding more destinations.
Move rate and resource controls out of scattered application processes.
Separate technical setup, billing, viewing, and ownership responsibilities.
Use sanitized lifecycle evidence and reviewed guides rather than raw upstream bodies or secrets.
Open a workspace-scoped support case with bounded, customer-visible context.
No. Start with a narrow integration whose risk, traffic shape, and operational value justify a shared control layer.
No. ThrottleProxy can shape local traffic, but the upstream provider remains authoritative.
No. Growth and Scale support authenticated checkout, while Starter and Enterprise can still use a reviewed activation path.
Use one workspace key, one exact public host, and non-sensitive test traffic.