Productized offer · 14 days
Trading Desk
A live exchange trading stack: market data, risk caps, Telegram control, and a monitoring dashboard — your rules, your keys.
$897
Fixed price · 14 days · one revision after first demo
Fixed scope and timeline. Full rules: Refund Policy.
Prefer a quick check first? Telegram · WhatsApp — same-day reply on weekdays.
Market vs Oaklaunch
Agencies quote “algo bots” like a six-week research project. If you already have rules, the work is engineering: live data, risk, Telegram, dashboard.
- · Typical custom exchange bot + dashboard quotes: about $3,000–$8,000
- · Oaklaunch Trading Desk: $897
- · About 70–89% less than that band (~80% below a ~$4,500 mid-market average)
- · Clear deadline: 14 days fixed — not an open retainer
Benchmark from 2025–2026 public agency / freelance quotes for similar scoped work. Exact vendor quotes vary. Not a $50 Fiverr gig and not a 3-month agency SOW.
Not investment advice. We implement the rules you provide. No profit or ROI guarantee. You keep API keys with withdrawals disabled.
More extra packs live under Other services. Need a page first? Launch Page is the web pack.
What you can use this for immediately
- Bybit (or scoped venue) live data + orders with a kill switch
- Telegram start/stop, balance, positions, trade alerts
- Hard risk caps so a bad day cannot run the account
- Demo / paper mode before keys go live
Shipped stack
vbk_trade
Real trading bot we shipped. The marketing pages are the first-demo snapshot — not the later full build. Stack and launch steps below; strategy and keys stay private.
Stack used to build the bot
Runtime
Python 3 · asyncio event loop
Exchange
Bybit REST for account and orders · WebSocket for live market data
Telegram
aiogram bot: start/stop, balance, open positions, trade alerts
Risk
Position size cap, daily loss stop, max drawdown, kill switch — in front of every order
Dashboard
aiohttp monitor: status, positions, recent logs
First run
Demo / paper mode before live keys. Env template; withdraw rights off.
After launch
python main.py
- 01
Start the process
From the project root run python main.py. It loads the env file and starts the asyncio loop.
- 02
Connect
The loop brings up Telegram control and the Bybit REST + WebSocket connections.
- 03
Risk first
Every order path goes through the risk manager. Caps and the kill switch can halt trading without killing the process by hand.
- 04
Watch and control
Use Telegram for start/stop and alerts. Open the dashboard for status, positions, and logs.
Not investment advice. No profit or ROI guarantee. You keep API keys with withdrawals disabled. Strategy rules stay private.
Best for
Traders and crypto operators who already know their rules and need them running live
Includes
- · On-time delivery of the listed scope — fixed 14-day timeline
- · One exchange connection (Bybit default; another venue if scoped in the brief)
- · Live market data over WebSocket + REST for account/orders
- · Risk caps: position size, daily loss, max drawdown, kill switch
- · Telegram control: start/stop, balance, open positions, trade alerts
- · Monitoring dashboard: status, positions, recent logs
- · Demo / paper mode for the first run
- · Env template, runbook, and one revision after first demo
Not included
- · Profit, ROI, or signal guarantees
- · Holding or trading client funds; API keys with withdraw enabled
- · Secret strategy research sold as a product
- · 24/7 desk support retainer
- · Unlimited exchanges, symbols, or strategy rewrites
You receive
- · Runnable source + env template
- · Telegram bot for control and alerts
- · Monitoring dashboard URL or local run
- · Runbook (start, stop, keys, risk caps)
Handoff · first demo · revision · acceptance
What you get at handoff
Final delivery includes the listed items — typically a staging or production URL, source access (GitHub invite or zip + README), an env/credential checklist (you keep the keys; we do not store withdraw-enabled secrets), a short test and rollback note, and a handoff checklist. A license to use the work transfers only at this final handoff. We notify the contacts from your brief.
Change after first demo
At the first demo you may ask for a new direction — not only in-scope tweaks. We rebuild against that plan and the stated timeline starts again from the day we confirm it in writing.
One revision round
After the first demo, send one consolidated note of in-scope changes: tests for the listed workflow, credentials and env wiring, staging checks, and rollback notes. It is not extra features, extra integrations, or a redesign of the agreed scope. Extra rounds are a paid add-on or change order.
72 hours after handoff
Once we send final handoff to your stated contacts, you have 72 hours to report a missing listed deliverable in writing. If you don’t, the pack is deemed accepted for refund purposes. Refund Policy.
After payment
What actually happens next
We work mostly by written messages. After payment and a complete brief, we lock the workflow, send a first demo, then hand off on the stated clock.
- 01
Written kickoff
We confirm the workflow, timeline, and open questions by email / Telegram / WhatsApp.
- 02
Workflow map
You get a short map of commands, alerts, or connections — reply until it matches.
- 03
First demo
We send a working demo. This is the moment to change direction if the first plan was wrong.
- 04
Revision + handoff
One in-scope revision, then source, runbook, and access — inside the fixed timeline.
Timeline: 14 days. See Terms and Refund Policy.
Ready when the example fits
Book a free consult first — or pay now if you’re ready. Apple Pay, Google Pay, PayPal, Wise, or USDT. Production starts after payment and a complete brief.
Trading Desk — consult first, or pay now