Softwr

APIs · head to head

Apollo GraphQL vs Neonomics

Apollo GraphQL logo

Apollo GraphQL

APIs

GraphQL platform and API orchestration layer for building unified graphs

From
Free
Rated
-
Neonomics logo

Neonomics

APIs

Nordic open banking payments and data, now with UK coverage through Ordo

From
On request
Rated
-

The short version

  • Only Apollo GraphQL has a free tier, so it costs nothing to try first.
  • Each has a real cost: Apollo GraphQL pricing beyond the Developer tier requires contacting sales, making cost comparison harder for mid-size teams.; Neonomics coverage outside the Nordics and the UK is comparatively shallow, so a pan European merchant will find gaps and inconsistent bank behaviour in southern and eastern markets.
  • They diverge on capability: Apollo GraphQL covers Apollo Connectors, Neonomics covers Payment initiation.
  • Prices and features above were last checked on 1 September 2026.

Where they differ

Only the attributes on which Apollo GraphQL and Neonomics actually diverge.

Attributes where Apollo GraphQL and Neonomics differ
AttributeApollo GraphQLNeonomics
Starting priceFreeOn request
Pricing modelfreemiumquote
Free tierYesNo

Identical on both: platforms (web, api), user rating (Not yet rated), category (APIs).

What each one covers

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 Apollo GraphQL

  • Apollo Connectors
  • GraphOS Router
  • Schema registry
  • Schema checks
  • Response caching
  • Audit logging

Only in Neonomics

  • Payment initiation
  • Account information
  • Nordic bank depth
  • UK coverage via Ordo
  • Variable recurring payments
  • Request to pay
  • White label journeys
  • Reconciliation data

What people use each for

The jobs each tool is most often brought in to do.

Apollo GraphQL

  • Federating multiple backend services into one GraphQL APInot Neonomics
  • Wrapping legacy REST APIs for frontend consumptionnot Neonomics
  • Enterprise API governance with schema checks and audit logsnot Neonomics
  • Reducing frontend over-fetching and under-fetching of datanot Neonomics

Neonomics

  • A Norwegian or Swedish merchant collecting payments directly from bank accounts to avoid card feesnot Apollo GraphQL
  • A debt collection agency sending request to pay messages instead of chasing bank transfers manuallynot Apollo GraphQL
  • A software vendor embedding pay by bank into an accounting or invoicing product for Nordic customersnot Apollo GraphQL
  • A business needing both UK and Nordic bank payment coverage from one suppliernot Apollo GraphQL

Where each one falls short

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

Apollo GraphQL

  • Pricing beyond the Developer tier requires contacting sales, making cost comparison harder for mid-size teams.
  • Adopting GraphOS effectively requires buy-in to the GraphQL paradigm, which is a larger architectural shift than adding a REST gateway.
  • The free plan's 1-day data retention and 60 req/min self-hosted router limit make it unsuitable for production use.
  • Volume-based per-request pricing can become expensive at very high request volumes compared to flat-rate API gateways.

Neonomics

  • Coverage outside the Nordics and the UK is comparatively shallow, so a pan European merchant will find gaps and inconsistent bank behaviour in southern and eastern markets.
  • It is a small company relative to Tink and TrueLayer, so supplier viability and the depth of engineering support behind bank API changes are genuine procurement questions.
  • Payment initiation only means the merchant handles settlement, reconciliation and refunds, and there is no chargeback framework to fall back on.
  • Integrating a recently acquired UK business means two regulatory entities and, for a period, two technology stacks, so cross market feature parity is a promise rather than an existing state.
  • Conversion is governed by each bank's own authentication experience, and Nordic BankID flows behave differently from UK app redirects, so a single UX cannot be assumed across the footprint.

Pricing, plan by plan

Apollo GraphQL

Free
  • FreeFree
    • Up to 3 developers
    • 1-day data retention
    • Community support
  • Developer$5/month
    • $5 per million requests with volume discounts
    • $50 usage credit for new signups
    • Up to 10 developers
  • Standard$undefined/month
    • Up to 30 developers
    • 90-day data retention
    • Standard support with SLA
  • Enterprise$undefined/month
    • Unlimited developers
    • 18-month data retention
    • 24x7x365 support with SLA

Neonomics

On request
  • Neonomics platform$undefined/year
    • Quoted per customer, typically per initiated payment or per API call
    • Volume commitments and monthly minimums are common
    • Payment initiation only; merchant handles settlement and refunds

Which should you pick?

Choose Apollo GraphQL if

  • You need apollo connectors.
  • You want to start without paying.
  • You work on web, api.
  • You also want graphos router.

Choose Neonomics if

  • You need payment initiation.
  • You work on Web, API.
  • You also want account information.

Questions people ask

Is Apollo GraphQL or Neonomics better?
Neither clearly leads. Apollo GraphQL starts at Free and Neonomics at On request, and user ratings are close enough to be indistinguishable. Choose on capability and platform support.
Which is cheaper, Apollo GraphQL or Neonomics?
Apollo GraphQL has a free tier; the other does not. Paid plans start at Free for Apollo GraphQL and On request for Neonomics.
Does Apollo GraphQL or Neonomics run on more platforms?
Apollo GraphQL runs on web, api. Neonomics runs on Web, API.
Can I use Apollo GraphQL for free?
Yes. Apollo GraphQL has a free tier, so you can try it without paying. Neonomics starts at On request.
What is Apollo GraphQL best used for?
Apollo GraphQL is most often used for federating multiple backend services into one graphql api, wrapping legacy rest apis for frontend consumption, enterprise api governance with schema checks and audit logs, reducing frontend over-fetching and under-fetching of data. Of those, federating multiple backend services into one graphql api and wrapping legacy rest apis for frontend consumption are not what Neonomics is typically brought in for.
What can Apollo GraphQL do that Neonomics cannot?
Apollo GraphQL covers Apollo Connectors, GraphOS Router, Schema registry, Schema checks. Neonomics covers Payment initiation, Account information, Nordic bank depth, UK coverage via Ordo.

Answered from the vendors’ own pages

Apollo GraphQL: What does Apollo GraphQL cost?

The Free plan supports up to 3 developers at no cost. Developer plan starts at $5 per million requests with a $50 signup credit, while Standard and Enterprise require contacting sales for custom pricing.

Source
Neonomics: Is Neonomics authorised in the UK?

Yes, through the acquisition of Ordo, an FCA authorised open banking payments firm, approved by the FCA and the Norwegian regulator.

Apollo GraphQL: Is there a free plan and what are its limits?

Yes, the Free 'Forever Free' plan supports up to 3 developers, 1-day data retention for checks and insights, and a self-hosted router capped at 60 requests per minute.

Source
Neonomics: Does it support variable recurring payments?

Yes in the UK through the Ordo capability, subject to which banks support commercial VRP; support elsewhere is more limited.

Apollo GraphQL: How is usage metered on paid plans?

Standard requests are billed per million operations with tiered volume discounts, starting at $5.00/million for the first 250M and dropping to $3.00/million beyond 5B, with similar tiered pricing for subscription update events.

Source
Neonomics: Does Neonomics hold merchant funds?

No. It initiates payments; settlement, reconciliation and refunds remain with the merchant or its payment provider.

Share

Related pages

Other head to heads