APIs · head to head
Basis Theory vs Split

Basis Theory
APIs
Developer tokenisation platform that holds card and sensitive data inside a PCI Level 1 environment you do not operate
- From
- $995/month
- Free plan
- No

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
- Basis Theory starts at $995/mo; Split prices on request.
- Only Basis Theory lists tokenisation API; only Split lists feature flags with targeting.
- Prices and features on this page were last checked on 20 November 2026.
How do Basis Theory and Split differ?
Basis Theory and Split differ on starting price ($995/month against On request), pricing model and platforms. Only the attributes on which Basis Theory and Split actually diverge.
| Attribute | Basis Theory | Split |
|---|---|---|
| Starting price | $995/month | On request |
| Pricing model | Per month by token volume | Quote |
| Platforms | Web, iOS, Android, Linux | Web, API, iOS, Android, Windows |
| Category | APIs | Testing |
Identical on both: free tier (No).
Which features does each one have?
They share no listed features; 8 appear only for Basis Theory 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 Basis Theory
- Tokenisation API
- Hosted elements
- Outbound proxy
- PCI attestation of compliance
- Processor portability
- Reactors
- Access controls and audit
- PII and PHI options
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?
The jobs each tool is most often brought in to do.
Basis Theory
- A payments company that wants card on file without bringing its own infrastructure into PCI scope and paying for the assessment that followsnot Split
- A merchant locked into a processor by that processor vault that wants to hold its own tokens and route to more than one acquirernot Split
- A fintech collecting bank account and identity data that needs it isolated from its application database before an enterprise security reviewnot Split
- A team that needs to send stored card data to a third party for a one-off integration without that data traversing its own serversnot Split
Split
- A product organisation that wants every release measured against conversion and latency by default, not only deliberate experimentsnot Basis Theory
- Running A/B tests with real statistical significance rather than comparing two dashboard linesnot Basis Theory
- Catching a regression at five per cent rollout because a guardrail metric fires before the change reaches everyonenot Basis Theory
- A team already committed to Harness for CI and CD that wants flags in the same platform and contractnot Basis Theory
Where do Basis Theory and Split fall short?
Documented limitations, not opinions. Every one is a constraint you would hit in normal use.
Basis Theory
- The Starter plan is 995 US dollars a month before any volume, which is a real floor for an early stage company and puts the product out of reach of teams tokenising a few thousand records
- Starter is limited to the US region, so a company with European data residency requirements is pushed into a quoted Scale or Enterprise agreement immediately
- Log retention on Starter is 24 hours, which is well below what most security teams expect for a system holding cardholder data and forces an upgrade for reasons unrelated to volume
- Migrating away means moving card data out of the vault, which requires processor and assessor involvement and is slow, so the portability argument that attracts buyers cuts against them at exit
- An attestation of compliance covers the vendor environment, not your assessment; your assessor still decides what is in scope, and buyers occasionally discover their integration pattern pulled systems back into scope anyway
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 Basis Theory and Split cost?
Basis Theory starts at $995/mo; Split is priced on request. Plan by plan below, from each vendor's own pricing page.
Basis Theory
$995/month- Starter$995/mo
- 20,000 tokens included
- Production PCI Level 1 environment
- US region only
- ScaleOn request
- Quoted
- Higher token volumes
- Additional regions
- EnterpriseOn request
- Quoted
- Additional compliance options for PII and PHI
- Responses for 95 percent of PCI SAQ D
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 Basis Theory if
- You need tokenisation api.
- You work on Web, iOS, Android, Linux.
- You also want hosted elements.
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 Basis Theory or Split better?
- Neither clearly leads. Basis Theory starts at $995/month and Split at On request, and user ratings are close enough to be indistinguishable. Choose on capability and platform support.
- Which is cheaper, Basis Theory or Split?
- Basis Theory starts at $995/month and Split at On request.
- Does Basis Theory or Split run on more platforms?
- Basis Theory runs on Web, iOS, Android, Linux. Split runs on Web, API, iOS, Android, Windows.
- What is Basis Theory best used for?
- Basis Theory is most often used for a payments company that wants card on file without bringing its own infrastructure into pci scope and paying for the assessment that follows, a merchant locked into a processor by that processor vault that wants to hold its own tokens and route to more than one acquirer, a fintech collecting bank account and identity data that needs it isolated from its application database before an enterprise security review, a team that needs to send stored card data to a third party for a one-off integration without that data traversing its own servers. Of those, a payments company that wants card on file without bringing its own infrastructure into pci scope and paying for the assessment that follows and a merchant locked into a processor by that processor vault that wants to hold its own tokens and route to more than one acquirer are not what Split is typically brought in for.
- What can Basis Theory do that Split cannot?
- Basis Theory covers Tokenisation API, Hosted elements, Outbound proxy, PCI attestation of compliance. Split covers Feature flags with targeting, Metrics impact engine, Guardrail metrics, Statistical significance testing.
Answered from the vendors’ own pages
Basis Theory: Does this make us PCI compliant?
It removes cardholder data from your systems and gives you an AOC plus documented responses for most of a SAQ D. Your assessor still determines your scope, and a careless integration can pull systems back in.
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.
Basis Theory: What does it cost to start?
995 US dollars a month on Starter, including 20,000 tokens, a production PCI Level 1 environment and US hosting. Higher tiers are quoted.
Split: Can I buy just feature flags?
Not from a price list. Harness publishes bundle tiers and directs single-module buyers to sales.
Basis Theory: Can we switch payment processors without re-collecting cards?
Yes, that is the main non-compliance reason to buy it. You hold the tokens and detokenise into whichever processor you route to.
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.
Basis Theory: Is data stored outside the United States?
Not on Starter, which is US only. Other regions require a Scale or Enterprise agreement.
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.
Related pages
More on Basis Theory
Other head to heads
- Basis Theory vs Skyflow
- Basis Theory vs Increase
- Basis Theory vs Lithic
- Basis Theory vs Swan
- Basis Theory vs Moov
- Basis Theory vs Volt
- Basis Theory vs TrueLayer
- Basis Theory vs Paymentology
- Basis Theory vs Trustly
- Basis Theory vs Vodeno
- Basis Theory vs Dwolla
- Basis Theory vs Liveblocks
- Basis Theory vs 10x Banking
- Basis Theory vs Appwrite
- Basis Theory vs Bruno
- Basis Theory vs Marqeta
- Basis Theory vs Apidog
- Basis Theory vs Microsoft Azure API Management
- Basis Theory vs GrowthBook
- Basis Theory vs Kameleoon
- Basis Theory vs Eppo
- Basis Theory vs Katalon
- Basis Theory vs Selenium
- Basis Theory vs Sauce Labs
- Basis Theory vs TestRail
- Basis Theory vs Applitools
- Basis Theory vs CloudBees Smart Tests
- Basis Theory vs QA Wolf
- Basis Theory vs CircleCI
- Basis Theory vs BrowserStack
- Basis Theory vs BugHerd
- Basis Theory vs SoapUI
- Basis Theory vs Playwright
- Basis Theory vs GitHub Actions
- Basis Theory vs Cypress
- Basis Theory vs Appium
- Split vs Skyflow
- Split vs Increase
- Split vs Lithic
- Split vs Swan
- Split vs Moov
- Split vs Volt
- Split vs TrueLayer
- Split vs Paymentology
- Split vs Trustly
- Split vs Vodeno
- Split vs Dwolla
- Split vs Liveblocks
- Split vs 10x Banking
- Split vs Appwrite
- Split vs Bruno
- Split vs Marqeta
- Split vs Apidog
- Split vs Microsoft Azure API Management
- Split vs GrowthBook
- Split vs Kameleoon
- Split vs Eppo
- Split vs Katalon
- Split vs Selenium
- Split vs Sauce Labs
- Split vs TestRail
- Split vs Applitools
- Split vs CloudBees Smart Tests
- Split vs QA Wolf
- Split vs CircleCI
- Split vs BrowserStack
- Split vs BugHerd
- Split vs SoapUI
- Split vs Playwright
- Split vs GitHub Actions
- Split vs Cypress
- Split vs Appium
