How to Publish Strategies on Arthalab as a SEBI-Registered RA

Arthalab lets SEBI-registered Research Analysts publish option strategies that users can review and deploy to their own broker accounts. This page is for analysts: how the application works, what the dashboard gives you, and how publishing behaves in practice.

Applying

The application asks for your name, your SEBI registration number and a description of what you do. It is submitted from within a normal Arthalab account and moves to a pending state while it is reviewed.

One application per account. Once submitted you can see its status, and once approved your account gains access to the RA dashboard.

What the dashboard provides

Area	What you can do
Your strategies	Create, edit, publish and unlist
Backtests	Run and refresh the backtest attached to a published strategy
Users	See who has deployed each strategy
Deployments	Positions, orders and execution logs for a given deployment
Profile	The details users see alongside your strategies

The fourth row is the one analysts find most useful and is uncommon elsewhere. Seeing the actual execution logs for a user's deployment means you can distinguish a strategy underperforming from a deployment that was never started, or one whose orders were rejected.

Publishing a strategy

Build it

The same builder users have: legs, strike rules, entry and exit times, per-leg and strategy-wide risk settings.

Backtest it

The published figures come from this run, so it is what users will judge the strategy on.

Publish

The strategy becomes visible in the RA section with your name, the index, the backtested figures and the minimum margin.

Unlist when needed

Unlisting removes it from the public list. Existing deployments are unaffected.

The listing shows users the full rule set, not a summary. A strategy published here is reviewable rather than opaque, which is the main thing distinguishing it from a signal service.

What happens when you update a published strategy

This behaviour is deliberate and worth understanding before you edit something people are running.

Users with it deployed are notified. They see that the strategy has been updated and can dismiss the notice once read.
The strategy is flagged as having a pending backtest. Until you refresh it, users see that the published figures describe an earlier version of the rules.
Existing deployments keep running their captured configuration. A running bot executes what it was deployed with; it does not silently adopt your change.

What makes a published strategy worth deploying

From the user's side, the strategies that get deployed and stay deployed tend to share characteristics. Worth knowing when deciding what to publish.

A margin requirement ordinary accounts can meet. A strategy needing heavy margin is reviewed widely and deployed narrowly.
A drawdown that is survivable in rupees. Users convert your percentage to their own size; a figure that looks moderate on a chart can be uncomfortable in money.
Rules a user can understand. Strategies people cannot explain get abandoned during the first bad stretch.
A backtest that is current. A long-standing stale flag is visible to everyone considering the strategy.
Behaviour consistent with its published figures. Nothing erodes confidence faster than a live experience that does not resemble the backtest.

The third item is underrated. A complicated strategy with good numbers loses to a simple one with slightly worse numbers, because the simple one survives the week its user starts doubting it.

Option analysis strategies

Alongside standard option strategies, the dashboard supports option-analysis strategies with two additional controls: executing across all subscribed users at once, and exiting across all of them.

These are powerful and correspondingly consequential. An execute-for-all places orders in many accounts at once, and the same checks that apply to any order — margin, session, address — apply independently in each one, which means partial outcomes across users are possible.

What to check after a bulk action

Each run is recorded so you can see what happened per user rather than only in aggregate. That record is the thing to check immediately after any bulk action.

What users see, and what they do not

Users see	Users do not see
Your name and registration	Other users' accounts or positions
The full strategy rules	Your other unlisted strategies
The published backtest figures	Anything about your own trading
Minimum margin required
Whether the backtest is stale

Practical notes

Refresh the backtest after any material rule change
Check deployment logs before concluding a strategy underperformed
Remember users carry their own margin — a strategy needing heavy margin will have fewer live deployments
Unlisting does not stop existing deployments
Users can clone your strategy and modify it; that copy is independent of your updates

The third item shapes adoption more than most analysts expect. A strategy with a high minimum margin is reviewed by many and deployed by few, simply because of what it requires in the account.

The short version

Apply with your SEBI registration; one application per account
The dashboard covers strategies, backtests, users and per-deployment logs
Published listings show the full rule set, not a summary
Updating a strategy notifies deployed users and flags the backtest as stale
Running deployments keep the configuration they were deployed with
Bulk execute and exit are available for option-analysis strategies, and are recorded per user

If you are a user rather than an analyst, the guide to RA strategies covers how to review and deploy one.

Frequently asked questions

A margin requirement ordinary accounts can meet, a drawdown that is survivable in rupees, and rules a user can actually explain. Strategies people do not understand get abandoned during the first bad stretch.

Simple strategies with slightly worse figures often outlast complex ones with better figures, because users hold them through the week they start doubting.

Yes. The per-deployment execution logs distinguish a strategy that traded and lost from one that was never started or whose orders were rejected.

Promptly. Until you do, the strategy carries a pending-backtest flag that everyone considering it can see, and the published figures describe rules you are no longer running.

SEBI-registered Research Analysts, after applying with their registration number and being approved.

No. You apply from within a normal Arthalab account, and approval adds the RA dashboard to it.

Yes. The dashboard shows who has deployed each strategy and, for a given deployment, its positions, orders and execution logs.

Deployed users are notified, the strategy is flagged as having a pending backtest until you refresh it, and existing deployments continue running the configuration they were deployed with.

No. Unlisting removes it from the public list; deployments already running are unaffected.

They can clone it into their own strategies and modify the copy. That copy is independent and does not receive your later updates.

A control on option-analysis strategies that places orders across subscribed users at once. Each account is still subject to its own margin, session and address checks, so partial outcomes across users are possible and each run is recorded per user.

No. RA strategies are included in users' plans with no per-strategy fee and no profit sharing.

Start with a free 3-day trial

Build a strategy, backtest it and run it on paper — no broker, no IP and no money needed to try it.

Create a free account

All articles More in RA Strategies