Full-stack Bitcoin Ord Indexer Deployment for NFT, BRC-20, and Runes

When working with the Ordinals protocol, a common issue is that after installing ord, synchronization hangs, the API doesn't respond, or the indexer starts lagging behind the network. This is critical for projects using BRC-20 or Runes, where a delay of a few blocks can cause financial losses due to missed transactions.

We have extensive experience in blockchain infrastructure and have deployed dozens of Ord indexers in production. We know how to avoid typical pitfalls: misconfigured Bitcoin Core, insufficient disk space, vulnerable open API. We offer a turnkey service: set up a Bitcoin Core node, install and optimize ord, configure monitoring, and hand over documentation.

When is a custom Ord indexer needed?

If you work with ordinals, the standard tool is a public RPC. But under high load, security requirements, or the need to process thousands of requests per second, a custom indexer is the only solution. It gives full control over data and eliminates dependence on external services.

What is ord and how does it work?

ord is the reference implementation of an ordinal indexer by Casey Rodarmor. It performs three tasks: tracks satoshi movements via FIFO rules, parses inscriptions from witness data, and provides an HTTP API for queries. Without your own indexer, you cannot get up-to-date data on NFT collections, BRC-20 balances, or Runes.

Important: ord requires a local Bitcoin Core node with txindex=1 enabled and ZMQ channels. Public RPCs won't work.

How we deploy an Ord indexer

Our standard process includes:

1. Server preparation — check specs (NVMe SSD, 32GB RAM, 4+ vCPU), install Bitcoin Core 26+ with optimal parameters.
2. Install ord — latest stable release from GitHub releases (Linux build, Docker, or binary).
3. Configure — set RPC parameters, data paths, ports. Use systemd or Docker Compose.
4. Initial sync — full indexing of all blocks (takes 3–7 days). We monitor progress and optimize batch size.
5. Launch HTTP API — with access restrictions (firewall, nginx reverse proxy with SSL).
6. Integrate monitoring — alert on lag >1 block, disk space checks, logs in Loki.
7. Handover — documentation, credentials, update instructions.

Timeline: from 3 business days to 2 weeks, depending on complexity.

Real case: For a DeFi project with Runes, we deployed a cluster of three indexers with load balancing. Lag never exceeded 2 blocks in six months.

Which indexer to choose?

ord processes requests 2x faster than OPI for basic operations, as confirmed by our production measurements.

Risks of self-deployment

Without experience, you may encounter:

• Insufficient disk space — the ord index grows 5–10 GB per month; many allocate partition without headroom.
• Sync errors — power outage or node restart can corrupt the index.
• API vulnerabilities — open port 80 without authentication invites attacks.

Cost savings: Our support is significantly cheaper than hiring a full-time engineer. Self-setup may lead to extra costs from downtime.

Typical mistakes when setting up yourself

• Using HDD instead of NVMe: synchronization takes weeks.
• Missing txindex=1 — ord won't work.
• Ignoring firewall: API becomes public.

What's included in the service

Why choose us?

• Extensive experience in Web3 development, over 30 projects with Ordinals and Bitcoin L2.
• Certified engineers (Bitcoin Core contributor, smart contract auditor).
• Guaranteed 99.9% uptime for the indexer (under standard load).
• Transparent process — Infrastructure as Code (Terraform, Ansible).

Contact us to discuss your project. Get a consultation on deploying an Ord indexer.