Document your rules
You supply the logic. Together we resolve implementation questions and agree deliverables, data dependencies and exclusions.
Custom strategy coding & broker API integrationYour strategy.
Your strategy.
We help code it.
Bring your documented trading strategy. We help turn your rules into code, integrate your broker API and test the implementation against your specification. You define the trading logic; we provide coding and technical support.
Custom development services only. We do not sell ready-made trading software, trading strategies or algo subscriptions, provide investment advice or promise returns.
- Your strategyCustomer-defined and approved
- Your accountCredentials and funds stay yours
- Your controlTesting, visibility and handover
Rules into codetechnical implementation only
Test before releasedocumented acceptance criteria
Broker API supportsubject to applicable requirements
Scoped supportclear responsibilities and handover
01 / Customer-defined strategy coding
A written rule becomes a testable instruction.
Bring your entry, exit, sizing and risk rules in a document or spreadsheet. We resolve technical ambiguities with you, then turn the approved specification into software. You decide what to trade and why; we implement how the system follows your instructions.
Coding and integration support
- Entry conditions, indicators and timeframes you specify
- Customer-defined position sizing, exposure limits and exit logic
- Versioned rules, test examples and written acceptance criteria
YOUR RULES / YOUR CONTROL
Rule-to-code workspace
01 / INPUTRule documentCustomer supplies the logic
02 / PROCESSImplementationConditions translated into code
03 / OUTPUTAcceptance reviewCustomer approves the behaviour
Customer ownership · Clear permissions · Traceable changes
Checking system readinessLoading-state concept
02 / Broker API integration support
Integration support for your broker API.
We help implement the supported API connection for your own strategy code, including authentication, permitted data access and error handling. Any order-related integration requires a review of the actual arrangement and applicable broker, exchange and regulatory requirements before live use. Customer ownership or API access alone does not establish an exemption.
Coding and integration support
- Broker authentication through the supported login flow
- Order status tracking, partial-fill handling and duplicate-order checks
- Customer-defined controls for new entries and open-position management
YOUR RULES / YOUR CONTROL
Order lifecycle / illustrative
Session and permissionsCheck before submitting an instruction↗
Order acknowledgementTrack broker status, not assumed success↗
Unknown responsePause and reconcile; do not blindly retry↗
Engineering concept onlyNo live account data
Checking system readinessLoading-state concept
Your requirements.
Coded to your brief.
These illustrations show the kinds of interfaces we can code around your own rules and data requirements. Each engagement is scoped as custom development, testing and technical support. No ready-made platform, strategy package or trading subscription is offered. Order-related examples depend on applicable permissions and approvals.
03 / Charts & technical analysis
See the setup. Keep the context.
Bring the price chart, indicator panes and drawing tools into one workspace. Move between daily, weekly and monthly views without losing the surrounding watchlist, then inspect the same instrument in the diary when reviewing an execution.
Examples we can code to your specification
- NSE symbol search; 1D, 1W and 1M intervals; 3M through maximum-history ranges
- Candlestick and bar styles, OHLC context, volume, EMA, RSI, ADX and ATR visibility
- Zoom, reset, fit-to-data, adjustable pane heights and saved chart layouts
- Trend-line drawings, price-range measurement and chart-image download
● ● ●CWC / WORKSPACE CONCEPT↗
C
CUSTOM CODING EXAMPLE
DEMOChart workspace
DEMO SYMBOL1D1W1M1YMAX
EMAVolumeRSIADXATR
Pan · Zoom · Draw · Measure · Save layout
04 / Watchlists & screening workspace
An organised universe, beside every chart.
We can code searchable lists for the instruments and screening criteria you supply. You specify the groups, columns and data sources; we implement the interface and data-readiness checks. We do not supply stock picks or recommended screening rules.
Examples we can code to your specification
- Search watchlists and symbols, create custom lists, flag instruments and organise groups
- Sort by symbol, last price or percentage change; show the columns you need
- Switch between watchlist and alert views and inspect paper/live holdings context
- Track membership, available candle history, provider mappings and subscription readiness
● ● ●CWC / WORKSPACE CONCEPT↗
C
CUSTOM CODING EXAMPLE
DEMOWatchlist manager
ScreenerIPOCustom list
⌕ Search your selected universe ⇅
| SYMBOL | LAST | CHG. | FLAG |
|---|---|---|---|
| DEMO A | — | — | ◇ |
| DEMO B | — | — | ◆ |
| DEMO C | — | — | ◇ |
| DEMO D | — | — | ◆ |
HOLDINGS CONTEXTPAPER / LIVE
Search · Sort · Flag · Group
05 / Chart-line alerts & reminders
Know when a condition needs your attention.
Draw a line, select it and attach a crossing alert to keep the event connected to its chart context. Notifications can also cover broker-login reminders and critical execution events, with delivery channels agreed for your deployment.
Examples we can code to your specification
- Selected-line price-crossing alerts with a dedicated alert list
- Broker-session reminders and critical live-event notifications
- Alert state and system context shown without presenting notifications as trade advice
- Delivery depends on the worker, market feed, permissions and configured provider
● ● ●CWC / WORKSPACE CONCEPT↗
C
CUSTOM CODING EXAMPLE
DEMOAlert workspace
Chart alertsSystem events
DEMO A / selected trend lineCrossing condition · user-definedARMED
Broker sessionAuthentication reminderSCHEDULE
Execution needs reviewAn uncertain response requires reconciliationREVIEW
↗ WORKSPACE NOTIFICATIONA condition needs review
Open the chart and inspect the event. This is not a buy or sell recommendation.
Configured channels · No guaranteed delivery
06 / Paper & live position books
Review positions and recorded stop settings.
Separate simulated positions from the connected broker book, and distinguish system-created holdings from manual holdings. A single view brings together position cost, current value, exposure and the stop information needed for operational review.
Examples we can code to your specification
- Paper/live tabs, system/manual classification and connection freshness
- Quantity, weighted average cost, last price, invested/current value and P&L fields
- Day/net change, per-position open risk, active stop and quantity coverage
- Position drill-down to a chart and stop details; explicit off-hours or missing-data states
● ● ●CWC / WORKSPACE CONCEPT↗
C
CUSTOM CODING EXAMPLE
DEMOPositions
PAPERLIVE
Invested—Demo field
Current value—Demo field
Open risk—Demo field
| INSTRUMENT | QTY | STOP | COVERAGE |
|---|---|---|---|
| DEMO A | — | — | Defined |
| DEMO B | — | — | Review |
| DEMO C | — | — | Defined |
LAST LOADED SNAPSHOTOff-hours state
Illustrative fields · No account balances
07 / Configurable strategy & entry logic
Your specification becomes a visible control deck.
We can code a settings interface for the conditions in your written strategy. You supply the indicators, thresholds and permitted changes. We implement and test those instructions without selecting entry rules or providing a preset strategy.
Examples we can code to your specification
- Entry and exit conditions taken from your written specification
- Indicator calculations, timeframes and comparisons you select
- History sufficiency checks, including explicitly defined handling of newly listed instruments
- Decision windows, scan intervals, symbol ranking and synchronized membership controls
● ● ●CWC / WORKSPACE CONCEPT↗
C
CUSTOM CODING EXAMPLE
DEMOCustomer rule profile
Rule profileEntry filtersHistory
Your entry conditionCustomer-defined period and trigger
Your indicator ruleCustomer-defined calculation
Your comparison ruleCustomer-supplied logic
History readinessMissing data stays visible
RULE VERSIONReview before applying
No recommended settings or default strategy supplied
08 / Sizing, stops & execution authority
Make permission and exposure explicit.
Configure position sizing, stop behaviour and operating permissions as distinct controls. Paper and live entry channels are independent. Stopping new entries must not be confused with stopping the management of positions that already exist.
Examples we can code to your specification
- Capital versions, fixed-amount or equity-percentage risk, allocation caps and concurrent-position limits
- Stop and trailing-stop behaviour specified and approved by you
- Your documented exit rules, exposure checks and exception handling
- Explicit live authorisation, session/worker readiness checks and separate paper-only add-on limitations
● ● ●CWC / WORKSPACE CONCEPT↗
C
CUSTOM CODING EXAMPLE
DEMORisk & authority
Position riskDefined by the customer
New-entry permissionIndependent from protection
Running stop rulesAgreed combinations only
Worker-monitored stops depend on uptime and connectivity. They are not guaranteed fills or automatically broker-held orders.
Technical controls cannot guarantee loss limits
09 / Backtests & research history
Replay the rules. Preserve the evidence.
We can build a test harness for your supplied strategy and selected historical data. You define the rule versions, date range and assumptions; we implement reproducible runs and result records. This tests the implementation and does not include strategy recommendations or profitability optimisation.
Examples we can code to your specification
- Single-symbol and combined-universe tests, custom dates, capital and execution-cost assumptions
- Configurable signal ranking, sizing, stops and exits; frozen settings for reproducibility
- Saved run history, completion/failure status and retained failure context
- Result packs with metrics, equity/drawdown curves, monthly returns, simulated trades and benchmark comparison
● ● ●CWC / WORKSPACE CONCEPT↗
C
CUSTOM CODING EXAMPLE
DEMOHistorical test bench
ConfigurationSaved runsResults
UniverseCustomer selection
PeriodCustom dates
Rule versionFrozen with run
ExecutionSimulation only
Run A / approved specificationConfiguration snapshot retainedSAVED
Run B / alternative specificationIsolated from execution channelsRESEARCH
Historical and simulated results do not predict future performance. Data quality, costs and fill assumptions matter.
No live orders · No performance figures shown
10 / Trading journal & trade book
From individual fills to the full trade story.
Use a trade book for every execution and a journal for the complete entry-to-exit record. Keep paper and live histories separate while providing consistent filters, summaries and navigation into the underlying chart and event trail.
Examples we can code to your specification
- Month, status/side and symbol filters for ledger and execution views
- Entry/exit dates, quantity, price, stop, return and open/closed state
- Gross/net result fields and clearly labelled estimated taxes and charges where applicable
- Excel journal export; fill-level buy/sell/turnover summaries and detailed execution history
● ● ●CWC / WORKSPACE CONCEPT↗
C
CUSTOM CODING EXAMPLE
DEMOEntry-to-exit ledger
JournalTrade bookPAPER
Month ⌄ All trades ⌄ Excel ↗
| SYMBOL | ENTRY | EXIT | STATE |
|---|---|---|---|
| DEMO A | — | — | Open |
| DEMO B | — | — | Closed |
| DEMO C | — | — | Closed |
Gross result—Demo field
Est. charges—Demo field
Net result—Demo field
Separate ledgers · Traceable executions
11 / Chart diary & personal rule book
Record the reasoning, not just the result.
Review a trade beside its chart, markers and details, then add observations without rewriting the system facts. A shared rule vocabulary makes reviews comparable while paper and live selections and notes remain separate.
Examples we can code to your specification
- Previous/next trade navigation, chart context and trade-details drawer
- Notes and tags for situational awareness, entry, risk management and exit
- Positive and mistake categories; custom rule definitions that can be maintained
- Observations stored separately from immutable execution facts
● ● ●CWC / WORKSPACE CONCEPT↗
C
CUSTOM CODING EXAMPLE
DEMOChart-linked review
Trade diaryRule book
REVIEW CHECKLIST
Market context
Entry followed plan
Risk reviewed
Exit documented
PERSONAL OBSERVATION
What would you repeat? What needs a clearer rule?
Notes do not alter the execution engine
12 / Behaviour & review reports
Make recurring behaviour easier to spot.
Turn diary tags into a structured review of the selected period. Reports organise observations by category so the operator can examine repeated mistakes and disciplined actions without treating a dashboard as investment advice.
Examples we can code to your specification
- Date-range or month filtering, reviewed-trade totals and untagged-review counts
- Breakdowns for situational awareness, entry, risk and exit categories
- Repeated-mistake summaries, tag frequencies and tagged-trade result fields
- Multiple tags per trade are retained; tag totals may exceed the number of reviews
● ● ●CWC / WORKSPACE CONCEPT↗
C
CUSTOM CODING EXAMPLE
DEMOReview reports
Date rangeMonthReview categories
ContextIllustrative category
EntryIllustrative category
RiskIllustrative category
ExitIllustrative category
Repeated mistakesGroup the customer's saved tagsREVIEW
Untagged tradesKeep incomplete reviews visiblePENDING
Category illustration · Not measured performance
13 / Imports, broker sync & coverage
Keep the record complete, without duplicate fills.
Connect current-day broker executions to the journal and backfill older periods from supported tradebook files. Coverage indicators help distinguish what is saved, what is synchronized and what still needs an import.
Examples we can code to your specification
- Tradebook imports from supported broker XLSX, XLS and CSV formats
- Execution sync using your broker API, de-duplication and daily coverage tracking where supported
- Historical gaps filled through supported imports when your broker API does not provide the required history
- Import/sync history with source, period and received/new record counts
● ● ●CWC / WORKSPACE CONCEPT↗
C
CUSTOM CODING EXAMPLE
DEMOImport & coverage
01Broker fills / tradebook fileCurrent day or historical backfill
↓02Validate & de-duplicatePreserve source and period
↓03Journal & coverage historyRecord what was added
Imports are explicit actions—not automatic historical access
14 / Broker readiness & runtime diagnostics
Know whether the system is ready to act.
Bring authentication, market-data readiness and worker health into view before relying on an automated workflow. Your build can show separate readiness for analytics, live market data and order execution, according to what your broker API supports, and expose the latest cycle instead of hiding failures behind a loading screen.
Examples we can code to your specification
- Worker heartbeat, connection/session state and off-hours status
- Paper/live entry authority, pause/kill posture and protective-management dependencies
- Symbol mappings, historical warmup, subscriptions and last-good watchlist membership
- Latest cycle timing, scanned/skipped instruments, entries/exits, status and diagnostic exports
● ● ●CWC / WORKSPACE CONCEPT↗
C
CUSTOM CODING EXAMPLE
DEMORuntime overview
Worker—Demo field
Data mapping—Demo field
Channels—Demo field
Analytics sourceHistorical data and calculationsREADINESS
Broker connectionAuthentication, ticks and ordersSESSION
Resident workerCycle history and heartbeatHEALTH
ExceptionsMissing data and reconciliationREVIEW
A healthy screen is not a guarantee of execution. Review outages, permissions and open-position responsibilities.
Observable state · Customer-controlled operation
15 / Environment setup and handover support
Setup support for an agreed environment.
We help configure a suitable development and testing environment and hand over your custom code. Any setup for live use must first meet the requirements that apply to the actual arrangement, including broker and exchange permissions. Running code on your own PC or server does not itself remove regulatory obligations.
Coding and integration support
- Technical requirements for the agreed development and testing environment
- Application, database, logs and backup configuration
- Static-IP planning and broker onboarding checks where required
YOUR RULES / YOUR CONTROL
Customer-controlled deployment
01 / INPUTPC or cloud serverCustomer-owned environment
02 / PROCESSRules engine + databaseConfiguration, events and audit history
03 / OUTPUTYour broker APICustomer-authenticated broker connection
Customer ownership · Clear permissions · Traceable changes
Checking system readinessLoading-state concept
16 / Maintenance, changes & handover
A maintained system, with a defined scope.
After acceptance, we can provide software fault investigation, dependency updates and changes to rules you supply. Each change is reviewed and tested. We do not choose profitable parameters, monitor markets as an adviser or make discretionary trading decisions for you.
Coding and integration support
- Agreed support hours, response targets and exclusions
- Custom source-code handover and ownership terms defined in the contract
- Runbooks, configuration history and scoped maintenance releases
YOUR RULES / YOUR CONTROL
Change request / delivery record
Customer requestNew specification or reproducible software fault↗
Review and testingScope, estimate and acceptance cases↗
Controlled releaseDocumented approval, deployment and rollback↗
Engineering concept onlyNo live account data
Checking system readinessLoading-state concept
A clear brief. A controlled build.
Start with a defined requirement—not a promise of market performance. Each stage ends with something you can review.
Build & verify
We implement the approved specification and demonstrate expected behaviour with tests and agreed simulation scenarios.
Review & hand over
You review the custom code and test results. Any live-use assistance requires applicable permissions and approvals to be confirmed for all parties before activation.
Hand over & maintain
Receive documentation, access details and an operating runbook. Ongoing changes follow the agreed support and approval process.
We code your rules.
You define the strategy.
Our technical scope
Code your supplied specification, help integrate permitted broker APIs, test and hand over the custom implementation. Maintenance covers technical issues and changes to rules you supply. We do not sell ready-made trading software or operate a trading service for you.
Your responsibility
Define and approve your strategy, retain account control and review the implementation. We, you and any broker or provider remain responsible for the obligations that apply to our respective roles.
Before live use
Assess the actual service arrangement and confirm applicable broker, exchange and regulatory requirements. Any required provider empanelment, algo registration, broker permissions and technical controls must be in place before live use.
Deployment requirements can change. Review your broker’s official API documentation and applicable broker, exchange and regulatory requirements for your exact use case. Trading involves risk; software cannot guarantee execution, uninterrupted operation or protection from losses.
Practical answers.
No trading promises.
Can I buy ready-made trading software or a strategy from you?
No. We offer custom coding, broker API integration support, testing and technical maintenance for a strategy you supply. The illustrations on this page are examples of development work, not a product catalogue or an algo subscription.
Do you provide trading strategies or investment advice?
No. This service implements rules you supply and approve. We do not recommend securities, choose investment parameters, supply trading tips, manage portfolios or promise returns. Requests that go beyond technical implementation require a separate assessment and are not included in this offering.
Does coding my strategy guarantee better trading results?
No. Coding translates the rules you supply into instructions; it does not establish that those rules are profitable. Testing checks agreed behaviour. Markets, slippage, gaps, rejected orders and software faults can still cause losses.
Can I run the software on my own computer?
Yes, subject to the agreed technical setup and current broker requirements. Your PC must remain available when the software needs to run. A customer-controlled server is another option; neither deployment location guarantees uptime or determines regulatory classification by itself.
Who keeps my broker login, API credentials and funds?
You retain control of your broker account, funds and credentials. Authentication uses the broker’s supported flow. Secrets belong in your controlled environment, not the public website or source repository. Any temporary technical access must be explicitly authorised, limited and revoked when no longer needed. Never send passwords, OTPs or API secrets through this enquiry form.
Does every project include live order execution?
No. Our service is custom coding and broker API integration support, not access to an order-placement platform. Projects may cover data integration, dashboards, journals, backtesting or paper simulation. Any work that enables live algo orders needs a separate assessment of applicable empanelment, registration and broker requirements; customer authorisation alone is insufficient.
What should I prepare before asking for a quote?
Prepare a plain-language rule document, the broker and API you use, required data and timeframes, expected screens, preferred PC or server setup, and support expectations. We will request the detailed specification after the initial enquiry. Do not include login credentials.
What does the quote cover?
Fees cover custom coding, integration support, testing and agreed handover or maintenance work. We do not charge for access to ready-made trading software or a supplied strategy. Hardware, cloud hosting, internet/static-IP services, broker API subscriptions and data licences are identified separately where applicable. Support hours, warranty terms, acceptance criteria, ownership and outage responsibilities belong in the written agreement.
Does custom coding avoid the empanelment requirement in Section 5(III)(a)?
No blanket exemption is stated. Section 5(III)(a) of SEBI’s 4 February 2025 circular requires exchange empanelment for algo providers offering the facility to place algo orders with brokers through APIs. It does not explicitly resolve every freelance coding or support arrangement. The actual activity must be assessed under applicable rules; calling it custom coding or running it on a customer’s machine does not settle the question. Read the SEBI circular, pages 3–4.
Are you affiliated with my broker, or does this page guarantee compliance?
Clear Web Craft is an independent software-development service. This page does not imply a partnership with or endorsement by your broker. Integration is subject to your broker API’s supported features, permissions and terms. Broker, exchange and regulatory requirements must be checked for the exact deployment; this page is not legal advice or a registration exemption.