Every week someone asks if PipSync has its own signals. It doesn't, and it won't. We chose, on day one, to be the boring layer underneath someone else's edge — the part that takes a message in one of fourteen formats and turns it into an order at your broker without losing fields, dropping fills, or making promises about future returns.
That sentence is the entire pitch. The reason it took two years to ship is that boring is hard.
Why a router is the right unit of work
The retail-quant world is full of strategy products. Backtesters, signal marketplaces, copy-trading bots, autopilot accounts. They all pitch the same thing — returns. None of them want to admit that 90% of a working setup is plumbing: keeping the broker session alive, parsing a malformed message at 2 AM, sizing the position to a specific risk percent without rounding into an over-leverage, retrying the order when the bridge times out, writing the audit log so you can prove tomorrow what happened tonight.
When a strategy product breaks, the customer blames the strategy. When the plumbing breaks, the customer blames you. We picked the side where breakage is unforgivable, so we'd be forced to take it seriously.
What that means for the product roadmap
- We do not publish signals. We never will.
- We do not rank or rate signal providers. That is a slippery slope into implicit recommendations, which a routing tool has no business making.
- We do not promote backtest performance. Past performance disclaimers exist for a reason.
- We integrate every broker we can reach. The user picks. Our job is to deliver the order, not to nudge.
What we'll spend the next quarter on
Three things. First, finishing the audit trail so every order, modification, and partial-fill is queryable for at least 12 months. Second, hardening the failure modes — broker outages, expired sessions, mis-parsed prices — with explicit operator alerts instead of silent retries. Third, publishing real evidence on latency and availability once the production status surface is wired to live telemetry. Until that's in place, we don't make latency claims.
— Tobi