Execution Under Load
Stay steady when demand spikes. Keep critical flows moving.
Keep execution-critical workflows moving on Solana with consistent reliability and clear control, even under load.
A calmer, more reliable path to execution when demand spikes.
Stay steady when demand spikes. Keep critical flows moving.
Plan around consistent results, not best-effort delivery.
Keep authority over what matters most when the system is busy.
Handle high demand without degrading experience or confidence.
When demand spikes, outcomes become less predictable. Priority and protection are not built into the public endpoint.
During contention, your transactions compete with unrelated traffic. Timing and ordering become variable.
Public broadcast reveals intent before execution, enabling copying and reordering.
No built-in priority signals or protection controls at the endpoint.
AURA adds a controlled submission layer built for predictable execution.
AURA sits between your client and the Solana network, built for reliability under load.
A quick look at the product experience: fast feedback, clear protection, and calm execution under load.
Paste a payload and get a signature back in moments. Fast feedback with a clean, drop-in workflow.
Not run yet
Enable protection with a simple indicator. No extra setup, no added friction.
Protection signal detected
When demand spikes, a priority signal helps keep placement predictable without breaking fairness.
AURA establishes a controlled boundary for protected submission.
Detected at the relay layer and routed through the protected path.
Protection controls exposure. Priority controls execution.
When demand exceeds capacity, transactions must be scheduled to preserve predictable execution.
Priority model
Tips act as scheduling signals. Higher tips are processed earlier during contention. When the network is uncongested, the signal has no practical effect.
Works with a familiar workflow. No rebuild required.
AURA provides a familiar interface compatible with existing Solana tooling.
Endpoints are available in multiple regions.
{
"protocol": "2.0",
"id": 1,
"method": "sendTransaction",
"params": ["<SIGNED_TX_BASE64>", { "encoding": "base64" }]
}
Transactions must include a minimum transfer of 0.001 SOL to one of the following AURA accounts.
aura2NHPnnLkPWPXkcqeHkRisDT2b8vy76eMgXH6TsL
auraMDpDVVWxwrJDtBz3Nhog4WGtbrGK2v8y3Pda7ei
auraMkDXGTE678N8LX6cqSV5JJKDpgavVcubPudaVrs
auraSRE5x8CMKbPKto1AkWjLaH4SowAJeAfGqAtdmDC
aurahN2ezg2Ktb2vrDVWqe9yunSZJajzPNTevECSGV4
aurajDJ4Eoq7L6AW36frV8PrrSjf6WMfDjEraU5iFPC
aurarguyidxqBCVtDdoi1FiKrFr3CyyNELGPaU2MWLy
Select any one account per transaction.
Endpoints are regionally deployed for low-latency access.
http://62.113.194.74:5000
http://84.32.64.135:5000
Coming soon
Designed to fit your existing workflow. No accounts. No SDKs.