v0.1 · public beta — join the first cohort

Ship UI without shipping code.

Fragments is a no-code runtime for banners, modals, experiments and product surfaces. Marketers build, the SDK delivers, analytics closes the loop — no sprint required.

customer website · example.com
Home › Pricing
Simple pricing, built for teams

Start free. Scale as you grow. No credit card required for the first workspace.

Starter$0
Team$49
Business$149
area · promo-ru
FOR YOU · RU
–20% on annual
Auto-applied if you upgrade today.
Claim it →
SDK EVENTS · REAL-TIME
00:00.024✓sdk.init()
00:00.041→fetch /api/slots
00:00.089✓resolve user.ctx
00:00.094·geo=RU · device=desk
00:00.102✓match widget #promo-ru
00:00.118→render tree (4 nodes)
00:00.151✓painted · 38ms total
00:00.152→track impression
resolving…
plays well with
Next.jsReactVueNuxtFigmaGA4Yandex MetricaAmplitudeSegmentVercelCloudflareNext.jsReactVueNuxtFigmaGA4Yandex MetricaAmplitudeSegmentVercelCloudflare
Why Fragments

Your marketing team doesn't need a sprint to change a banner.

Every UI experiment that goes through a backlog is one that won't happen. Fragments moves the surface layer out of code and into the hands of the people who need it.

Before — life with tickets

  • ✕Every banner, modal or CTA is a ticket. Every ticket is a sprint. Every sprint has six other tickets.
  • ✕Marketing waits three weeks for a colour change. Nobody is happy about this, including the engineers.
  • ✕Experiments require a deploy, so you run one a month instead of one a day.
  • ✕Analytics live in five tools. Nobody knows which variant won, only which one shipped.

After — one SDK, done

  • →A visual builder your PM can use. Drag, type, publish — banner live in fifteen minutes.
  • →Targeting by geo, device, plan, cohort, time. Rolls out from the edge, not a release.
  • →A/B tests, feature flags and scheduled rollouts live inside the same tool you built the widget in.
  • →Impressions, clicks and conversions attached to every fragment, out of the box.
How it works

Build, ship, analyse. In that order, on the same surface.

Three steps, about fifteen minutes from a blank canvas to the first impression on production.

01 · Build
step 01 / 03~12 min
Build

Drag components onto a canvas. Import from Figma. Wire up data sources and conditional logic without touching the codebase.

canvas▢ banner · 420pxdatauser.plan, user.geologicif plan = free → promo_astate● ready to ship
02 · Ship
step 02 / 03~2 min
Ship

Pick audience. Pick schedule. Pick split. Publish to the edge — live on your site in under a second, globally.

geoRU, KZ, BYdevicedesktop + tabletsplit50 / 50 A/Bcdn● propagated · 380ms
03 · Analyse
step 03 / 03live
Analyse

Impressions, clicks, conversions — attached to every fragment, streamed to your dashboard, exportable to Metrica, GA4, Amplitude.

impr12,481ctr17.0%conv4.2%winnervariant B · p=0.02
Platform

Three things, one runtime.

A builder, a delivery layer and analytics share one SDK — plus the two features teams stay for after the pilot.

A builder that speaks to designers, ships to engineers.

Drag-and-drop canvas, component library, data binding, conditional logic, versioning. Exports production-grade DOM — not an iframe.

canvaslibrarylogic

Targeting, scheduling, flags and A/B — one surface.

Roll a fragment out to a cohort, a country or Tuesday 10am. Flip it off in a click; every change goes through the same audit log.

geoschedulea/b

Every fragment comes with its own analytics, attached.

Impressions, clicks, conversions, dwell — measured on the widget, attributed to the user, exported to GA4, Metrica, Amplitude.

eventsfunnelsexport

Figma → production, one button.

Any frame becomes a live area. Component names become props, auto-layout becomes CSS, variants become states. No hand-off doc.

framesvariantsround-trip

AnomalyDetector — always on, quietly.

A model watches every live fragment. When CTR, conversion or latency drifts off-pattern, it pages you — and knows what to ignore.

ctrlatencyslack

Feature flags without the ceremony.

Percentage rollouts, kill switches, cohort targeting. Same tool, same audit log, no second vendor.

rolloutskill-switchcohorts
from idea to live
15min
Average time from opening the builder to first impression on production.
experiment throughput
10×
More tests per month vs. pre-Fragments baseline across pilot teams.
code written by marketing
0
Lines. Forever. The builder produces production DOM — this is not a metaphor.
engineering integration
1h
One afternoon. One script tag. One identify call. One happy platform team.
SDK

One script tag. Then engineers get out of the way.

Drop the SDK once, mark your slots with data-fragment, ship. Everything after that happens in the dashboard — whatever your stack renders with.

index.html · one-time setupHTML
1
2
3
4
5
6
7
8
9
10
<!DOCTYPE html>
<html>
<head>
  <script
    src="https://cdn.fragments-studio.io/sdk.js"
    data-key="frg_4kJ29_live"
    async defer>
  </script>
</head>
</html>
app.tsx · render an areaTypeScript
1
2
3
4
5
6
7
8
9
10
import { Area } from '@fragments/react';

// drop an area anywhere — overrides + options
<Area
  areaCode="4ce18c45cd999"
  props={{
    key: 'Override value',
  }}
  options={{ ssr: false }}
/>
12.4 kbgzipped, zero deps
<50msp99 edge latency
ssr · csrboth supported natively
csp safenonces + strict-dynamic

Anywhere a <div> goes, a fragment goes.

Six of many. Every one of them ships from the same builder, the same SDK, the same dashboard.

01

Promo banners and announcements

Launch offers, holiday messaging, compliance notices, maintenance bars. Scheduled to the minute, killable with one click.

bannermodalannouncement-bar
02

A/B and multivariate tests

Test copy, colour, layout, placement. System allocates traffic, tracks lift, stops on significance. Export the winner to your repo if you want.

a/bmultivariateauto-stop
03

Geo and compliance targeting

Show different content in RU, KZ, EU. Solve GDPR banners. Swap pricing by currency. All from the same dashboard.

geogdpri18n
04

In-product onboarding and nudges

Empty-state prompts, upgrade nudges, feature announcements, NPS surveys. Trigger on user traits, scroll, inactivity, anything.

onboardingnpsupsell
05

Fast widget production

Figma → builder → prod, with data binding. Ideal for landing pages, event sites, campaign microsites that need to ship this week.

figma-importlandingcampaign
06

Feature flags without the ceremony

Percentage rollouts, kill switches, cohort targeting. Same tool. Same audit log. No second vendor.

flagskill-switchcohorts
Pricing

Flat pricing. No seat maths, no surprises.

Per workspace, not per seat. Every plan includes all three modules and all targeting.

Pilot
Pilot · free

Full platform, no credit card, cancel by doing nothing.

$0/ 14 days
Start pilot
  • 10,000 impressions / day
  • 3 live fragments
  • All modules, all targeting
  • Community Slack support
Team
Team · most chosen

For product and growth teams running weekly experiments.

$499/ month
Start pilot →
  • 1M impressions / month
  • Unlimited fragments & users
  • A/B tests + feature flags
  • Metrica, GA4, Amplitude export
  • Dedicated Slack channel
  • Priority response within 24h
Enterprise
Enterprise

Self-host, SSO, custom SLA, procurement teams welcome.

Let's talk
Contact sales
  • Dedicated cloud
  • SSO (SAML/SCIM on request)
  • Audit log exports
  • Data residency on request
  • Direct founder support

Questions we actually get asked.

Common questions from pilots, last updated April 2026. Anything else — write to us, a founder answers.

Optimize is dead and VWO rewrites your DOM with a mutation overlay — slow, fragile, and their builder is from 2014. Fragments renders production-grade native DOM through a purpose-built SDK, with SSR support, a modern builder, and feature flags baked in.
12.4 kb gzipped, zero dependencies, async by default, no render-blocking. p99 time-to-paint for a fragment is under 50ms globally. We publish our perf budget publicly and ship slower if we break it.
Yes. The SDK is framework-agnostic — you mark slots with data-fragment or use the thin adapter for your framework. SSR is supported natively; hydration is clean.
Default EU hosting; RU localization (152-ФЗ-compliant) and US on the roadmap. Custom regions on Enterprise. Fragments ships with consent-mode integration for GDPR and can be configured to not drop a single cookie until the user opts in.
No — that's literally the point of the product. After the one-time SDK install, everything happens in the dashboard. If you need a new slot on a new page, a dev adds one data-fragment attribute. That's it.
On the Enterprise plan, yes — either on-prem or in a dedicated cloud tenant. For most teams, our managed cloud is faster to roll out and cheaper to operate.
Pilot · 14 days · no card

Ship your first fragment before stand-up tomorrow.

Book the call and we'll do the integration with you, on your site, in one sitting.

A 30-minute call. No sales pitch, a founder on the line.
We drop the SDK into your site together, live.
A banner on production before you hang up — or lunch is on us.
spec sheetfragments/0.1.0-beta
statuspublic beta · v0.1
hostingEU · RU / US on roadmap
encryptionin transit and at rest
lock-innone — export DOM anytime
sdk12.4 kb · zero deps