Frequently asked questions

A single-strategy prototype starts at about $600. A full bot with a risk engine, backtesting and Telegram control starts at about $1,800. A production system with a dashboard and multi-account support starts at about $3,600. The exact figure follows a scoping conversation, which is free.

A single-strategy bot is typically 2–4 weeks including testnet. A prototype is 3–5 days. A system with a dashboard and several venues is five weeks and up.

By milestone. The first milestone is deliberately small so both sides can check each other on real work.

No. Scoping and an estimate are free.

Yes, that is the normal case. Your rules become an isolated strategy module with a documented interface.

Yes. Independent long and short legs on one symbol, with separate risk rules per leg.

Yes. USDT perpetuals are the most common request. Spot and dated contracts too, where the venue exposes them.

Yes. Indicators are computed inside the bot process, with no dependency on a third-party signal service.

Yes, with an honest fee model: net edge is computed after taker fees, rebates and funding, not from the raw spread. Arbitrage is not risk-free — failed legs and latency are real.

Yes. Grid step is sized from volatility, and averaging ladders always carry a hard ceiling on total exposure.

Yes. Strategy code is isolated from execution: parameters are configuration, logic changes are a scoped task.

Yes. Start and stop, parameters, positions, statistics and alerts. Telegram runs as a separate process so the trading loop never blocks on it.

Yes. Positions, orders, risk state, audit log, and roles or multi-account where needed.

Bybit V5: signed REST and private WebSocket on a unified trading account.

Automatic reconnect, resubscribe, sequence recovery, and reconciliation against the exchange before any new order is sent — so a drop cannot produce duplicates.

Average price and remaining quantity are recomputed explicitly. The unfilled remainder of a limit order is cancelled immediately rather than left hanging; the filled part is either closed or bracketed, by configuration.

A token bucket tuned to Bybit's IP and UID limits, with prioritisation: cancelling an order matters more than refreshing a quote.

Yes, with explicit latency and slippage grids, and costs applied inside the run rather than subtracted at the end.

Virtual fills against the live order book. It exposes the gap between backtest and reality before capital is at risk.

Features at bar t are recomputed on a truncated series where the future physically does not exist, then compared against the full computation. Any mismatch is a leak. On one of our projects this audit found and closed three real leaks.

You do. Keys live in the environment on your server. They never travel through Telegram.

No. Trade permission is enough. We never ask for withdrawal rights.

On your infrastructure: your VPS or your cloud account. Docker or systemd.

Yes, after payment for the agreed milestone, together with documentation.

We work under NDA. Public case studies show engineering metrics and never the client's identity, strategy parameters or financial results.

No. We are accountable for software behaviour against the specification, not for market outcome. Anyone guaranteeing returns on a trading bot is selling something else.

No. We do not sell signals, do not run signal channels, and do not manage anyone's money.

We implement and harden yours. If you only have an idea we can help formalise and honestly test it, but we do not sell black-box alpha.

Work requiring authentication bypass, breaching an exchange's terms, market manipulation, or collecting personal data without a lawful basis.