Softwr

APIs · head to head

PocketBase vs Split

PocketBase logo

PocketBase

APIs

Open-source backend with REST API, real-time subscriptions and Admin UI

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

  • PocketBase is a lightweight, open-source backend.
  • PocketBase is free; Split prices on request.
  • Only PocketBase lists REST API; only Split lists feature flags with targeting.
  • Where PocketBase falls short: requires technical expertise to deploy and maintain.
  • Prices and features on this page were last checked on 20 November 2026.

How do PocketBase and Split differ?

PocketBase and Split differ on starting price (Free against On request), free tier (Yes against No) and platforms. Only the attributes on which PocketBase and Split actually diverge.

Attributes where PocketBase and Split differ
AttributePocketBaseSplit
Starting priceFreeOn request
Free tierYesNo
PlatformsLinux, Windows, macOSWeb, API, iOS, Android, Windows
CategoryAPIsTesting

Not yet recorded: pricing model for PocketBase, founded for Split.

Which features does each one have?

They share no listed features; 9 appear only for PocketBase 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 PocketBase

  • REST API
  • Real-time subscriptions
  • Admin UI
  • SQLite
  • Webhooks
  • File storage
  • Go support
  • Docker support

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?

PocketBase is most often brought in for embedded realtime database with REST API. The jobs each tool is most often brought in to do.

PocketBase

  • Embedded realtime database with REST APInot Split
  • Backend-as-a-service for single-file deploymentsnot Split
  • Rapid application development with email/OAuth2 authenticationnot Split
  • File storage and media attachment managementnot Split
  • Lightweight alternative to Firebase or traditional backend infrastructurenot Split
  • Go and JavaScript customisable application frameworknot Split

Split

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

Where do PocketBase and Split fall short?

PocketBase's most cited limit: requires technical expertise to deploy and maintain. Documented limitations, not opinions. Every one is a constraint you would hit in normal use.

PocketBase

  • Requires technical expertise to deploy and maintain
  • No built-in hosting provided
  • Community support only

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 PocketBase and Split cost?

PocketBase is free to use; Split is priced on request. Plan by plan below, from each vendor's own pricing page.

PocketBase

Free
  • PocketBase (open source, self-hosted)Free

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 PocketBase if

  • You need rest api.
  • You want to start without paying.
  • You work on Linux, Windows, macOS.
  • You also want real-time subscriptions.

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 PocketBase or Split better?
Neither clearly leads. PocketBase 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, PocketBase or Split?
PocketBase has a free tier; the other does not. Paid plans start at Free for PocketBase and On request for Split.
Does PocketBase or Split run on more platforms?
PocketBase runs on Linux, Windows, macOS. Split runs on Web, API, iOS, Android, Windows.
Can I use PocketBase for free?
Yes. PocketBase has a free tier, so you can try it without paying. Split starts at On request.
What is PocketBase best used for?
PocketBase is most often used for embedded realtime database with rest api, backend-as-a-service for single-file deployments, rapid application development with email/oauth2 authentication, file storage and media attachment management. Of those, embedded realtime database with rest api and backend-as-a-service for single-file deployments are not what Split is typically brought in for.
What can PocketBase do that Split cannot?
PocketBase covers REST API, Real-time subscriptions, Admin UI, SQLite. Split covers Feature flags with targeting, Metrics impact engine, Guardrail metrics, Statistical significance testing.

Answered from the vendors’ own pages

PocketBase: How much does PocketBase cost?

PocketBase is completely free and open-source. It is a self-hosted backend solution with database, authentication, and file storage capabilities at no cost.

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.

PocketBase: Is PocketBase open-source?

Yes, PocketBase is open-source software. You can download, modify, and deploy it yourself at no cost with no licensing restrictions.

Source
Split: Can I buy just feature flags?

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

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