Platform Overview

Supaship is a feature flag and experimentation platform that helps teams release features safely, control rollouts, and make data-driven decisions.

Instead of deploying code for every change, Supaship allows you to dynamically control application behavior through feature flags. Teams can gradually roll out features, run experiments, and instantly disable changes if something goes wrong.

Supaship is designed to be fast, reliable, and easy to integrate with modern applications.

Core Concepts

At the top, a workspace is your team boundary. It controls membership, roles, and shared ownership. Inside it, projects represent real product surfaces such as a web app, API, or internal console. Inside each project, environments isolate release stages (development, staging, production). Finally, feature flags control runtime behavior of your application within each environment.

How evaluation works at runtime

When your app asks for a feature flag, Supaship evaluates three things together: the flag configuration, rules in the selected environment, and the context you send (for example userId, plan, appVersion etc.).


const result = await client.getFeature('new-checkout', {
  context: {
    userId: '123',
    plan: 'premium',
    appVersion: '1.0.0',
  },
})

This is why environment discipline matters: rules in development never affect production unless you explicitly configure them there.

Targeting and Rollouts

Targeting decides who gets what. Supaship allows precise control over feature releases.

You can:

Roll out features to a percentage of users
Target specific user attributes
Enable features for specific segments or environments

A common rollout pattern is: start with internal users, expand to a small percentage, then gradually ramp to full traffic while observing product and reliability metrics.

This pattern keeps blast radius small and gives you confidence before broad exposure.

Edge Delivery

Supaship delivers flag configurations through a global edge network to ensure low latency and high availability.

Sensitive context properties can be hashed before being sent to the edge network, helping protect user data while still enabling targeted rollouts.

Keys and access model

SDK keys are project-scoped and environment-aware. Use client keys in frontend apps and server keys in backend services. This separation keeps integration practical while preserving security boundaries.

At the team level, owners manage membership and policy, while members operate flags and environments inside project scope.