What happens to a flag after the rollout finishes?

You promote it and the branch goes away. Because a flag, a test and a rule are the same object, a finished rollout turns into a rule. The alternative is flag debt, which every engineer recognises: the flag that was meant to last two weeks and is still in the code two years later.

Can a non-engineer change one?

Yes, for the value and the audience. A developer decides where the flag is read in the code, once. After that, who gets it and what it returns both change without them.

Can I target on more than a user ID?

Yes, and that is what running flags on a customer data platform gets you. Anything on the profile is a targeting condition, including behaviour from outside the app.

Do I pay extra for it?

No. It sits with personalization and experiments rather than as a separate product, and it works on the free tier.

A striped lighthouse on a rock sending beams of light over the waves.

Feature flags that target the right customers.

Serve boolean, string, number, and JSON flags through your SDKs, targeted on the same profile as your campaigns.

Start for free

0.0on G2

10B+events

500M+users

7+years profitable

50+enterprises

Give every feature more customer context.

A flag hands back whatever your code asks for, including a payload that draws a whole surface.

Serve a boolean, a string, a number or JSON
Keep one person on one answer across every call
Read it by name from any SDK

Give every feature more customer context

Target features around real customers.

The same conditions that build a marketing audience decide who gets the feature.

Target on plan, lifecycle stage or spend
Include what they did on your website an hour ago
Use a segment you already built for something else

Roll out safely, then pull back fast.

Move from a few people to everyone, and back, without a deploy.

Roll out to ten percent, then more
Turn it off instantly when something breaks
Change who gets it without shipping

Keep what works as the new rule.

A flag, a test and a permanent rule are one object here, so finishing a rollout does not leave a branch behind.

Promote a finished rollout into a permanent rule
Turn any flag into an experiment without a deploy
Stop carrying dead branches nobody remembers

Give marketing more control.

A JSON flag returns the content that renders a card or a banner, so one system serves both teams.

Serve code a boolean and a page a payload
Let a marketer change content without engineering
Govern both with the same rules

Keep feature control in the same suite.

Flags come with the suite rather than as a line item priced per seat.

Skip the separate flagging contract
Avoid per-seat pricing that makes teams share logins
Use it on the free tier

Use cases built for the metrics that matter.

Three outcomes teams measure from day one.

A feature gate split from code, with the winning variant promoted

Wired into the toolsyour team already opens.

Slack, Stripe, Twilio, SendGrid, Gmail, Google Calendar, Firebase, Apache Kafka, AWS. Blu Agent operates them for you without a browser tab.

See every integration

Teams love it

They stopped stitching tools andhired one system.

Jim Stromberg, CEO at StockInvest — “Acquisition and retention finally feel like one connected motion instead of two separate problems.”
Jim Stromberg
CEO, StockInvest

“Acquisition and retention finally feel like one connected motion instead of two separate problems.”
Jim Stromberg
CEO, StockInvest

Eric Gardner, COO at FieldsUSA — “We finally have one system that sees the whole customer journey.”
Eric Gardner
COO, FieldsUSA

“We finally have one system that sees the whole customer journey.”
Eric Gardner
COO, FieldsUSA

Tadas Kertenis, Co-founder at Hoperfy — “With Intempt, we built a signal-led pipeline driven by real behaviors.”
Tadas Kertenis
Co-founder, Hoperfy

“With Intempt, we built a signal-led pipeline driven by real behaviors.”
Tadas Kertenis
Co-founder, Hoperfy

Frequently askedquestions.

01 / 05

How is this different from LaunchDarkly?

They are the better pure flagging platform and they publish the numbers to prove it. Two things differ. Their flag knows your code; ours also knows your customer, so you can target on plan or lifecycle rather than a user ID list. And theirs is a separate contract priced per seat and per connection, which is what teams complain about most.

Intempt Marketing

Your first flag, targeted on a real segment.

Define the flag, choose who gets it, read it by name in your code, then promote it or pull it. No separate contract and no per-seat bill.