Predikted is four engineers and a designer based across Paris, Tel Aviv, and Singapore. We came from quant funds, exchange infrastructure, and one well-known crypto wallet. We share a strong dislike for the "guaranteed profit" school of trading software - and a strong preference for systems we can read end-to-end.
These aren't slogans - they're the test we run our own decisions against. If a deal would break one of these, we walk.
If we can't draw the architecture on a whiteboard in 60 seconds, we haven't designed the system. Every claim on this site is sourceable; every chart is reproducible.
No promised returns. No "passive income." We ship systems, you supply the strategy and the bankroll. If the backtest is red, we tell you - even if you've already wired the deposit.
At delivery, the repository moves to your org. Branches, history, configs, infrastructure keys - all yours. You can fire us and hire anyone else; the project keeps running.
You don't need to be a trader. If you can describe what the bot should do, we'll translate it. If you want every line of strategy code explained, we'll explain it before you wire funds.
We build for users in jurisdictions where Polymarket and Kalshi are accessible. We won't help with VPN setups, multi-account workarounds, or KYC circumvention. If that's what you need, we are not the team.
Every number on this site cites its source - rate limits, gas costs, market volumes, latency benchmarks. If we can't show the data, we don't write the sentence.
The person you scope with is the person who writes your strategy code, and the one on Discord at 2am when an API drift breaks something.
Ex-quant at a mid-size Paris fund (2017-2022). Built the first version of Predikted after losing patience with a $50k Polymarket bot quote that turned out to be a Fiverr-tier wrapper. Writes the strategy specs.
Six years at a Tel Aviv exchange building matching-engine infra and orderbook indexers. Owns the production runtime - if your bot's late by 50ms, she's the one who diagnoses why.
Joined from a Singapore crypto wallet (15M users). Built the operational layer - monitoring, alerting, deploy. Also our line of defense against "creative" requests that brush ToS.
Ex-Sorbonne PhD candidate (stats), dropped out to ship code. Writes the backtest engine and the wallet indexer that powers the directory. Quietly the most-cited author in our internal Slack.
Designed the Predikted brand and runs the marketing site. Formerly at a fintech in Paris. Insists every chart on the site cites its source - which is why every chart on this site cites its source.
We're hiring a fifth engineer to lead the Kalshi side of the product. CFTC-aware, comfortable with Trade API, ideally based US Eastern. Remote.
In late 2023, Roger paid an Upwork freelancer $4,200 to build a "Polymarket copy trading bot." Six weeks later, he received a Python script that polled the public API every 60 seconds, hard-coded one wallet address, and broke the first time Polymarket rotated its CLOB endpoint. The freelancer disappeared. The deposit didn't come back.
That experience would have been a footnote, except that it kept happening to people around us. A friend in a Discord trading group lost $9k to a similar promise. Another wired $25k to a self-described "Polymarket bot dev agency" in Bangalore and got a half-working dashboard back. By mid-2024 the pattern was clear: the demand for custom bots was real, the supply was largely scammy, and the gap between the two was an actual business.
"We didn't set out to start a company. We started fixing other people's broken bots - and then we got tired of fixing them and started shipping our own."
Predikted is the company we wished had existed when Roger first paid that freelancer. Fixed scope, written quotes, backtest-first deployment, code transferred to the client. No revenue share, no recurring "AI optimization fees", no $499/month subscription that quietly degrades after the first three months. Just engineers who write the code, ship it, document it, and move on to the next project.
We've shipped 23 bots since founding. We've also turned down 11 - projects where the strategy didn't survive the math, the use case brushed ToS, or the operator wanted a guarantee we couldn't make. We expect this ratio to stay roughly stable.
Every scope, change order, and decision is documented in writing before code moves. If it isn't in the doc, it doesn't exist. Saves both sides at month 3 when memory drifts.
Discord channel + weekly 30-min sync. We avoid scheduling for the sake of scheduling. If you're across timezones, that's a feature.
We use Python, TypeScript, Postgres, Grafana, and Hetzner. If a tool isn't five years old and dull, it usually isn't on our stack. Your future hire will thank us.
No pitch deck. We listen, we ask questions, and within five business days you have a written spec and a quote. If we're not the right team, we'll point you to someone honest.