Self-driving pricing
Contents
PostHog Self-driving is priced on usage. You pay for the work agents do on your behalf: watching the sources you turn on, running scouts, researching reports, and, if you turn them on, opening pull requests.
Self-driving is charged in AI credits, the same unit other AI features in PostHog use. 1 AI credit = $0.01.
The number of credits each piece of work uses varies with how much effort it takes. A quick check uses few credits, and a deep investigation uses more.
Your first month
Your first month of Self-driving comes with 1,000 AI credits, worth $10, so you can see what the agents find in your product before you pay anything. During your first month, Self-driving creates up to 5 reports and runs up to 3 scouts. After that, there's no recurring free tier. You pay for what you use.
How spend builds up
Knowing where spend comes from tells you which settings shape it.
- Sources: Each source you turn on sends signals to Self-driving. You pay for processing and grouping those signals, and for researching the reports they form.
- Scout runs: Each scheduled scout run costs money, whether it finds something or not. A scout's schedule affects its spend more than what it finds.
- Pull requests: Pull requests are off by default. If you turn them on, writing a pull request for an actionable report costs money.
Track your spend
Self-driving shows your spend in these places:
- Usage table: An overview of spend per source type and across your scouts in the current billing period. Find it in the Settings tab in Self-driving.
- Sources: The Sources tab in Self-driving shows each source's spend in the current billing period.
- Scouts: The Scouts tab in Self-driving shows each scout's average cost per run in the scout list.
Self-driving spend also appears in your usage alongside the rest of your PostHog spend, on the billing overview and billing usage pages.
Usage data may take up to 24 hours to appear on the billing overview and billing usage pages.
Understand and optimize your usage
There are two ways to understand and optimize your Self-driving usage:
- Ask your agent to analyze your usage and recommend changes. This is the easiest way.
- Make changes manually to your sources, scouts, and other settings.
Ask your agent
Ask your agent to run the managing-self-driving-spend skill through the PostHog MCP, with a prompt like "Which sources and scouts drive my Self-driving usage?" or "How can I get more out of my Self-driving setup?"
The skill:
- Breaks your spend down by source, scout, and day
- Compares each source and scout's spend with how many of its reports got resolved
- Recommends changes ranked by impact, with what each one saves and what you give up
- Applies a change only after you confirm it
Make changes manually
Sources
Your sources decide which reports get researched, so start here. Turn off a source to stop Self-driving from watching it. Reports that already exist stay in your inbox.
Before you turn off a whole source, check whether one part of it drives the spend. Some sources let you turn down part of the signals they send:
| Source | What you can turn down |
|---|---|
| Error Tracking | Turn new, reopened, and spiking issues off separately. |
| Replay Vision | Stop a scanner from sending findings to your inbox while it keeps scanning, lower the share of recordings it scans, or turn it off. |
| Linear | Choose which teams' issues Self-driving watches. |
Other sources, such as support tickets, have no setting that selects part of the source. Keep them, turn them off, or steer them.
Scouts
- Pause a scout: Stops its scheduled runs. Its past reports stay in your inbox.
- Run a scout less often: Spend falls with the number of runs. Going from hourly to every 6 hours cuts that scout's spend by about five sixths.
A scout that rarely creates reports can still be useful if it keeps existing reports up to date. Check what it edits before you pause it.
Steering instructions
Steering instructions tell scouts and research agents what to focus on and what to skip, for example "Skip support tickets that are low-priority questions about billing." Some sources also take their own guidance about what to skip, but not every source supports it yet.
Steering changes what agents spend effort on, not how much work arrives, so its effect on spend is hard to predict. Check your spend again after two weeks.
Pull requests
Pull requests are optional and off by default. Reports land in your inbox either way.
- PR generation: Turn on automatic pull requests for actionable reports.
- Priority threshold: Set the lowest report priority that opens a pull request automatically. Lower-priority fixes then need a manual start. You can also set your own threshold under Your overrides. The priorities, from highest to lowest, are P0 – Critical, P1 – High, P2 – Medium, P3 – Low, and P4 – Minimal.
Limits
| Limit | How it works |
|---|---|
| Billing limit | A monthly cap on Self-driving spend. PostHog sets a default $150 billing limit, which you can raise, lower, or remove on the billing settings page. |
| Daily report limit | Caps how many new reports appear each day, in your project's timezone. It saves money on days with spikes. Set it in the Settings tab in Self-driving. |
When you reach either limit, new signals from your sources are dropped, scheduled scout runs are skipped, and research pauses. The billing limit resets at the next billing period, and the daily report limit resets at midnight.
Limits drop new signals instead of queueing them. Issues found after you reach a limit never reach your inbox, even after the limit resets.