Softwr

APIs · head to head

Liveblocks vs Split

Liveblocks logo

Liveblocks

APIs

Realtime collaboration infrastructure for building multiplayer features

From
Free
Free plan
Yes
Split logo

Split

Testing

Feature flags tied to a metrics pipeline that attributes production impact to each release, now Harness FME

From
On request
Free plan
No

The short version

  • Liveblocks starts at $30/mo; Split prices on request.
  • Only Liveblocks lists realtime presence and cursors; only Split lists feature flags with targeting.
  • Where Liveblocks falls short: on the Free plan, each metered feature has a hard cap and simply pauses when exceeded rather than allowing overage.
  • Prices and features on this page were last checked on 20 November 2026.

How do Liveblocks and Split differ?

Liveblocks and Split differ on starting price (Free against On request), pricing model (Freemium against Quote) and free tier (Yes against No). Only the attributes on which Liveblocks and Split actually diverge.

Attributes where Liveblocks and Split differ
AttributeLiveblocksSplit
Starting priceFreeOn request
Pricing modelFreemiumQuote
Free tierYesNo
PlatformsWeb, APIWeb, API, iOS, Android, Windows
CategoryAPIsTesting

Not yet recorded: founded for Split.

Which features does each one have?

They share no listed features; 6 appear only for Liveblocks and 8 only for Split. Drawn from each product's published feature list. An absence here means we hold no record of it - not that the product lacks it.

Only in Liveblocks

  • Realtime presence and cursors
  • Comments
  • Version history
  • Custom notifications
  • SSO and SOC 2
  • Management API

Only in Split

  • Feature flags with targeting
  • Metrics impact engine
  • Guardrail metrics
  • Statistical significance testing
  • Event ingestion
  • SDKs and streaming updates
  • Audit and approvals
  • Harness platform integration

What is each one used for?

Liveblocks is most often brought in for adding live cursors and presence to a collaborative editor. The jobs each tool is most often brought in to do.

Liveblocks

  • Adding live cursors and presence to a collaborative editornot Split
  • Building threaded comments on documents or designsnot Split
  • Sending realtime notifications tied to collaborative actionsnot Split
  • Restoring previous versions of collaborative contentnot Split

Split

  • A product organisation that wants every release measured against conversion and latency by default, not only deliberate experimentsnot Liveblocks
  • Running A/B tests with real statistical significance rather than comparing two dashboard linesnot Liveblocks
  • Catching a regression at five per cent rollout because a guardrail metric fires before the change reaches everyonenot Liveblocks
  • A team already committed to Harness for CI and CD that wants flags in the same platform and contractnot Liveblocks

Where do Liveblocks and Split fall short?

Liveblocks's most cited limit: on the Free plan, each metered feature has a hard cap and simply pauses when exceeded rather than allowing overage. Documented limitations, not opinions. Every one is a constraint you would hit in normal use.

Liveblocks

  • On the Free plan, each metered feature has a hard cap and simply pauses when exceeded rather than allowing overage
  • The jump from Pro ($30/month) to Team (starting at $600/month) is steep for teams that outgrow Pro but don't need full Team scale
  • Multi-region hosting and SCIM provisioning are Enterprise-only and require custom pricing

Split

  • Split is now a module of the Harness platform and split.io redirects to harness.io, so buying it means entering a Harness commercial relationship rather than a standalone flag vendor contract
  • Harness no longer publishes per-module prices, so an organisation that wants only feature management cannot get a list price and must negotiate a module out of a platform bundle
  • The measurement engine needs traffic volume to reach significance, so a product with modest usage gets flags with an experimentation layer it will rarely be able to conclude anything from
  • Metric attribution depends on correctly instrumented events flowing into Split, which is an integration project in its own right; without it you have paid for an experimentation platform and are using it as a flag switch
  • As part of a larger DevOps suite the roadmap now competes with CI, CD, security and cloud cost modules for attention, so feature management is no longer the company’s single focus the way it was as an independent product

How much do Liveblocks and Split cost?

Liveblocks has a free plan, with paid plans from $30/mo; Split is priced on request. Plan by plan below, from each vendor's own pricing page.

Liveblocks

Free
  • FreeFree
    • 10 projects
    • 3 dashboard seats
    • 10 simultaneous connections per room
  • Pro$30/mo
    • $30 monthly credits
    • Removes Liveblocks branding
    • 3 dashboard seats
  • Team$600/mo
    • SSO and SOC 2
    • 10 dashboard seats
    • 50 connections/room

Split

On request
  • Harness FreeFree
    • Harness Open Source and community support
    • Intended for individuals and small teams
    • Feature management capability limited at this tier
  • Harness EssentialsOn request
    • Bundled DevOps modules including CI, CD, IaC and security testing
    • Standard support
    • Pricing requires contacting sales
  • Harness EnterpriseOn request
    • Mix and match from 15 or more modules including Feature Management and Experimentation
    • Premier support with a dedicated account manager
    • Higher pipeline concurrency and organisation limits

Which should you pick?

Choose Liveblocks if

  • You need realtime presence and cursors.
  • You want to start without paying.
  • You work on Web, API.
  • You also want comments.

Choose Split if

  • You need feature flags with targeting.
  • You work on Web, API, iOS, Android, Windows.
  • You also want metrics impact engine.

Questions people ask

Is Liveblocks or Split better?
Neither clearly leads. Liveblocks starts at Free and Split at On request, and user ratings are close enough to be indistinguishable. Choose on capability and platform support.
Which is cheaper, Liveblocks or Split?
Liveblocks has a free tier; the other does not. Paid plans start at Free for Liveblocks and On request for Split.
Does Liveblocks or Split run on more platforms?
Liveblocks runs on Web, API. Split runs on Web, API, iOS, Android, Windows.
Can I use Liveblocks for free?
Yes. Liveblocks has a free tier, so you can try it without paying. Split starts at On request.
What is Liveblocks best used for?
Liveblocks is most often used for adding live cursors and presence to a collaborative editor, building threaded comments on documents or designs, sending realtime notifications tied to collaborative actions, restoring previous versions of collaborative content. Of those, adding live cursors and presence to a collaborative editor and building threaded comments on documents or designs are not what Split is typically brought in for.
What can Liveblocks do that Split cannot?
Liveblocks covers Realtime presence and cursors, Comments, Version history, Custom notifications. Split covers Feature flags with targeting, Metrics impact engine, Guardrail metrics, Statistical significance testing.

Answered from the vendors’ own pages

Liveblocks: What does Liveblocks cost?

Liveblocks offers a Free plan with hard usage caps, a Pro plan at $30/month ($25/month billed annually) including $30 in monthly credits, a Team plan from $600/month, and custom Enterprise pricing.

Source
Split: Is Split still called Split?

It is now sold as Harness Feature Management and Experimentation after the Harness acquisition, and split.io redirects to harness.io.

Liveblocks: Is there a free plan, and what are its limits?

Yes, the Free plan includes 10 projects, 3 dashboard seats, 10 simultaneous connections per room, 3,000 collaboration minutes, 200 comments, and 1GB of realtime data storage, with features pausing once a cap is hit.

Source
Split: Can I buy just feature flags?

Not from a price list. Harness publishes bundle tiers and directs single-module buyers to sales.

Liveblocks: How is usage metered?

Paid plans include monthly credits covering collaboration minutes, comments, and storage; usage beyond the credit is billed at metered rates such as $0.002 per collaboration minute and $0.01 per comment, with credits resetting each billing cycle without rollover.

Source
Split: What does it do that a plain flag service does not?

It attributes changes in your product metrics to specific flags with statistical significance testing and alerts on guardrail metrics.

Split: Do we need a lot of traffic?

Yes. Statistical tests need volume to conclude, so low-traffic products get limited value from the measurement layer.

Share

Related pages

Other head to heads