tier·dev
git-integrated feature flags for open-source + saas tiers
tier·dev is for products that ship twice from one codebase: an open-source version and a paid saas version. Instead of a private fork or a long-lived enterprise branch, you name your tiers and express every paid difference as a feature flag with per-tier values — the divergence becomes a reviewable config file, not a merge conflict.
Connect a GitHub repository (GitLab works too), manage the flag matrix in the dashboard, and copy the generated tiers.json, tiers.yaml, or dependency-free flags.ts straight into your repo. Every tier builds from the same commit; each one enables exactly its own features.
how it works
- 01
connect your repo
One OAuth click for GitHub — tier·dev reads repo metadata only, never your source code.
- 02
define tiers + flags
Name open-source, saas, pro. Create flags like PRO_DASHBOARD_ENABLED with a default and per-tier overrides.
- 03
commit the config
Copy the generated JSON, YAML, or TypeScript snippet. Set PRODUCT_TIER per build and ship every edition from main.
a look inside
a few of the screens you'll actually use.
- flags resolved per tier, in one matrix
- generated json / yaml / code snippets
- no runtime sdk — config you commit
{
"tiers": {
"open-source": {
PRO_DASHBOARD_ENABLED: false
},
"saas": {
PRO_DASHBOARD_ENABLED: true
},
"pro": {
PRO_DASHBOARD_ENABLED: true
}
}
}tier·dev guides
Ways to use tier·dev, and how it compares.
- how toShip your open-source and SaaS versions from one repository — the exact workflowA step-by-step workflow for shipping an open-source edition and a paid SaaS edition from a single git repository using per-tier feature flags instead of branches.
- comparisontier·dev vs LaunchDarkly: which feature flags fit an open-core product?LaunchDarkly targets runtime experimentation; tier·dev targets edition packaging for open-source + SaaS products. When each fits, what each costs, and why open-core needs committed config.
- use caseTier-based feature flagging, explained: flags that know which edition they're inTier-based feature flagging assigns each feature flag a value per product tier — open-source, saas, pro — so one codebase ships as multiple editions. Definition, mechanics, and when to use it.