Offboarding & Data

How to stop using TameFlare and restore your agents to direct API access.

Step 1: Stop proxying agents

Remove the tf run wrapper - run your process directly:

# Before (with TameFlare)
npx @tameflare/cli run --name "Bot" python my_agent.py
 
# After (without TameFlare)
python my_agent.py

You'll need to provide API keys directly to your process again (they were in TameFlare's credential vault).

Warning
The credential vault is encrypted. There is no way to extract plaintext credentials. You will need to generate new API keys from the original services (GitHub, Stripe, etc.) and configure them directly in your process environment.

Step 2: Export your data

Before closing your account, export what you need:

  • Audit log - go to Audit Log → Export CSV in the dashboard
  • Configuration - go to Settings → Export Configuration to download policies and agents as JSON

Step 3: Delete your account

Contact support@tameflare.com to request account deletion. We will delete all your data within 30 days, including:

  • User accounts and sessions
  • Gateway configurations and connector settings
  • Policies and access rules
  • Audit events and traffic logs
  • Encrypted credentials (vault)

Vendor lock-in assessment

| Component | Lock-in risk | Details | |---|---|---| | Proxy mode | Very low | Agents use standard HTTP_PROXY/HTTPS_PROXY env vars. Remove the proxy, agents connect directly. Zero code changes. | | Policies | Low | Exportable as JSON. Concepts (conditions, decisions, scoping) are standard. | | Credential vault | Low | Credentials are encrypted. You can't extract them, but you can regenerate API keys from original services. | | Audit data | Low | Exportable as CSV. Standard fields (timestamp, event type, actor, details). |

Next steps

  • Support - get help with offboarding