Why Upgrade to TameFlare Pro? A Guide for Solo Developers and Small Teams

You've outgrown Starter. Here's how you know.

TameFlare's Starter tier is genuinely free - 3 gateways, 1,000 actions/month, all 8 connectors, credential vault, dashboard, and 30-day audit retention. Most solo developers start here and stay for weeks or months.

But there are clear signals that you need more:

You're hitting 1,000 actions before the month ends. A single GitHub PR agent run uses ~50 actions. If you're running agents daily, you'll hit the limit in 3 weeks.

You need to investigate something from 5 weeks ago. Starter keeps 30 days of audit history. If an incident happened 35 days ago, that data is gone.

You're managing more than 3 environments. Dev, staging, production - that's your 3 gateway limit. Add a second agent type and you're blocked.

Someone else touches your config. When policies change and you can't see who changed what or when, debugging gets painful.

What Pro ($29/mo) adds

90-day audit retention

Starter: 30 days. Pro: 90 days.

This matters more than it sounds. Compliance reviews, incident investigations, and quarterly security audits all need historical data. With 30 days, you're constantly racing against the clock to export logs before they expire. With 90 days, you have a full quarter of history available in the dashboard at all times.

Real scenario: Your agent made an unexpected Stripe charge 6 weeks ago. On Starter, that audit record is already purged. On Pro, you can trace the exact policy evaluation, see which rule matched, and determine whether it was a policy gap or an agent bug.

Policy versioning

Every policy change is tracked with git-style history. You can see:

What changed (diff view)

When it changed (timestamp)

The previous version (rollback target)

Why it matters: You update a policy to allow a new action type. Two days later, an agent starts making unexpected API calls. Without versioning, you're guessing what changed. With versioning, you see the exact diff and can roll back in one click.

This is especially valuable when multiple people manage the same gateway. No more Slack messages asking 'did anyone change the GitHub policy?'

Config export / import

Export your entire gateway configuration - connectors, access rules, blocked categories, notification settings - as a portable file. Import it into another gateway, another environment, or share it with a teammate.

Use cases:

Staging to production promotion. Configure and test in staging, then import the exact same config to production. No manual recreation.

Team onboarding. New team member? Import the team's standard gateway config instead of walking them through setup.

Backup. Export before making risky changes. If something breaks, import the backup.

Custom notification rules

Starter sends all notifications to the dashboard (and optionally Slack). Pro lets you filter:

Only notify on high-risk denials (not every read-only pass-through)

Route approval requests to Slack but denials to your incident channel

Suppress notifications for specific action types you've already reviewed

This turns TameFlare from 'noisy alerting tool' into 'signal-only governance layer.' The difference matters when you're running agents 24/7.

10 gateways, 10,000 actions/month

Starter: 3 gateways, 1,000 actions. Pro: 10 gateways, 10,000 actions.

The math for a small team (3-5 engineers):

3 environments (dev, staging, prod) = 3 gateways

2 agent types (code agent + ops agent) = 2 more gateways per env = 6 more

Total: 9 gateways, well within Pro's limit

Actions: 5 agents running ~100 actions/day = 500/day = ~15,000/month. Pro's 10,000 limit covers most small teams. If you're consistently above 10,000, you're likely a platform team and should look at Team ($79/mo) with 50,000 actions.

Webhook callbacks

Fire-and-forget HTTP callbacks on every policy decision. Pipe events to:

Your own logging infrastructure (Datadog, Grafana, ELK)

A Slack bot that formats alerts your way

An automation pipeline that reacts to specific decisions

A compliance system that needs real-time event feeds

Email support (48h response)

Starter: community support via GitHub. Pro: direct email support with 48-hour response time. When you're running agents in production and something isn't working, waiting for a community response isn't always an option.

The cost math

$29/month = $0.97/day.

If TameFlare Pro saves you one hour of debugging per month (tracing an incident through 90 days of audit history instead of recreating it, rolling back a bad policy instead of manually fixing it, importing a config instead of rebuilding it), it pays for itself at any engineering salary.

For a small team, the config export/import feature alone saves hours of setup time when onboarding new environments or team members.

How to upgrade

1. Log in to your dashboard at tameflare.com/dashboard
2. Go to Account > Subscription
3. Click Upgrade to Pro
4. Complete checkout via Stripe (annual billing saves ~17%)

Your limits increase immediately. Audit retention extends to 90 days (existing events within the window are preserved). All Pro features activate on your next page load.

Start free, upgrade when it matters

There's no trial period and no pressure. The Starter tier includes every core feature - proxy, connectors, vault, dashboard, audit. Pro adds operational maturity: longer history, version control, portability, and smarter notifications.

Create a free account and upgrade from the dashboard when you're ready.

*TameFlare is source-available under the Elastic License v2. The cloud gateway runs at proxy.tameflare.com on your machine. Read the docs for the full feature reference.*