Hypertune
Search
K

Project

Your Hypertune project contains your:
  • Schema which defines your:
    • Feature flags, i.e. their names and types
    • Input types for flag targeting logic, e.g. User, Organization, Environment
  • Logic
    • For flag targeting
  • A/B tests
    • Can be "dropped" anywhere in your flag targeting logic and reused across multiple flags
    • Can be "dropped" anywhere in your flag targeting logic and reused across multiple flags
    • E.g. Sign up, Purchase, etc
    • Can contain "features", e.g. revenueAmount
  • Funnels
    • To see drop-off rates between different event types
    • To compare conversion rates across different arms of an A/B test or machine learning loop
All of these are saved together as a single commit in the Git version history for your project which is hosted by Hypertune.
A new commit is created on your main branch any time you save new changes.
Hypertune uses the latest commit on your main branch when you consume your flags.
You consume your flags via: