Softwr

Machine Learning · head to head

Dataiku vs Yapily

Dataiku logo

Dataiku

Machine Learning

Browser-based platform where visual data preparation and written code share one pipeline

From
Free
Free plan
Yes
Yapily logo

Yapily

APIs

Open banking API infrastructure for account data and pay-by-bank payments across Europe

From
Free
Free plan
Yes

The short version

  • Both are free.
  • Only Dataiku lists visual Flow; only Yapily lists unified open banking API.
  • Prices and features on this page were last checked on 20 November 2026.

How do Dataiku and Yapily differ?

Dataiku and Yapily differ on pricing model, platforms and category (Machine Learning against APIs). Only the attributes on which Dataiku and Yapily actually diverge.

Attributes where Dataiku and Yapily differ
AttributeDataikuYapily
Pricing modelFreemiumFree sandbox, pay-as-you-go production
PlatformsLinux, macOS, Windows, WebWeb, API
CategoryMachine LearningAPIs

Identical on both: starting price (Free), free tier (Yes).

Not yet recorded: founded for Yapily.

Which features does each one have?

They share no listed features; 9 appear only for Dataiku and 6 only for Yapily. 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 Dataiku

  • Visual Flow
  • Visual recipes
  • Code recipes and notebooks
  • Computation pushdown
  • Automated machine learning
  • Scenarios
  • Node topology
  • Governance features

Only in Yapily

  • Unified open banking API
  • Account information access
  • Payment initiation
  • Free sandbox
  • Multi-country bank coverage
  • Webhooks and reconciliation tooling

What is each one used for?

Yapily is most often brought in for A merchant wanting a lower-cost payment method alongside card acceptance. The jobs each tool is most often brought in to do.

Dataiku

  • Organisations where analysts and data scientists must collaborate on the same pipeline rather than exchanging extractsnot Yapily
  • Regulated model risk environments needing documented lineage, sign-off and a record of how a production model was producednot Yapily
  • Pushing heavy transformations down into a cloud warehouse while keeping the pipeline definition in one reviewable placenot Yapily
  • Large enterprises replacing a sprawl of spreadsheets and unmanaged scripts with something a governance function will acceptnot Yapily

Yapily

  • A merchant wanting a lower-cost payment method alongside card acceptancenot Dataiku
  • A lending or budgeting product needing bank account data for affordability checksnot Dataiku
  • A business wanting one API instead of separate integrations to each bank's own open banking standardnot Dataiku
  • A company prototyping open banking features for free in sandbox before committing budgetnot Dataiku

Where do Dataiku and Yapily fall short?

Documented limitations, not opinions. Every one is a constraint you would hit in normal use.

Dataiku

  • Visual recipes are stored as Dataiku's own configuration and do not export as runnable SQL or Python, so a Flow with hundreds of visual steps has to be rebuilt from scratch if the organisation ever leaves, and that cost rises with every project added
  • Production requires separate automation and API nodes, each installed and licensed, so the figure quoted for building models is not the figure for running them
  • Licensing is per user across tiers, and the lower tiers are constrained enough that occasional contributors frequently end up needing a full seat, which makes a wide rollout cost more than the initial estimate suggested
  • A self-hosted installation needs a dedicated administrator for upgrades, connection management, permissions and node topology, so the licence is a fraction of the real cost of ownership
  • Computation pushes down to the warehouse or Spark cluster where it is billed by that provider, so a platform sold on making analysts self-sufficient can generate a large warehouse bill that nobody attributes back to it

Yapily

  • Production pricing itself is not published; only the resulting typical merchant transaction cost is publicly known, so the underlying platform fee still requires a sales conversation
  • Consumer adoption of pay-by-bank still lags card payments, so merchants offering it as a checkout option typically see it used as a secondary rather than primary payment method
  • Coverage depends on the banks in each country maintaining reliable open banking APIs, and inconsistent bank-side reliability across markets is a known category-wide weakness, not unique to Yapily but not solved by it either
  • As infrastructure for both account data and payments, a company only needing one of those two capabilities is still evaluating a broader platform than it may need
  • Regulatory dependence on PSD2 and UK open banking rules means the underlying legal framework, not just Yapily's product, could shift and affect what is possible on the platform

How much do Dataiku and Yapily cost?

Dataiku is free to use; Yapily is free to use. Plan by plan below, from each vendor's own pricing page.

Dataiku

Free
  • Free EditionFree
    • Single user
    • Core features
  • EnterpriseFree
    • Full platform
    • Collaboration
    • MLOps

Yapily

Free
  • SandboxFree
    • Free testing environment
    • UK and European bank connections for development
  • ProductionOn request
    • Pay-as-you-go pricing, exact rates not published
    • Typical pay-by-bank cost of 0.1 to 0.5% or a flat 5 to 30 pence per transaction

Which should you pick?

Choose Dataiku if

  • You need visual flow.
  • You want to start without paying.
  • You work on Linux, macOS, Windows, Web.
  • You also want visual recipes.

Choose Yapily if

  • You need unified open banking api.
  • You want to start without paying.
  • You work on Web, API.
  • You also want account information access.

Questions people ask

Is Dataiku or Yapily better?
Neither clearly leads. Dataiku starts at Free and Yapily at Free, and user ratings are close enough to be indistinguishable. Choose on capability and platform support.
Which is cheaper, Dataiku or Yapily?
Dataiku starts at Free and Yapily at Free.
Does Dataiku or Yapily run on more platforms?
Dataiku runs on Linux, macOS, Windows, Web. Yapily runs on Web, API.
Can I use Dataiku for free?
Both have a free tier, so you can try either at no cost before committing.
What is Dataiku best used for?
Dataiku is most often used for organisations where analysts and data scientists must collaborate on the same pipeline rather than exchanging extracts, regulated model risk environments needing documented lineage, sign-off and a record of how a production model was produced, pushing heavy transformations down into a cloud warehouse while keeping the pipeline definition in one reviewable place, large enterprises replacing a sprawl of spreadsheets and unmanaged scripts with something a governance function will accept. Of those, organisations where analysts and data scientists must collaborate on the same pipeline rather than exchanging extracts and regulated model risk environments needing documented lineage, sign-off and a record of how a production model was produced are not what Yapily is typically brought in for.
What can Dataiku do that Yapily cannot?
Dataiku covers Visual Flow, Visual recipes, Code recipes and notebooks, Computation pushdown. Yapily covers Unified open banking API, Account information access, Payment initiation, Free sandbox.

Answered from the vendors’ own pages

Dataiku: Is there a free version?

There is a free edition with limits on users and features, adequate for evaluation and personal work. Anything a team runs in production is a negotiated commercial agreement.

Yapily: Is there a free way to try it?

Yes, sandbox access is free for development and testing.

Dataiku: Do I have to write code to use it?

No. That is the premise. An analyst can build a complete pipeline through visual recipes, and a data scientist can write Python next to it in the same Flow.

Yapily: How much cheaper is pay-by-bank than card payments?

Typically 0.1 to 0.5% of transaction value, or a flat 5 to 30 pence, against 1.5 to 3.5% for card scheme fees.

Dataiku: Where does the computation actually run?

Wherever you connect it. Transformations are pushed down into the warehouse, database or Spark cluster where the data lives, which is efficient and also means the compute cost appears on that provider's bill rather than Dataiku's.

Yapily: Is production pricing published?

No, production access is pay-as-you-go but exact rates require a sales conversation.

Dataiku: Can I export my work if we leave?

Code recipes are your code and leave with you. Visual recipes do not export as equivalent code, so the visual portion of a Flow has to be reimplemented, and that portion tends to be the majority in the projects where the platform succeeded best.

Dataiku: Self-hosted or cloud?

Both are offered. Self-hosting gives control over data residency and networking and requires an administrator; the managed cloud removes that work and moves the constraint to what the vendor's environment supports.

Share

Related pages

Other head to heads