# Trevo

> Trevo is an experimentation platform that finds testable opportunities in a product site and
> codebase, writes approved variants as pull requests, measures outcomes with sequential
> statistics, and prepares cleanup pull requests after a decision.

Trevo is built for product, growth, and engineering teams whose main experiment bottleneck is
implementation. It writes only to trevo/* branches; a customer's own review, CI, and branch
protection decide what merges.

## Start here

- [Homepage](https://trevosdk.com/): Product overview, workflow, security, and pricing.
- [Product guide](https://trevosdk.com/guide): Seven chapters covering setup, proposals, pull
  requests, results, and team controls.
- [How Trevo decides](https://trevosdk.com/how-trevo-decides): mSPRT statistics, sample-ratio
  mismatch checks, guardrails, and the human-approval boundary.
- [About Trevo](https://trevosdk.com/about): Why the product exists and how Trevo publishes
  technical and comparison content.
- [Blog](https://trevosdk.com/blog): A/B testing, growth engineering, and product-engineering
  articles.
- [Comparisons](https://trevosdk.com/vs): Dated comparisons with links to each vendor's official
  documentation.
- [Documentation](https://docs.trevosdk.com/): SDK and integration reference.

## Product and use-case pages

- [Trevo for growth teams](https://trevosdk.com/growth)
- [Trevo for startups](https://trevosdk.com/startups)
- [Pricing experiments](https://trevosdk.com/use-cases/pricing)
- [Onboarding experiments](https://trevosdk.com/use-cases/onboarding)
- [AI product experiments](https://trevosdk.com/use-cases/ai-products)
- [Marketplace experiments](https://trevosdk.com/use-cases/marketplaces)
- [GitHub integration](https://trevosdk.com/integrations/github)
- [PostHog integration](https://trevosdk.com/integrations/posthog)

## Canonical facts

- Website: https://trevosdk.com
- Application: https://app.trevosdk.com
- Documentation: https://docs.trevosdk.com
- Experiments are proposed from site, repository, funnel, and prior-experiment context.
- Approved variants are written on trevo/* branches and returned as pull requests.
- Trevo never merges a customer's pull request.
- Variant assignment runs through Trevo SDKs in the customer's own code.
- Experiment analysis uses mixture Sequential Probability Ratio Testing (mSPRT).
- A completed decision produces a pull request that keeps the winner or removes the rejected
  variant.

For security, pricing, or product questions not answered publicly, contact hello@trevosdk.com.