Hypertune
  • Introduction
  • Getting Started
    • Set up Hypertune
    • Next.js (App Router) quickstart
    • Next.js (Pages Router) quickstart
    • React quickstart
    • Remix quickstart
    • Gatsby quickstart
    • Vue quickstart
    • Nuxt quickstart
    • Node.js quickstart
    • React Native quickstart
    • JavaScript quickstart
    • Python quickstart
    • Rust quickstart
    • Go quickstart
    • Web quickstart
    • GraphQL quickstart
  • Example apps
    • Next.js and Vercel example app
  • Concepts
    • Architecture
    • Project
    • Schema
    • Flag lifecycle
    • Logic
    • Variables
    • Splits
    • A/B tests
    • Staged rollouts
    • Multivariate tests
    • Machine learning loops
    • Events
    • Funnels
    • Hypertune Edge
    • Reduction
    • SDKs
    • GraphQL API
    • Git-style version control
    • App configuration
  • Use Cases
    • Feature flags and A/B testing
    • Landing page optimization
    • In-app content management
    • Pricing plan management
    • Permissions, rules and limits
    • Optimizing magic numbers
    • Backend configuration
    • Product analytics
  • Integrations
    • Vercel Edge Config integration
    • Google Analytics integration
    • Segment integration
    • Webhooks
      • Creating webhooks
      • Handling webhooks
  • SDK Reference
    • Installation
    • Type-safe client generation
    • Initialization
    • Build-time logic snapshot
    • Hard-coded fallbacks
    • Local-only, offline mode
    • Hydrate from your own server
    • Wait for server initialization
    • Provide targeting attributes
    • Local, synchronous evaluation
    • Remote logging
    • Getting flag updates
    • Serverless environments
    • Vercel Edge Config
    • Custom logging
    • Shutting down
Powered by GitBook
On this page
  1. Concepts

Project

PreviousArchitectureNextSchema

Last updated 10 months ago

Your Hypertune project contains your:

  • which defines your:

    • Flags, i.e. their names and types

    • Input types for flag targeting logic, e.g. User, Organization, Environment

    • , e.g. SignUpEvent, PurchaseEvent with payload fields, e.g. revenueAmount

    • For flag targeting

    • Can be embedded anywhere in your flag targeting logic and reused across multiple flags

    • Can be embedded anywhere in your flag targeting logic and reused across multiple flags

    • 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 for your project.

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:

One of the

The

Schema
Event types
Logic
A/B tests
Machine learning loops
Funnels
Git-style version history
SDKs
GraphQL API