Solana Transaction Sender.
Delivered, not attempted.

Glaive sends Solana transactions directly to current and upcoming leaders via dedicated connections. No public RPC queues, no wasted bandwidth.

Get Started Read the docs →

# Send a transaction via Glaive
curl "http://ams1.glaive.trade?key=$GLAIVE_KEY" \
  -X POST \
  -H "Content-Type: application/json" \
  -d '{
    "jsonrpc": "2.0",
    "id": 1,
    "method": "sendTransaction",
    "params": ["<base64-encoded-tx>"]
  }'

Direct Validator Connections

Persistent streams to current slot leaders. Your Solana transactions skip the public TPU queue entirely and land in the validator's processing pipeline.

Intelligent Fanout

Glaive tracks the leader schedule in real time and sends each transaction to the current leader plus the next N upcoming leaders, maximizing inclusion probability.

Low-Latency Delivery

Built from the ground up for speed. Microsecond-level overhead per transaction, not milliseconds.

How it works

  Your App
      │
      │  JSON-RPC / sendTransaction
      ▼
  ┌──────────┐
  │  Glaive   │   ← authenticates, validates, rate-limits
  └──────────┘
      │
      ├────────▶  Leader slot N     (current)
      ├────────▶  Leader slot N+1   (upcoming)
      ├────────▶  Leader slot N+2   (upcoming)
      └────────▶  Leader slot N+3   (upcoming)

DIRECT

No public RPC queues

JSON-RPC

Drop-in compatible endpoint

PER-KEY

Individual rate limiting

MULTI-REGION

Deploy closest to your users

Send Solana transactions in three lines

Use your existing Solana tooling. Just point your RPC endpoint at Glaive.

app.ts

import { Connection, Transaction } from "@solana/web3.js";

// Point at Glaive instead of a public RPC
const connection = new Connection(
  `http://ams1.glaive.trade?key=${process.env.GLAIVE_KEY}`
);

// Everything else stays the same
const sig = await sendAndConfirmTransaction(connection, tx, [payer]);