Quickstart for Enterprise
Enterprise blockchain infrastructure requires the same standards as traditional IT infrastructure — access control, audit trails, and SLA guarantees. This page outlines the adoption path from PoC to dedicated infrastructure, and describes the enterprise features available at each stage.
Onboarding
The recommended adoption path is to run a PoC on Elastic Node, then transition to Dedicated Node based on your requirements. Validating API integration, security configuration, and audit features in an Elastic Node environment before switching to dedicated infrastructure reduces deployment risk.
Step 1: Start Your PoC with Elastic Node
Create a project in the Nodit Console and validate node integration in the Elastic Node (shared node pool) environment. No contract or account manager coordination is required to get started, and 99.9% SLA is guaranteed. Use Node API to verify block queries, transaction submission, and other node-level integrations, and measure real traffic patterns and response performance.
Step 2: Expand Services and Configure Your Operating Environment
After validating node integration, connect additional services such as Web3 Data API and Webhook, and configure security and audit settings — including IP Allowlist, Team Account, and Request Logs — from the console.
Step 3: Transition to Dedicated Node
Dedicated Node is recommended when any of the following requirements apply. The integration configuration validated during your PoC can be carried over as-is.
- You need to handle large-scale traffic that exceeds the per-plan request limits.
- You require fully isolated infrastructure, completely separate from other users.
- Your security audit requires evidence of dedicated infrastructure operation.
1. PoC — Getting Started with Elastic Node
Creating a project in the Nodit Console lets you begin node integration immediately in the Elastic Node (shared node pool) environment. No contract or account manager coordination is needed, so technical validation can proceed before internal decision-making.
Elastic Node is a node infrastructure service that provides access to blockchain networks without building your own node. Through Node API (JSON-RPC and similar interfaces) provided by the node client, you can validate node-level integrations including block queries, transaction submission, and smart contract calls.
The following items can be validated during the PoC phase:
- Node API Integration Validation — Access blockchain nodes through Elastic Node and verify that Node API (JSON-RPC) calls are compatible with your existing systems. Node-level functionality including block queries, transaction submission, and smart contract calls can be tested.
- Traffic Pattern Analysis — Measure actual Node API call patterns and response performance to establish a baseline for sizing Dedicated Node specifications when you transition.
Elastic Node guarantees 99.9% SLA. If mid-scale traffic and standard SLA are sufficient for your operational requirements, you can continue running on Elastic Node beyond the PoC phase.
API integration methods are covered in Quickstart for Developers. API authentication and call structure are described in API Overview.
2. Expanding Services and Configuring Your Operating Environment
After validating node integration, connect additional Nodit services and configure the security and audit environment required for enterprise operations. The service integrations and security configurations established in this phase are preserved when you later transition to Dedicated Node.
Web3 Data API / Webhook
While Node API exposes the node client's JSON-RPC interface directly, Web3 Data API and Webhook are separate services that process on-chain data into formats suitable for enterprise systems. They operate independently of the node infrastructure (Elastic Node / Dedicated Node), so switching nodes does not affect existing integrations.
- Web3 Data API — Indexes on-chain data and retrieves token balances by account, NFT holdings, transaction history, and more in a structured format. Business logic can consume the data directly without parsing raw node output.
- Webhook — Sends real-time notifications to a specified endpoint when specific on-chain events occur (transaction confirmation, token transfer, etc.). Event-driven integration eliminates polling, reducing response latency and unnecessary API calls.
Access Control
API call origins can be restricted by Domain Name and Source IP. Activate the Allowlist in the Security tab of the project detail view and add entries — requests from unregistered origins are blocked with an HTTP 403 error.
- Domain Name Allowlist — Used to restrict requests originating from web browsers. Only registered domains are permitted to call the API.
- Source IP Allowlist — Used in fixed network environments such as server-to-server communication. Only registered IP addresses are permitted to call the API.
Each Allowlist supports up to 25 entries. Configuration details are available in the Security guide.
Permission — Team Account
Converting a personal account to a team account allows multiple team members to share project resources (API Keys, Webhooks, Request Logs, etc.). Two member types are available — Team Owner and Team Member. Payment method management and plan changes are restricted to Team Owners. Team Members have the same access as Team Owners for all functions except project settings.
Team members can be invited or removed immediately from the console as team composition changes, reducing account management overhead. Configuration details are available in the Team Account guide.
Debugging — Request Logs
Request Logs is a debugging tool that lets you view the API call history and detailed results from the past 7 days in the console. The API type, request and response content, network, and response time are all visible on a single screen, making it straightforward to identify the cause of issues.
Logs can be filtered by network, time range, HTTP status, error code, and other criteria to extract the records you need. This tool is useful for tracking API integration errors during the PoC phase or verifying unexpected responses in production. Usage details are available in the Request Logs guide.
3. Transitioning to Dedicated Node
Dedicated Node is recommended when any of the following requirements apply.
- Large-Scale Traffic — When traffic exceeds the per-plan request limits of Elastic Node and must be handled reliably, a dedicated node sized to custom specifications is required.
- Infrastructure Isolation — When the node must run in an environment fully isolated from other users' traffic, Dedicated Node allocates resources independently within dedicated, isolated infrastructure.
- Security Audit Compliance — When evidence of dedicated infrastructure operation or additional security audit support is required, this can be addressed through a contract-based arrangement.
The integration configuration validated during your PoC can be carried over as-is; only the node infrastructure is subject to the transition. Services integrated in Step 2 — such as Web3 Data API and Webhook — are unaffected and continue operating without interruption.
Elastic Node vs. Dedicated Node
| Elastic Node | Dedicated Node | |
|---|---|---|
| Infrastructure | Shared node pool | Dedicated, isolated infrastructure |
| SLA | 99.9% | 99.9% or higher (contract-based) |
| Traffic | Per-plan request limits | Custom-sized specifications |
| Monitoring | Shared dashboard | Dedicated monitoring environment |
| Security Audit | Standard | Additional support available |
| Best For | PoC, startups, mid-scale teams | Financial institutions, large enterprises |
Adoption Process
Dedicated Node adoption follows a five-step process from requirements consultation to go-live. A dedicated account manager provides technical, integration, and operational support at each stage.
- Requirements Consultation — Discuss the networks to use, expected traffic volume, and security requirements (IP Allowlist, audit compliance, etc.). Sharing the traffic patterns and API usage data gathered during your PoC accelerates specification sizing.
- Infrastructure Design and Quotation — Based on the agreed requirements, dedicated node specifications and costs are determined. An optimal configuration is proposed considering factors such as the number of networks, concurrent request volume, and data retention period.
- Dedicated Node Provisioning — The node is deployed and configured in an isolated environment. The API Key and endpoint configuration used in your existing Elastic Node setup can be preserved.
- Integration and Monitoring Setup — Endpoint integration, access control settings, and a dedicated monitoring dashboard are configured. IP Allowlist and Team Account settings from your PoC environment can be migrated as-is.
- Go-Live and Ongoing Support — Technical issues and specification change requests that arise during operations are handled by the account manager. Capacity expansion in response to traffic growth can also be requested post-launch.
Full details are available in the Dedicated Node guide.
Contact
For Dedicated Node adoption, Scope consulting, or other enterprise requirements, reach out through the following channels.
- Email: [email protected]
- Contact Form: Submit a consultation request through the Nodit contact page.
A PoC can be started immediately from the Nodit Console. For Dedicated Node adoption or Scope consulting, reach out through the enterprise contact page to start a conversation.