Billing

Pullfrog separates its platform plan from model usage. Pro covers private-organization runs; Pullfrog Router funds model tokens at provider cost. Both are managed from the organization console.

​

The plan

Personal accounts and public repositories run free. Private repositories in GitHub organizations require Pro once the organization trial ends.

• Individuals and open source — free, no card. Personal repos and any public repo can run Pullfrog.
• Pro for organizations is rolling out at $30/month per GitHub organization for private-repo use. Public repositories inside an organization are always free. Until Pro is enabled, organization runs continue without a subscription.

The only usage-based cost is the model tokens themselves, and you pay those at cost: bring your own provider key (free), or use Pullfrog Router at raw provider pricing with no markup.

​

Starting Pro and adding a card

When Pro is available for an organization, open pullfrog.com/console/<org> and click Upgrade in the Plan card. Stripe Checkout shows the first charge date, requires acceptance of Pullfrog’s Terms, starts Pro, preserves any remaining free-trial days, and saves the payment method used for the subscription. Pro costs $30/month per GitHub organization. A card previously added for Router never enrolls the organization in Pro automatically. To fund Pullfrog Router without starting Pro, use Add card in the Top up row under Model usage. This saves a payment method through Stripe without starting a subscription. Once a card is attached, Plan and payment shows a Payment method row with the card brand and last four digits, or Stripe Link when the method is a Link account rather than a card. Use Manage billing (or Manage plan on a Pro organization) to change cards and the billing email through the Stripe Customer Portal. The Billing history card below it holds both ledgers: the Invoices tab lists finalized Pro and legacy pay-as-you-go invoices (draft, voided, and zero-total invoices are omitted), and the Router credit tab lists Router top-ups and credit grants.

​

Pullfrog Router

Pullfrog Router is a managed model backend that fronts every major LLM provider through a single billing account. With the Router, you don’t need to manage provider keys at all — Pullfrog mints a short-lived proxy key for each run and bills model usage at raw OpenRouter cost (no markup). In the Model usage section of the Billing card, switch between two modes at any time:

• BYOK (recommended) — Bring your own provider keys, or an existing Claude Code or Codex subscription. You pay the provider directly, at their prices. See BYOK for setup.
• Pullfrog Router — Pullfrog handles model access. The agent picks up the right credentials at dispatch; you only see the wallet balance on the dashboard.

The mode is account-wide and can be flipped at any time. If your account already holds a Router credit grant, the balance shows on the Router tab and spends automatically once you’re in Router mode.

​

Auto-reload

Auto-reload is opt-in. When enabled, Pullfrog tops up your Router balance automatically whenever it drops below your configured threshold, so you don’t have to babysit credits between runs. Two knobs:

• Auto-reload threshold — the balance that triggers a reload (e.g. $10). When the wallet drops below this, Pullfrog charges your card and tops up.
• Auto-reload amount — how much to add each time (e.g. $50). The full amount is credited to the wallet; Stripe’s processing fee is grossed up on the charge so your wallet sees the net.

If auto-reload is off and the wallet runs dry, runs that would have used the Router fail with a clear “add credit” message in the PR comment, and the agent surfaces the dashboard link directly.

​

Monthly spend limit

Organization owners can configure a per-account ceiling on how much Pullfrog Router will auto-reload in any UTC calendar month. The cap resets at 00:00 UTC on the 1st. Useful as a safety net against runaway agent loops, stuck workflows, or a leaked PR trigger spending more than you meant to. The cap is optional — running without one is the default. Two modes:

• Hard cap — once the next auto-reload would push past the limit, that reload is refused. Your wallet keeps draining on subsequent runs (you still have access to the credit you’ve already paid for), but new top-ups are blocked until you raise the cap or the next UTC month starts.
• Alert-only — auto-reloads keep flowing; we email the account’s billing contact when a reload pushes you over the limit. Treat it as a soft tripwire.

Set the cap from the Monthly spend limit field in the Model usage section, alongside auto-reload amount and threshold. Leave the field empty for no limit. The field appears once a card is on file and auto-reload is on. Once a number is in the field, a Behavior at limit toggle appears for choosing hard cap vs alert only. The cap can also be set via PATCH /api/account/<owner>/billing/settings with routerMonthlyLimitUsd (number in dollars, or null to clear) and routerLimitMode (hard_cap or alert_only). Manual top-ups at /billing-top-up/<owner> are unrelated to the cap — you’re clicking through Stripe Checkout yourself, so we treat them as deliberate spend and never block them.

​

Free models

A handful of models cost nothing to run:

• Big Pickle (OpenCode)

Pick it in the model selector and you skip both Router credit usage and BYOK setup entirely.

​

Open source program

Open source maintainers can apply for free access to premium models via Pullfrog Router. If you maintain a public repository, reach out to support@pullfrog.com with:

• A link to your repository
• A brief description of how you’d use Pullfrog

We review applications on a rolling basis.

​

Enterprise

Pro covers most teams without a conversation. An Enterprise plan is on the way for multi-team organizations, with GitHub Enterprise support, SSO, audit logs, RBAC, SOC 2 / HIPAA, SLAs and dedicated support, committed spend, and on-prem / private cloud. To talk through requirements or ask about early access, contact sales@pullfrog.com.