Why we built TICPOZ
Retail algorithmic trading is broken. Fragmented tools, ancient platforms, and the signal-seller trap. Here is what we did differently.
I want to be upfront about something. The domain you are reading this on is two days old. We are not a company with a decade of brochures behind us. We are a small team that got tired of the same three problems and decided to build the thing we wanted to use ourselves.
TICPOZ is software. It runs strategies you build, on a brokerage account you own, with rules you wrote. We do not hold your money, we do not take discretionary positions on your behalf, and we do not sell signals. That framing is going to repeat itself a lot across this blog because it is the whole point.
The three things that are broken
1. The tooling is fragmented
A serious retail trader today uses, on average, five separate tools. One to research, one to backtest, one to code the strategy, one to host the bot, and one to monitor it. Each of these tools speaks a slightly different language about candles, ticks, spreads, and fills. The integration tax is enormous and most of the bugs in retail algo trading live in the seams between these tools, not in the strategies themselves.
2. The platforms are old
MetaTrader 4 was released in 2005. The UX is unchanged. MQL is a language that exists nowhere else. cTrader is better but still requires you to write C# inside a panel that feels like Visual Studio 2010. None of this is bad engineering, it is just frozen. The rest of the developer world has moved through a decade of compounding improvements and retail trading platforms have not benefited from any of them.
3. The signal-seller trap
Search "forex signals" on any social platform and you will find thousands of accounts promising 30 percent monthly returns. Some of them are outright frauds. Many of them are well-meaning traders who got lucky for three months and started selling subscriptions before reality reasserted itself. The trader who buys the signal carries one hundred percent of the downside, almost none of the upside, and learns nothing along the way.
What we did differently
TICPOZ is built around three commitments. They are not features, they are constraints we accept on the product so that you do not have to wonder where we sit.
Your strategy, your account
You connect your own brokerage account, cTrader or MT5 or a prop firm account, via OAuth or an API key. The funds never leave your broker. We do not have withdrawal rights, we do not have netting authority, we cannot move money. The strategies you build or buy run against your account using the rules you configured. Every trade is your decision, expressed in code, executed automatically.
Software, not advice
We do not tell you what to trade. We do not nudge you toward instruments where we earn a margin, because we earn no margin on any instrument. We do not run a discretionary book. We are a subscription product. The output of TICPOZ is automation infrastructure, not a view on markets.
Illustrative honesty
Every backtest result on the platform is tagged as illustrative. Every metric we display has a tooltip explaining what assumptions went into it. We refuse to show a Sharpe ratio without showing the live track record next to it. We refuse to display equity curves without the underlying trade log being downloadable. If a number cannot survive scrutiny, we do not show it.
How the engineering reflects the values
Most product decisions are operational, but a few are visible enough to call out.
- Passwords are protected with a modern memory-hard hashing function, chosen specifically because it makes large-scale offline attacks expensive even with GPU clusters. The threat model assumes a breach of our data store and the design fails closed against it.
- Broker tokens — the connection credentials you give us so we can place trades on your behalf — are encrypted at rest with a strong symmetric cipher. The decryption key is held separately from the encrypted data, so a read-only data leak does not give an attacker usable tokens.
- Every user gets a dedicated outbound IPv4 address bound exclusively to their broker traffic. Prop firms flag shared outbound IPs as collusion; we refuse to share IPs between users for that reason. The cost is a recurring infrastructure expense we absorb in the subscription.
- Strategy code runs in per-user isolated workers. One user's runaway loop cannot eat another user's compute.
Respecting prop firms
A non-trivial slice of our users are prop traders, working under FTMO, FunderPro, FundedNext, MyForexFunds successors, and similar firms. We treat these firms as counterparties to be respected, not as obstacles to be gamed. Our per-firm rule plugins are built from the public rule documents and refined when firms publish clarifications. We do not advertise techniques to disguise behaviour, mask drawdown, or hide consistency violations. If a prop firm sees a TICPOZ-connected account, they should see a perfectly ordinary trader running a perfectly ordinary strategy from a stable outbound IP.
The transparency commitment
We publish our changelog. We publish our sub-processor list. We publish what data we collect and what we do with it. When we hit incidents, and we will hit incidents, we publish post-mortems within seven days. This is not unusual for SaaS companies, but it is unusual for trading platforms, where the norm is to hide downtime and reframe outages as scheduled maintenance.
If you read something on the TICPOZ blog and it later turns out to be wrong, we will either correct it inline with a dated note or retract the post. We will not silently edit away mistakes.
What this blog is for
We will write about three kinds of things on this blog. First, technical posts about how the platform works — the dedicated IP system, the backtest engine, the strategy runtime, the Quant-AI prompt pipeline. Second, opinion pieces about how retail algo trading should be done honestly, including pieces that are uncomfortable to write because they criticise common practices we used to participate in. Third, occasional product updates, clearly tagged as such.
We will not write marketing fluff. We will not run "10 best indicators" listicles. We will not chase SEO terms we do not deserve to rank for. If you came here looking for that, this is going to be a disappointing blog and we are okay with that.
That is why we built TICPOZ. The rest of this blog is a slower, more detailed answer to the same question.