Meet Zela: Remote Procedure Execution (RPE) for Solana
What is Zela?
Zela (Zero Latency) is a remote procedure execution platform designed for projects and companies that need to read and write to the blockchain at the fastest possible speed.
Multi-step on-chain workflows run as a single near-producer call instead of many RPC call round-trips between your backend and remote RPC nodes.
This removes most of the network latency between your app and Solana blockchain, speeding up execution and lowering overall complexity.
Speed and simplicity on Solana.
// IBRL
How it works:
→ Your backend makes a single call with parameters.
→ Zela executes your procedure next to the validator – it can read state, perform the computation, and, if needed, submit a transaction.
→ The platform then returns one response instead of forcing you to stitch together multiple RPC calls over a long path between your backend and the chain.
Deploy latency-sensitive procedures next to current Solana block proposer, so your hot paths skip the long trip from your backend to the validator, as if you were physically colocated.
Send RPC calls with a single Zela procedure that runs the full logic remotely and returns one result. No more multiple calls and jitter issues that come along with it.
Point your most critical, latency-sensitive workflow to Zela and ship performance gains immediately. You can plug in additional services over time, no full migration required.
Spend less time tweaking the network layer, retries, and timeouts; focus on strategy while Zela handles placement, execution, and observability of your code.
// IBRL
How Zela works:
You connect your GitHub repo, pick a package, and Zela builds a sandboxed procedure, deploys it globally, and serves it through a single API endpoint for your backend.
Your backend makes a single call with parameters and Zela ensures that your code is executed near the current block producer.
You procedure can then read fresh state, perform the computation, and, if needed, submit a transaction. It then returns one response instead of forcing you to stitch together multiple RPC calls over a long path between your backend and the chain.
RPC vs RPE
RPC is how you talk to the chain; RPE is how you act on the chain fast enough to matter.