Coming soon [email protected]

Feature testing for software companies

Track user behaviour to help you build what matters

You don’t know if a feature worked, what to build next, or how to try an idea on 5% of your users — because building the variants costs weeks of engineering. Somar Code builds the variants. Signals show the problem, the agent writes two or three versions, ships them behind a flag, and the experiment says which one won.

0 people have joined the waitlist

Be first to get access when Somar launches. No spam — just the launch.

Signals Variants Flag @ 10% Experiment Verdict Winner ramps

Somar Code writes the variants

The expensive part of testing a feature is building the versions. The agent reads your signals and your repo, writes control plus two variants, and opens one PR — all behind one flag.

Ship it to a slice, safely

Merged code serves nobody until you open the flag. Try it on 5% of Pro users, watch the guardrails, and cancel from your phone — flag to 0%, no revert, no deploy.

Every rollout gets a verdict

The metric is chosen before it ships, so weeks later the list says won, lost, or not enough data — and a rollout nobody touched in a month says stuck.

somar / onboarding-v2

Drop-off concentrates at step 2. I’ve written two variants — inline skip, and a shorter form — on branch somar/onboarding-v2, behind one flag, and opened the PR. Merge it and both sit at 0% until you open the flag.

PR #482 · control + 2 variants flag: onboarding_v2 · 0% metric: activation rate

Build what matters — and know that it did.

Join the waitlist — we’ll email you when Somar launches.

Join the waitlist