Merge Gateway launchDistribution-amplified (light)

The product

What is Merge Gateway?

Merge is a San Francisco company founded in 2020 by Shensi Ding and Gil Feig, with offices in San Francisco, New York and Berlin. It built its business on the unified API idea: one integration that covers a whole software category, across HR and payroll, applicant tracking, CRM, accounting, file storage and ticketing, so a B2B product can ship customer-facing integrations once rather than one vendor at a time. On its own site Merge states it raised a $55 million Series B backed by Accel, Addition and NEA, and names Airwallex, Revolut, Brex and Ramp among its customers. Those are the company's stated figures, cited here as context for why an announcement from this account travels.

Gateway extends that pattern from SaaS integrations to model providers. The lane it competes in is LLM routing and gateway infrastructure, where the real alternatives are the other unified inference layers and routers that sit between an application and OpenAI, Anthropic, Google, Mistral, Cohere and the rest, plus the option most teams are actually on: a single provider SDK wired in during the prototype and never revisited. Merge's stated angle is that the routing rule should belong to the customer rather than to the vendor.

Merge is a real company with a real product, and Shensi Ding is a real founder posting from her own account. This reading is only about how the launch post's reach was built.

What it does

• Routes requests across every major provider, including OpenAI, Anthropic, Google, Mistral and Cohere, from one API key and one base URL.
• Scores models on benchmarks the customer chooses and weights, on every request, rather than on a vendor's own idea of the best model.
• Supports standard benchmarks (HumanEval for code, MMLU for knowledge, GPQA for reasoning, GSM8K for math, IFEval for instruction following), industry leaderboards, and custom evals uploaded through the UI, JSON or the API.
• Caps spend by project, team or customer tier in real time, and attributes cost by model, provider and team.
• Fails over automatically when a provider degrades, shifting traffic without a code change.
• Adds policy-based routing, data loss prevention and prompt-injection protection at the gateway layer.

The launch was a single post carrying a 118-second video, published at 7:00 AM Pacific on Tuesday 26 May 2026, exactly on the hour, from Merge co-founder Shensi Ding's own account.

The post is built as an argument, not a feature list. It opens with the name and the tagline, "Introducing Merge Gateway, Build Your Own Router," then walks the reader through a scenario before naming the product: you are three sprints into a coding assistant, you picked the most hyped model, integrated, tested and deployed, and a month later a new model drops, so you re-test, re-integrate and re-deploy. The line that turns it is the one that costs nothing to agree with: "Your product didn't change, but the benchmark did."

From there the post makes a claim broad enough to argue with, "There is no best model," followed by the resolution: "There's only the right one for your product, users, and use-cases." Only then does the product appear, as the answer to a problem the reader has already accepted. The closing mechanic is a stated offer: $100 in credits to the first 200 people who comment.

A founder posting from her own account, not the brand

Ding posted from @shensi, an account created in July 2018, based in New York, carrying the bio "co-founder @merge_api" and a Merge affiliate badge, with 7,178 followers at the time of RADAR's pull. That follower count is worth holding next to the view count below. A 7,000-follower account is not a distribution machine on its own, which is the ordinary reason a launch at this scale reaches for help with the top of the funnel.

The launch ran a small number of assets, each doing a distinct job: a video, a narrative post, a declared comment incentive, and a scheduled slot at the start of the US work week.

The credits offer is disclosed, and it has a hard ceiling

The offer of $100 in credits to the first 200 people who comment is a legitimate, openly stated tactic. It is written into the post where every reader can see it, it pays in the company's own product rather than in cash, and it asks for a comment rather than a like or a repost. RADAR treats it as a real driver of the 240 replies this launch carried, and as an honest one.

It is also capped. The offer tops out at 200 people, so at its absolute maximum it accounts for 200 of the 240 replies and nothing else. It cannot move a view count into the millions. Whatever explains the gap between 3.67 million views and 1,378 likes, the credits offer is not it.

The launch post reached 3,667,154 views on 1,378 likes, with 361 reposts, 240 replies, 116 quotes and 1,337 bookmarks. These are matured public metrics, re-pulled directly from the source post on 26 August 2026.

Thin written layers, a strong save layer

The public actions total 2,095, which is 0.057 percent of the views. For reach in the multi-millions that is on the thin side, and the written layers in particular are shallow: 240 replies and 116 quotes are modest for a post seen this many times, even with a comment incentive helping the reply count along. This is the shape the original reading described, a launch whose views ran a clear step ahead of the audience that engaged.

The bookmark layer cuts the other way, and it deserves credit. At 1,337 saves against 1,378 likes, bookmarks land at 0.97 per like, almost one to one. A bookmark is a private action with no social return: nobody sees it, it wins no clout, and it only happens when a reader intends to come back. On an infrastructure launch aimed at engineers evaluating a routing layer, a save layer this close to the like layer is the signal of a genuinely interested technical audience inside the reach, however that reach was assembled.

What the numbers did between detection and today

RADAR first measured this launch at 3,661,633 views on 1,875 likes. On the matured re-pull the views had risen by 5,521 to 3,667,154, while the likes had fallen by 497 to 1,378. Views rising and likes falling is not a contradiction: view counts only ever accumulate, while like counts can be revised downward when the platform removes engagement it has decided not to count. RADAR re-pulls for exactly this reason, and shows both figures rather than the flattering one.

Why the published read stays light

RADAR's verdict is a five-signal forensic read. The views-to-likes ratio is one input, weighed alongside the velocity curve, how tightly the engagement layers move together, whether the reply network reads as real conversation, and how the amplifier accounts cluster. The ratio moved. The other four signals have not been re-derived since the published read was set, so the honest position is that the ratio now argues for a heavier band while the read that was actually adjudicated argues for a lighter one, and RADAR states both instead of picking the newer number and calling it the original finding.

The original framing still holds on its own terms: because the ratio sits so close to the 2,000 threshold, the engagement layers underneath matter for placing the read. The written layers are present but not deep, which is consistent with a launch whose views ran a clear step ahead of the audience that engaged. The bookmark layer is the counterweight, and it is a real one.

What the forensic record holds

RADAR's forensic record for this launch holds a roster of 38 amplifier accounts. No regime classification was settled in the ERP for this launch, so RADAR does not characterize how the lift was delivered, and does not infer one from the roster size. RADAR names no account, no vendor and no third party, here or anywhere on this surface. Amplifiers are counted, not identified.

The copy is the part worth stealing. The post spends its first six lines putting the reader inside a problem they have lived, three sprints in, a new model drops, re-test and re-deploy, before it names the product at all. Then it plants a claim broad enough to argue with. That structure is why a routing layer, which is not an obviously postable product, got 240 people to write something back.

The number to sit with is the gap between the layers. Bookmarks came in almost level with likes, which says the readers who did engage were the right ones. Replies and quotes stayed thin against millions of views, which says most of the reach never turned into an audience. A launch can buy the top of the funnel. It cannot buy the part where people save the post because they intend to use the thing.

FORKOFF builds launch videos and the launch copy around them so the reach lands on people who would have saved the post anyway. See how we approach it on the viral launch video service, or read the best product launch videos we track for more real examples.