Built for your production services
Gazebo holds the API keys to your production infrastructure. We take that seriously. Here's exactly how we protect your credentials, your agents, and your services.
Scoped agent identity with read/write controls
Every AI agent gets its own token — scoped to only the services you explicitly permit. You also control which HTTP methods each agent can use per service: give one agent read-only access to Stripe (GET only), give another write access (POST, PATCH). If an agent attempts an operation outside its permitted methods, the request is denied and you get an alert. Least-privilege access is the default, not an option.
Encrypted credential vault
Every API key and secret you store is encrypted with AES-256-GCM before being written to the database. The encryption key is stored separately from the data. Plaintext credential values are never logged, never returned to the client after submission, and never sent to our AI provider.
Approval gate — nothing runs without you
Gazebo generates a step-by-step execution plan for every workflow. That plan is shown to you in full before anything happens. API calls to your production services only execute after you explicitly click Approve. There is no way for a workflow to execute automatically or bypass this gate.
Full audit log
Every credential access is logged — which agent requested it, which service, and when. Every HTTP call made by an executed workflow is also recorded, including the method, URL, response status, and timestamp. You can review the complete history of what every agent and workflow did on your behalf at any time.
Authentication & session security
Passwords are hashed using PBKDF2-SHA512 with 100,000 iterations and a random salt — never stored in plaintext. Sessions use HTTP-only, server-side cookies that cannot be accessed by JavaScript. Magic link tokens are single-use and expire after 1 hour.
API and MCP access
Programmatic access via the REST API or MCP endpoint requires a Bearer token. Full-account tokens grant broad access; agent tokens are scoped to specific permitted services only. Both can be revoked at any time from your account settings. Every request is authenticated before any data is accessed or any action is taken.
SSRF and request-forgery protection
Gazebo blocks workflow executions that attempt to target private network addresses (RFC-1918 ranges: 10.x.x.x, 172.16–31.x.x, 192.168.x.x) and link-local addresses. This prevents workflows from being used to probe your internal infrastructure.
One-click revocation
Revoking an agent's access takes one click — no API key rotation required. The agent's token is invalidated immediately. Your underlying service credentials remain untouched. You can re-grant access anytime with a new scoped token.
Infrastructure
Gazebo is hosted on Replit's cloud infrastructure, built on Google Cloud Platform. All data is stored in a managed PostgreSQL database. Traffic between your browser and Gazebo is encrypted in transit via TLS 1.3.
Database backups run automatically. The credential vault encryption key is stored separately from the credential data and is never rotated without a migration plan.
Rate limiting is applied to workflow creation and agent credential requests to prevent abuse.
Vulnerability disclosure
If you discover a security vulnerability in Gazebo, please report it responsibly. Email us at [email protected] with a description of the issue and steps to reproduce it. We aim to acknowledge reports within 48 hours and resolve confirmed vulnerabilities within 14 days.
Please do not publicly disclose vulnerabilities before we've had a chance to investigate and fix them. We appreciate responsible disclosure and will credit researchers who help us improve security.
Worried a config file already has raw credentials in it?
Free scanner