RKV
RUKAV Signal execution infrastructure API · WebSocket · sub-second routing v1.0 Multi-venue

Signal
execution,
not guesswork.

→ Rukav routes signals from TradingView, Telegram, or a direct webhook into orders on your own exchange account.
→ Native multi-target TP, SL, trailing, position sizing, split entries — applied deterministically to every fill.
→ Sub-second order placement over WebSocket. You keep custody, the keys, and the audit trail.

Median routing
< 800 ms
Withdraw scope
Never required
Evaluation
14 days
Open account → Continue with Google
SEC.01 / PIPELINE

Three stages. Deterministic.

Onboarding: ~5 min
Integration: no code
Custody: stays with you
01

Connect a venue

Issue a trade-scoped API key on Binance, Bybit, OKX, Kraken, or Bitget and paste it once. Withdraw permission is never requested. Keys are encrypted at rest and revocable from your exchange dashboard.

02

Define execution policy

Wire TradingView webhooks, Telegram channels, or our REST endpoint. Set position sizing, TP allocation, SL strategy, split-entry count, and per-source caps. Policies apply to every signal, end-to-end.

03

Route to fill

Inbound signals are validated, deduplicated, persisted, and dispatched to the exchange over WebSocket. TP and SL brackets are placed atomically; closure is enforced server-side from a tick stream — not from your machine.

SEC.02 / CAPABILITIES

An execution stack built right.

Surface: REST · WebSocket
Latency: sub-second routing
State: persisted, auditable
TP

Multi-target TP allocation

Up to three configurable price targets with weighted size allocation per leg. Brackets are placed atomically alongside the entry — no race window.

SL

Server-side SL enforcement

Hard stop, breakeven on TP1 fill, or trailing. Closure is monitored from an exchange-side tick stream and reconciled against position state.

σ

Risk-aware sizing

Fixed notional, percent of equity, or risk-from-stop-distance. Daily loss cap, per-source caps, per-symbol overrides, max-concurrency.

⧉

Split entries & DCA

Ladder a position across N entries, scale in on confirmation, or replay after a stop. Each leg is tracked independently for P&L attribution.

⏻

Kill switch & dry-run

Disarm in one click — flatten or hold. Every signal can be dry-run end-to-end first; output matches what production would have placed.

⎚

Observability

Every signal, plan, order, and fill is timestamped and queryable. Telegram, email, and webhook hooks on lifecycle events. No black boxes.

SEC.03 / VENUES

Bring your own venue.

Custody: stays with you
Withdraw scope: never granted
Markets: spot + perps
BinanceSpot · Futures
BybitSpot · Futures
OKXSpot · Futures
KrakenSpot · Futures
BitgetSpot · Futures
+ moreon request
SEC.04 / TELEMETRY

Inbound stream, verbatim.

Source: sample feed
Window: rolling 60 s
Display: illustrative
signals.in · rolling Streaming
  • 14:02:11BTCUSDTlong65,432.10@cryptodesk
  • 14:01:48ETHUSDTshort3,108.55@whaleroom
  • 14:01:23SOLUSDTlong143.20@altsignals
  • 14:00:54ARBUSDTlong1.103@cryptodesk
  • 14:00:18DOGEUSDTlong0.1623@memetraders
  • 13:59:42LINKUSDTshort17.20@whaleroom
  • 13:58:30AVAXUSDTlong37.41@altsignals
Signals routed · 24h
1,284
p50 webhook → fill
784ms
API availability · 30d
99.99%
Active accounts
2,400+
SEC.05 / PRICING

Pick a tier.

Billing: monthly · USD
Evaluation: 14 days, no card
Cancellation: self-service
tier · 01

Starter

$014-day evaluation
  • 1 venue connection
  • Up to 3 signal sources
  • TP / SL / trailing
  • Dry-run execution
  • Email support
Open account →
Most popular tier · 02

Trader

$39/ month
  • Up to 3 venue connections
  • Unlimited signal sources
  • Multi-target TP allocation
  • Risk-based sizing & split entries
  • Dry-run + live execution
  • Daily loss limits & kill switch
  • Priority support
Open account →
tier · 03

Pro

$99/ month
  • Unlimited venues
  • Unlimited sources
  • Custom webhook integrations
  • Sub-accounts & segregated keys
  • Programmatic REST access
  • Trade history export · CSV / JSON
  • Dedicated channel
Open account →
SEC.06 / FAQ

Common questions.

Further detail?
Engineering docs are available
once you're signed in.
What custody model does Rukav use?
None. Funds stay on your exchange. Rukav authenticates with a trade-scoped API key — withdraw permission is never requested or used. Keys are encrypted at rest and can be revoked from your exchange dashboard at any time.
Which venues are supported?
Binance, Bybit, OKX, Kraken, and Bitget — spot and perpetuals. Additional venues are integrated on request from the Pro tier. Our order placer uses WebSocket where the venue supports it and falls back to REST otherwise.
What signal sources are accepted?
TradingView webhooks (shared-secret authenticated), Telegram channels you administer or follow, and a direct REST endpoint for custom strategies. Every inbound signal is validated against a schema, deduplicated by content hash, and persisted before dispatch.
How is execution validated before going live?
Every signal can be replayed in dry-run mode end-to-end: the gateway resolves position size, computes brackets, builds the order payload, and emits the same lifecycle events — without placing a real order. The dry-run output matches what production would have submitted.
Where does the service run?
On dedicated infrastructure inside a Kubernetes cluster colocated near major exchange APIs. The gateway, executor, and bot are independent services with mTLS between them. No client-side runtime; signals are processed even when you're offline.
What happens on cancellation?
Self-service from your account. Existing positions remain on your exchange and continue to be managed until close or until you revoke the API key. Access ends at the close of the billing period. Trade history remains exportable for 90 days after cancellation.

Signal in.
Order out.

Rukav is in private launch. Sign in to provision an account and start a 14-day evaluation — no card, no commitment.

Open account → Continue with Google