APIs · head to head
Hasura vs i2c

Hasura
APIs
GraphQL engine that instantly creates production-ready GraphQL API from databases
- From
- Free
- Rated
- -

i2c
APIs
Configurable card issuing and banking processing platform for banks and programme managers
- From
- On request
- Rated
- -
The short version
- Only Hasura has a free tier, so it costs nothing to try first.
- Each has a real cost: Hasura active model definition: model/command accessed more than 1,000 times monthly; i2c developer experience lags API-native competitors, and teams expecting Stripe-grade documentation and sandboxes find an enterprise integration project instead.
- They diverge on capability: Hasura covers GraphQL API, i2c covers Configurable product engine.
- Prices and features above were last checked on 1 September 2026.
Where they differ
Only the attributes on which Hasura and i2c actually diverge.
Identical on both: 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 Hasura
- GraphQL API
- Real-time subscriptions
- Access control
- PostgreSQL
- MySQL
- Webhooks
- REST APIs
- Cloud support
Only in i2c
- Configurable product engine
- Credit and instalments
- Multi-currency
- Fraud and risk tooling
- Digital banking front ends
- Global scheme connectivity
What people use each for
The jobs each tool is most often brought in to do.
Hasura
- Automatic GraphQL API generation from existing databasesnot i2c
- Real-time data subscriptions for modern applicationsnot i2c
- Backend infrastructure for web and mobile applicationsnot i2c
- Event-triggered webhooks for database changesnot i2c
i2c
- A bank wanting credit, debit and prepaid portfolios on one processor rather than threenot Hasura
- An issuer in a market where local scheme and currency support rules out US-centric processorsnot Hasura
- A programme manager launching instalment products without building a lending corenot Hasura
- A credit union replacing an ageing processor without writing custom code for product rulesnot Hasura
Where each one falls short
Documented limitations, not opinions. Every one is a constraint you would hit in normal use.
Hasura
- Active model definition: model/command accessed more than 1,000 times monthly
- Private DDN requires Base or Advanced plan
i2c
- Developer experience lags API-native competitors, and teams expecting Stripe-grade documentation and sandboxes find an enterprise integration project instead.
- Implementations lean on i2c or partner professional services, so timelines and costs are set by a services queue rather than by your own engineering speed.
- Pricing is per active card and per transaction with monthly minimums, none of it published, so comparing bids requires modelling your own portfolio carefully.
- Configuration flexibility means product behaviour lives in platform settings rather than in your repository, which complicates version control, testing and audit trails.
- As a private company with a broad global footprint, regional support depth is uneven, and a programme in a smaller market may get thinner service than a flagship account.
Pricing, plan by plan
Hasura
Free- DDN FreeFree
- Unlimited models
- 1 supergraph developer
- 15-minute observability retention
- DDN Base$5/month
- Per active model billing
- Unlimited developers
- 30-day observability retention
- DDN Advanced$30/month
- Per active model billing
- Federated collaboration
- Multi-repo CI/CD
i2c
On request- i2c processing platform$undefined/year
- Per-active-card and per-transaction processing fees
- Minimum monthly commitments by programme
- Implementation and configuration professional services
Which should you pick?
Choose Hasura if
- You need graphql api.
- You want to start without paying.
- You also want real-time subscriptions.
Choose i2c if
- You need configurable product engine.
- You work on Web, REST API.
- You also want credit and instalments.
Questions people ask
- Is Hasura or i2c better?
- Neither clearly leads. Hasura starts at Free and i2c at On request, and user ratings are close enough to be indistinguishable. Choose on capability and platform support.
- Which is cheaper, Hasura or i2c?
- Hasura has a free tier; the other does not. Paid plans start at Free for Hasura and On request for i2c.
- Does Hasura or i2c run on more platforms?
- Hasura runs on Web. i2c runs on Web, REST API.
- Can I use Hasura for free?
- Yes. Hasura has a free tier, so you can try it without paying. i2c starts at On request.
- What is Hasura best used for?
- Hasura is most often used for automatic graphql api generation from existing databases, real-time data subscriptions for modern applications, backend infrastructure for web and mobile applications, event-triggered webhooks for database changes. Of those, automatic graphql api generation from existing databases and real-time data subscriptions for modern applications are not what i2c is typically brought in for.
- What can Hasura do that i2c cannot?
- Hasura covers GraphQL API, Real-time subscriptions, Access control, PostgreSQL. i2c covers Configurable product engine, Credit and instalments, Multi-currency, Fraud and risk tooling.
Answered from the vendors’ own pages
Hasura: How much does Hasura cost?
Hasura DDN Free is free. DDN Base starts at $5/active model/month, and DDN Advanced starts at $30/active model/month.
Sourcei2c: Does i2c issue the cards itself?
No. It processes; issuance sits with a bank or licensed issuer, and in most markets you need that relationship separately.
Hasura: What is an active model in Hasura pricing?
An active model is defined as any model or command accessed more than 1,000 times monthly.
Sourcei2c: Can it handle revolving credit?
Yes. Credit, instalments and buy-now-pay-later sit on the same platform as debit and prepaid, which is unusual among modern processors.
Hasura: Is there a free version of Hasura?
Yes, Hasura DDN Free is always free and includes unlimited models, 1 supergraph developer, and 15-minute observability retention.
Sourcei2c: Is it self-serve?
No. Expect a configuration-led implementation with professional services rather than signing up and calling an API.
Related pages
Other head to heads
- Hasura vs PocketBase
- Hasura vs Parse Server
- Hasura vs Appwrite
- Hasura vs GraphQL Apollo
- Hasura vs GraphQL Playground
- Hasura vs Directus
- Hasura vs Asyncapi
- Hasura vs Janus Gateway
- Hasura vs Strapi
- Hasura vs Gravitee
- Hasura vs Bruno
- Hasura vs KeystoneJS
- Hasura vs Lithic
- Hasura vs Stoplight
- Hasura vs Swan
- Hasura vs Temenos Transact
- Hasura vs Token.io
- Hasura vs Treasury Prime
- Hasura vs Marqeta
- Hasura vs Enfuce
- Hasura vs Highnote
- Hasura vs Paymentology
- Hasura vs Episode Six
- Hasura vs Tribe Payments
- Hasura vs Mambu
- Hasura vs Skaleet
- Hasura vs Thredd
- Hasura vs 10x Banking
- Hasura vs PubNub
- Hasura vs Svix
- Hasura vs Synctera
- Hasura vs Treblle
- i2c vs PocketBase
- i2c vs Parse Server
- i2c vs Appwrite
- i2c vs GraphQL Apollo
- i2c vs GraphQL Playground
- i2c vs Directus
- i2c vs Asyncapi
- i2c vs Janus Gateway
- i2c vs Strapi
- i2c vs Gravitee
- i2c vs Bruno
- i2c vs KeystoneJS
- i2c vs Lithic
- i2c vs Stoplight
- i2c vs Swan
- i2c vs Temenos Transact
- i2c vs Token.io
- i2c vs Treasury Prime
- i2c vs Marqeta
- i2c vs Enfuce
- i2c vs Highnote
- i2c vs Paymentology
- i2c vs Episode Six
- i2c vs Tribe Payments
- i2c vs Mambu
- i2c vs Skaleet
- i2c vs Thredd
- i2c vs 10x Banking
- i2c vs PubNub
- i2c vs Svix
- i2c vs Synctera
- i2c vs Treblle
