What is our primary use case?
QuickNode Core API serves as our primary RPC access layer to interact with multiple production networks, including Ethereum, Polygon, and Arbitrum, in our digital banking environment where maintaining resilient connectivity across our stack of distributed ledgers is non-negotiable. Rather than deploying and maintaining self-hosted archival and full nodes internally, which demands continuous DevSecOps bandwidth and synchronization monitoring with higher infrastructure overhead, QuickNode Core API saves us considerable time and acts as a unified multi-chain gateway. QuickNode Core API also serves in our backend transaction ingestion engines and assists with wallet balance verification for our AML and KYC forensic teams while aiding us in detecting AI-driven fraud. The AI model significantly contributes to our fraud detection models, making this our primary use case.
Our major factor for choosing QuickNode Core API was the support and the results it has delivered in the past to other clients. We researched this decision in our internal board meetings where we discussed what we should adopt for the organization. QuickNode Core API fit into our consideration by saving a lot of continuous DevSecOps bandwidth, synchronized monitoring, and high infrastructure overhead while serving as a multi-chain gateway. This was our major decision driver for selecting it.
How has it helped my organization?
QuickNode Core API has resulted in faster time to market, reducing the development and deployment cycles by at least 47% to 52%, where we have experienced faster development times, deployments, and deliveries. This delivery impact has positively influenced customer satisfaction, with CSAT levels going up by 40% since we have not encountered any dropouts after implementing the solution. Transactions are smooth, with balances loading instantly for debit, credit, and everything else, resulting in no negative feedback, especially concerning software-related problems.
What is most valuable?
The best features QuickNode Core API offers include low latency and high availability since it is a globally distributed edge network. I have seen at least 99.99% uptime since we configured it in our environments, and I have not seen any downtime so far in those years. It ensures that customers are facing their retail crypto balances loading without any RPC dropouts, which is my favorite.
The second feature is the unified multi-chain endpoint architecture, following a standardized interface across 80+ networks, which drastically reduces the overhead for our development teams by 70% when adding support for new Layer 2 rollups.
The third feature is its adherence to enterprise security standards, supporting SOC 2 Type II compliance and ISO 27001 certification, following all the IP whitelisting and strict API access token control to meet bank-grade cybersecurity audits. Since we are a bank, we have to ensure it has enterprise-level security standards since many money-related transactions are involved. We totally rely upon it and have seen it is completely secure and safe for the organization.
Regarding QuickNode Core API's AI capabilities in governance and security, deploying the autonomous agents and predictive models within the regulated bank environment requires strict AI governance and deterministic execution. It has helped with on-chain ingestion predictive models, and our ML fraud detection and AML anomaly models rely on unmanipulated real-time blockchain telemetry. QuickNode Core API delivers consistent block-level data and archival state access with sub-50ms latency, preventing model drift caused by stale or out-of-sync RPC responses.
As for QuickNode Core API's AI capabilities in terms of accuracy and reliability of output, it has met my expectations at 100%. The AI agent systems managing treasury routing algorithm, reconciliation, and routing to automatic failover eliminate downtime, and the indicating and reporting using AI and ML has proven to be 100% accurate, with no issues on that part.
What needs improvement?
QuickNode Core API is functioning effectively for its intended purpose, and I do not have any suggestions for improvements.
For how long have I used the solution?
I have been using QuickNode Core API in my organization for the last two and a half years.
What do I think about the stability of the solution?
We have not encountered any challenges or glitches, and it is 100% stable.
How are customer service and support?
I would rate customer support a 10 out of 10. There was an incident reported by our internal teams, and they resolved the query within two hours of the reported incident.
Which solution did I use previously and why did I switch?
We did not use a different solution prior to QuickNode Core API.
How was the initial setup?
The deployment process for QuickNode Core API was very easy and was supported by the vendor, integrating into our pipelines within a day or two.
The configuration process was straightforward to set up and manage with the vendor across our internal environments.
Integrations of QuickNode Core API with other AWS services we use are seamless and smooth, and we did not encounter any challenges with integration.
What was our ROI?
QuickNode Core API has positively impacted our organization by yielding substantial ROI and significant operational cost reduction. It has cut self-hosted node infrastructure and specialized SRE maintenance costs by approximately 63.27%, which is a huge reduction. I have also seen a faster time to market, reducing the multi-chain feature release cycles from six weeks down to seven days due to the standardized endpoints and out-of-the-box archival support.
Additionally, we have seen a reliability SLA maintaining uninterrupted API availability at 99.99% in production, significantly reducing the latency-related transaction dropout for our retail users. Earlier, the dropout percentage was around 5%, and it has brought it down to 0.0001%, meaning one in maybe a million users will experience a dropout, which is negligible. This is a huge impact we have seen after implementing it.
What's my experience with pricing, setup cost, and licensing?
The metering and billing experience with QuickNode Core API is quite good, operating on a credit meter consumption model layered over tiered subscription plans, where we choose from Build, Accelerate, and Scale. We lie in the enterprise category and utilize the API credit consumption model rather than being charged flat rates per HTTP request, metering requests via weighted API credits based on simple balance checks and deep archival calls along with trace endpoints.
Which other solutions did I evaluate?
Before choosing QuickNode Core API, we evaluated multiple alternatives, including Alchemy, Infura, and Consensys, confirming that QuickNode Core API is definitely a stable solution.
What other advice do I have?
I would rate QuickNode Core API a five because the ROI, the business impact, and how it is helping us as an organization are truly exceptional, so it deserves a five.
I would suggest anyone looking for a great, solid solution for enterprise-grade deployments in a secure and broader environment should definitely consider QuickNode Core API.
Which deployment model are you using for this solution?
Public Cloud
If public cloud, private cloud, or hybrid cloud, which cloud provider do you use?
