About

We are new, and we build exactly one thing: isolated hosting for your trading.

triStack AlgoTrader is built and operated by Tristack Technologies LLP, registered in Delhi. It gives one customer one instance: their own database, their own dedicated egress address and their own engine running their own code. There is no company history worth telling yet, so this page is the next most useful thing: what we decided to build, why we decided it that way, what it cost us, and what we will not do.

One tenant per instanceDedicated egress IP31 broker adaptersEquity, F&O, currency and commodities

See how it works Read our compliance posture

The problem

Everything about algo trading in India is easy except where to run it.

The strategy is the interesting part and the part people want to spend their time on. What actually stops them is the week that comes after: a server, a database, a broker session that dies at three in the morning, and an address the broker will accept orders from.

Run it yourself

A second job you did not apply for

A VPS, TLS, backups, patching, monitoring, log rotation and a static address, all maintained by the person who was supposed to be writing strategies. It works right up until the morning it does not, which is reliably a morning the market is moving.

Use a shared platform

Your data behind somebody else’s WHERE clause

Cheaper, and separated from every other customer by a column in a shared table and an address a crowd trades from. You inherit their outages, their rate limits and their reputation with your broker, and you cannot inspect any of it.

Hand it over

Somebody else deciding your trades

Signal services and managed accounts solve a different problem, and they replace the part you presumably wanted to keep. If your edge is your own, giving it to someone else to run is not a hosting decision.

So we built the fourth option. You keep the algorithms and the broker account. We take the server, the database, the address and the three in the morning, and we take them for one customer at a time.

Positions

What we chose, and what each choice costs us.

These are decisions rather than features. Each one is more expensive than the alternative, and each one is the reason a particular category of failure cannot reach your account.

One database per customer, not one database with a customer column

The obvious way to build this is a shared schema with a tenant id threaded through every table, and it is cheaper to run by a wide margin. It also means the separation between two customers is a WHERE clause, upheld by every query anyone ever writes. We gave that up: your instance opens your own database file on your own volume, and the isolation holds even when the code is wrong.

Cost: one database, one volume and one backup schedule per customer

One egress address per broker account, never a pool

Your broker will accept API orders only from an address registered against your own developer app. A shared egress address would mean every customer whitelisting infrastructure that other people also trade from, which turns the control your broker gave you into decoration. So each broker account gets an address reserved to it, and IPv4 addresses cost real money that shows on the bill rather than being averaged across everybody.

Cost: a scarce resource bought per customer, per broker account

The customer writes the algorithm. Always.

It would be commercially easier to sell strategies, publish signals or offer to run an account. We do none of those, and the whole product is arranged so that we could not: no discretionary control, no aggregation of customer code, no view on any security anywhere in the system. What we sell is somewhere for your own trading system to live.

Cost: a smaller market, and a much shorter compliance conversation

The broker relationship stays between you and your broker

You open the account, you register the developer app, you hold the key, you register the address. We never create a broker app for a customer and never hold a credential the customer did not issue. Revoking the key stops your instance immediately and we cannot undo it, which is exactly the asymmetry that should exist.

Cost: onboarding has steps we cannot do for you

Test on paper before you test with money

Every instance ships a sandbox with its own store, its own capital, a real margin model and exchange-aligned square-off, and order approval mode is there so a strategy can run live with a human in the loop before it runs live without one. Neither is a premium feature, because a safety control behind a paywall is not a safety control.

Included: sandbox, approval mode, full logs, on every instance

Publish nothing we have not measured

There is no latency figure on this site, no uptime percentage and no backtest. A number on a marketing page becomes a contractual term the moment somebody screenshots it, and the ones we could publish today would be about your code rather than our infrastructure. When there is something measured and worth committing to, it will appear with the method next to it.

Uptime commitment: none published

The mechanics behind each of these are written up in security, and the sequence a new instance goes through is in how it works.

Boundaries

triStack AlgoTrader is hosting infrastructure, not an investment adviser and not a signal provider.

That is a boundary we designed around, not a line of fine print at the bottom of a page. Here is what it rules out, plainly.

No advice, tips, calls or buy and sell recommendations. We hold no opinion on any security and publish none.
No signals and no strategy marketplace. Every algorithm on your instance is one you wrote or chose to run.
No managed accounts and no discretion. The software executes only what your own code and configuration produce.
No profit sharing, and no assured, indicative or projected returns of any kind.
We never hold, receive or handle your funds or securities. They stay with your own SEBI-registered broker.

Registration status

Tristack Technologies LLP is not registered with the Securities and Exchange Board of India (SEBI) in any capacity: not as an Investment Adviser, not as a Research Analyst, not as a Portfolio Manager, and not as a stock broker. It does not hold, and does not claim, any SEBI registration.

We say it here rather than burying it, because if any of the five points above matter to what you were hoping to buy, you should find that out on this page and not after paying us.

Read the full compliance posture Risk disclosure

Roadmap

Where this goes next, stated as a plan and not as a product.

None of the first two is live today. Read them as a plan you can hold us to rather than as something you would be paying for. The third is not a plan at all; it is a line we are telling you in advance we will not cross.

In development

More broker adapters

Adapters are written against each broker's published API and appear on the brokers page marked available the week they ship, not before. 31 are in the engine today.

Designed, not built

Self-serve provisioning

Today an instance starts as a conversation, because an address has to be allocated and a size agreed. A guided path that does the routine part on its own is designed. Nothing about it would change who holds the broker key.

Deliberately not planned

Anything that trades for you

Not a signal feed, not a strategy marketplace, not a discretionary control on our side. This is not a resourcing decision that could change next quarter; it is the boundary the whole service is arranged around.

Provenance

Where the software came from

Worth saying out loud rather than leaving people to work out from a licence file.

The software behind triStack AlgoTrader began as a fork of the OpenAlgo open-source project, and we are grateful to its authors. It is now a separated fork: a codebase we maintain on our own, with our own architecture, our own release cycle and our own support. Upstream is not responsible for it, and it is not a distribution of upstream.

Open-source work that reaches production is a real gift, and pretending a codebase sprang from nowhere would be both dishonest and ungrateful. What we operate today has moved a long way from where it started, and everything about how it runs, how it is isolated per customer and how it is supported is ours to answer for.

Contact

How to reach us

Email reaches a person who works on the product. There is no ticket maze in front of that, and inside support hours somebody is watching the desk.

Registered entity

Tristack Technologies LLP

B-35, Vinoba Kunj ApartmentsSector 9, RohiniDelhi 110085India

LLPIN: ACP-3743
GSTIN: 07AAYFT2516N1ZF

Tristack Technologies LLP was founded in 2026 and is the legal entity behind the triStack AlgoTrader brand: the party you contract with, the party that raises your GST invoice, and the party named in the Terms of Service.

Support: [email protected]
Onboarding, broker connections, instances and billing
Grievance: [email protected]
Formal complaints, under the IT Rules, 2021

Monday to Friday, 8:00 AM to 5:00 PM IST

We run the infrastructure your instance sits on: the host, the isolated database, the dedicated egress IP and the engine process. Your strategies run on the schedule you configure, and starting, stopping and squaring them off remains yours to do. Planned maintenance is scheduled outside NSE and BSE market hours wherever it can be, and you are told before it happens.

Open the contact form Operating commitments

Get started

Start with a conversation, not a checkout

Tell us what you want to run, which broker you are with and how much of the day it needs to be awake. If this is the wrong product for you, we would rather say so on that call than after you have paid for an instance.

Create your account Sign in to your instance Talk to us

Your infrastructure, your code, your broker account. · [email protected]