Let’s be honest: building cross-chain infrastructure is still harder than it should be, especially once you care about UX, reliability, and control.

If you run a web3 dApp, you usually have two choices. You can burn engineering cycles maintaining custom integrations for 15+ bridges (which inevitably break at the worst time). Or you can ship a generic third-party cross-chain widget that lives in an iframe, behaves like a black box, and quietly degrades your UX.

We weren’t happy shipping brittle integrations or opaque widgets, so we built the execution layer we wanted to embed ourselves.

Velora is a cross-chain execution layer for web3 dApps that embeds directly into React frontends. It replaces iframe-based cross-chain widgets with native components, giving teams execution control, analytics visibility, and customization without operational overhead.

Velora Cross-chain Widget is the same execution infrastructure powering our own $150B+ volume, packaged for your frontend.

Why Velora

Most cross-chain widgets make integration easy by flattening execution into a single swap flow. Velora takes a different approach: it preserves execution choice at the UI layer.

Teams can expose hybrid execution modes (instant or intent-based), MEV-aware routing, cross-chain limit orders, gasless flows, full BUY and SELL support, and large-trade paths like P2P-style liquidity — without building or maintaining the underlying infrastructure. The result is a cross-chain widget that’s easy to embed, but doesn’t force you to compromise on execution quality, control, or user outcomes.

Native React > iFrames

It’s not a widget in the traditional sense — it’s an execution layer exposed as a native component.

Most cross-chain widgets are glorified iframes. They load slowly, sandbox your UI, block analytics, and feel like foreign objects glued onto the DOM.

We ship as a native React component because teams want full control over state, styling, and behavior — without maintaining cross-chain logic themselves. The component compiles directly into your build, shares state with your app, and inherits your CSS variables.

It doesn’t sit on your interface; it is your interface.

Drop it in, then dial it exactly as far as you need — from opinionated defaults to fully customized cross-chain execution.

import { Widget } from "@velora-dex/widget";
function App() {
  return (
    <Widget
      config={{
        theme: "light", // Inherits your CSS variables
        enableCrossChain: true,
        tradeMode: ["swap", "limit", "otc"], // Enable modules without changing your integration
        partner: "your-partner-id",
      }}
      provider={window.ethereum}
    />
  );
}

Most teams start with defaults and progressively unlock features as their product matures — no re-architecture required.

"God-Mode" Routing (Hybrid Cross-Chain Execution)

Your users don’t care how many bridges are involved — they care about speed, price, and certainty.

Under the hood, the widget connects to our Hybrid Execution Engine. We route across public bridges and liquidity sources, then selectively blend in private execution paths (agents and market makers) when it improves the outcome.

We don’t collapse everything into a single “swap.” We optimize based on context:

• MEV-aware execution: Orders avoid the public mempool and route through private auctions by default

• Hybrid execution: Switches between instant aggregation and intent-based routing depending on trade size

• Gasless flows: Enables sponsored execution where it improves conversion

• Full intent support: Native BUY and SELL flows, including cross-chain limit orders, not just swaps

• Large trade handling: Access P2P-style liquidity paths designed for size without market impact

Most widgets simplify execution to make integration easier; we make integration easy without simplifying execution.

As market conditions change, execution strategies evolve — the widget adapts without requiring changes to your frontend.

The Analytics Gap

One of the biggest hidden costs of iframe-based widgets is the data black hole. The moment a user interacts with an iframe, they disappear from your analytics.

Because Velora is native, it plugs directly into your existing analytics stack — including Safary, Mixpanel, and Google Analytics. You get full visibility into the user journey, custom events, and drop-offs.

You own the user. You should own the data.

Infrastructure That Pays

Integration shouldn’t just be easier — it should align incentives.

Velora includes a native fee-sharing module. Toggle feeSharing in the config and start capturing a percentage of surplus or partner fees generated by your cross-chain flow, without adding complexity to your stack.

For teams building DEXs or wallets, this means shipping cross-chain execution in days, not months — without owning bridge integrations or routing logic.

Get Access

We’re rolling this out in limited release to a small group of DEXs, wallets, and agent builders. The goal is simple: ensure every integration is production-grade before opening it up more broadly.

If you’re ready to stop building bridges and start embedding execution, let’s talk!