Trevo connects ad spend, product behavior, and your codebase to see where growth is stuck. Then it turns the strongest opportunity into a campaign insight, lifecycle email experiment, code experiment, or new product feature your team can actually launch.
Product-code changes arrive as PRs · your team merges · no card
∞ One connected growth loop
Trevo connects what customers saw, what they did, and where they stopped—then recommends a measurable next move.
Trevo joins Google Ads or Meta spend to attributed visitors who complete the activation funnel you choose, including cost per activated user.
Trevo finds the missed milestone, targets the people affected, and measures the product outcome—not just whether they opened the message.
► Watch the product loop
A guided replay from Trevo’s seeded Terra & Twine demo workspace. The workflow, pull requests, and product states match Trevo; the store and performance data are illustrative.
Hover to pause · click any stage to jump.
Follow the same states you can explore in the interactive demo workspace.
σ Statistics
Trevo keeps the original experience as the control, compares the same outcome for both groups, and waits for evidence instead of calling a lucky day a win. You can check the result whenever you want without making a false winner more likely.
For the stats reviewer: binary outcomes use mSPRT at α = 0.05. Tests with multiple variants use a Bonferroni-adjusted threshold. The interval shown here is descriptive; the always-valid p-value is the stopping rule.
Example numbers, not a customer claim. Trevo calls significance from the mSPRT p-value, not from whether the display interval crosses zero.
• More leverage, no mystery
Trevo works across growth without becoming a black box. Every action has a visible boundary and a familiar approval path.
Trevo reads the configured default branch, writes changes only to trevo/* branches, and opens a normal pull request. CI, CODEOWNERS, and branch protection stay in the review path.
$ Pricing
Every organization starts with connected product context and five real experiment PRs, shipped end to end with no credit card required. Paid plans are priced on the users you track.
Connect the product and ship your first measured changes.
Past 25k users or out of credits? Move to Starter — your five free experiments come with you.
Start freeIncludes 25k monthly users, then $10 per 1k users up to 100k.
Includes 100k monthly users, then $10 per 1k users up to 500k.
Over 500k monthly users. Custom capacity, operating controls, and support for multi-product organizations.
? Questions & trust
Short, honest answers on what Trevo sees, what it keeps, and what stays yours. The whole picture is in the guide.
No. Connecting a repository does not transfer ownership of your code to Trevo. Trevo does not keep a source-code clone: scan and pull-request jobs use a temporary workspace that is removed when the job finishes. Trevo keeps a derived structural snapshot — routes, components, server-side logic, file paths, and short descriptions — inside your workspace so it can ground proposals and changes. Disconnecting removes that snapshot from the active product.
The GitHub App can read the repositories you select and create branches and pull requests in them. Trevo reads the configured default branch and its product workflow writes changes only to trevo/* branches; it does not merge or deploy them. Your CI, CODEOWNERS, and branch protection still decide what can reach the default branch. You can revoke the GitHub App at any time.
No. Repository content and experiment metrics are not used to train models. Trevo uses model providers to process the context needed for a scan, proposal, or requested code change, and we can share the current provider list on request.
Trevo never deploys and never merges. It opens a pull request; your engineers review and merge it exactly like any other PR, through your existing CI and checks. Variant assignment then runs inside your own code from a synced config snapshot — there is no blocking third-party script in your critical path. Starting an experiment only flips traffic on code you already merged, and if you do not like a variant you simply close the PR and nothing changes.
Disconnecting stops Trevo from using that repository connection and removes its structural snapshots from the active workspace. Uninstalling or revoking the GitHub App removes the GitHub-granted access. Deleting a workspace revokes its SDK and API keys, removes its active workspace data, and deletes stored payload objects; append-only audit records remain as the security history.
∞ Start the loop
Connect your product, acquisition data, and codebase. Trevo surfaces the constraint, recommends a measurable move, and helps your team ship it through the right surface.
Start free · no card · keep human approval · or talk to an engineer