The fastest path. Sign up, get an API key, point your tool at the gateway. No infrastructure to manage.
Getting started
Create an organization
After signing in, create a new organization. This is where your team, API keys, policies, and audit log live.
Create an API key
Navigate to Settings > API Keys and click Create Key. Give it a name that identifies where it will be used (e.g., cursor-laptop, ci-pipeline). Copy the key immediately — it is shown once.
Configure your AI tool
Set the API base URL in your AI tool to:https://gateway.takumo.io/v1
Set the API key
export TAKUMO_API_KEY="tk_live_your_api_key_here"
.env file:TAKUMO_API_KEY=tk_live_your_api_key_here
Start coding
Secrets are now protected. Every request through the gateway is scanned, tokenized, and logged in the audit trail.
Gateway URL
All requests go through a single endpoint:
https://gateway.takumo.io/v1
What you get
| Capability | Details |
|---|
| Secret detection | All supported patterns are active by default |
| Audit log | Every request is logged with detection results |
| Rate limiting | Per-organization limits based on your plan |
| Policy enforcement | Configure custom rules in the dashboard |
| Zero infrastructure | Takumo manages the gateway, coordinator, database, and monitoring |
Verifying it works
After configuring your tool, send a test request that includes a fake secret:
curl https://gateway.takumo.io/v1/tokenize \
-H "Authorization: Bearer $TAKUMO_API_KEY" \
-H "Content-Type: application/json" \
-d '{"content": "const key = \"AKIAIOSFODNN7EXAMPLE\"", "filename": "test.ts"}'
SaaS is the right choice for most teams. You get the same protection without managing infrastructure. On-prem is for organizations with strict data residency requirements.
