Skip to main content
This page is the honest forward-looking view of unCoded’s development. It’s intentionally light on dates — committing to specific dates we miss is worse than no dates at all. It’s heavy on themes — operator demand drives the priorities.

​
How the roadmap is built

The most-requested features from operators get built. We watch:
  • Support requests for the same edge case multiple times.
  • Feature requests with multiple operators expressing interest.
  • Operator community discussions about needs not yet met.
  • Patterns in how operators are working around current limitations.
No VC-driven roadmap. No “we should add X because competitors have it” pressure. Just: what do our operators actually want.
Some requested features don’t align with unCoded’s design principles. We say no to those, even when operators want them.Examples of features we’ve declined:
  • Auto-execution of third-party signal services. Architectural mismatch with operator-controlled philosophy.
  • “AI-driven” signal generation. We don’t claim predictive capability we don’t have.
  • Cloud-hosted version. Self-hosted is core to the architecture.
  • Withdrawal-permitted API key support. Security architectural commitment.
Saying no to features that don’t fit is part of how we maintain product coherence.
Trading bot reliability matters more than feature velocity. We ship updates carefully:
  • Bug fixes faster.
  • Features after extensive testing.
  • Major versions only after multi-week sub-account validation.
Operators trust the bot to keep working. We earn that trust by shipping stable updates, not exciting new ones.

​
Recently shipped

Expansion beyond the original Binance focus. Each new venue went through full hand-tuning: signing scheme, symbol naming, lot/tick precision, error code mapping, rate-limit envelope.
For EU operators wanting native EUR-denominated tax reporting. ECB-published rates via Frankfurter API.
Viewer role for trusted observers (partner, accountant) without giving up control.
No-code strategy authoring. 136 indicators across 9 categories, 41 conditions across 9 categories, 4 trigger modes, 15 timeframes.
Read-only backtest sharing without account creation. Useful for second-opinion validation.

​
Currently shipping

The 64 exchanges in validation status are being individually evaluated for promotion to production. Operators trading on validation-status venues help surface the edge cases that drive these promotions.
The Dashboard already works on mobile (responsive design). Ongoing improvements to make critical actions (kill switch, position close) one-tap-friendly on mobile.
Better aggregation and visualization of per-mode, per-pair, per-strategy performance. Helps operators understand which parts of their setup are working.
Pre-built operator runbook templates for common operator profiles (starter, multi-venue, multi-mode). Easier for new operators to maintain disciplined operations.

​
In research / consideration

Currently: 2FA is operator-implemented at the reverse-proxy layer (Authelia, Cloudflare Access, etc.). Working as intended for most operators.Future: optional native Dashboard 2FA for operators who prefer it bundled. On the longer-term roadmap.
Currently: Telegram-only.Future: similar notification-only integrations for Discord, Slack, possibly Mattermost. Operator demand will determine priority.
Currently: 136 pre-built indicators. Custom indicators require contacting support.Future: an authoring path for custom indicators in the SignalEditor. Complex to do well — most operators don’t need it.
Currently: Backtester runs one configuration per job; operators compare across jobs manually.Future: built-in comparison tooling for evaluating multiple strategy variants side-by-side.
For operators who want validated knowledge of unCoded’s operation. Not core to the product but useful for some operators (especially those running for clients).Currently: no formal program. Future: possible.

​
Explicitly not on the roadmap

Some features are not on the roadmap because they conflict with unCoded’s architectural principles.
  • ❌ Cloud-hosted (SaaS) version of unCoded. Self-hosted is core to the product. We won’t ship a version where we hold operator API keys.
  • ❌ AI-driven trade signal generation. We don’t claim predictive capability. Building “AI signals” would dilute the rule-based-discipline value proposition. Operators wanting this should look elsewhere.
  • ❌ Auto-update without operator approval. Updates remain operator-driven. Auto-update of trading software is too risky.
  • ❌ Withdrawal-permitted API key support. Architectural commitment. Even if a venue supports it, unCoded’s documentation and tooling will continue to discourage it.
  • ❌ Marketplace of operator strategies. Architectural mismatch. unCoded encourages operators to author and own their strategies, not subscribe to marketplace signals.
  • ❌ Real-time HFT-grade infrastructure. Sub-50ms latency optimization. The pre-built modes are designed for multi-minute to multi-day strategies; HFT is a different design space.
  • ❌ Telegram remote-command interface. Notification-only by design.
These will not change. They’re not “future improvements”; they’re explicit design choices.

​
How operators influence the roadmap

Email support with feature requests. We track requests; multiple operator requests for the same thing is the strongest signal.Don’t expect a fast response on requests; we acknowledge but implementation timeline depends on demand and architectural fit.
Discord/Telegram operator communities surface needs through discussion. We watch for patterns.“Multiple operators are working around X” is information; it usually leads to roadmap consideration.
For confirmed bugs and feature discussions you’re willing to discuss publicly. Public issues create pressure for resolution.
Operators with substantial setups, interesting use cases, or bespoke needs sometimes have direct conversations with the team. Their input weighs in on architectural decisions.

​
Honest expectations

Roadmap items are not commitments. They’re current priorities subject to change. We won’t promise specific features by specific dates because:
  • Operator priorities shift as new patterns emerge.
  • Implementation often reveals complexities not visible in planning.
  • Stability matters more than velocity; if something needs more validation, it ships later.
What we commit to:
  • Bug fixes prioritized fast.
  • Security updates shipped immediately.
  • No surprise breaking changes — major versions communicated clearly.
  • Honest documentation of what’s shipping and what’s not.
What we won’t commit to:
  • Specific feature dates.
  • Feature-by-feature competitive parity.
  • “AI-driven” anything. (We don’t have a magic predictive model.)

​
What’s next

Why unCoded

The deeper case for unCoded’s choices.

Comparison

How unCoded compares to alternatives.

Security philosophy

The architectural commitments.

Quickstart

Start operating with current capabilities.

Pricing

The full cost picture.

Support

For feature requests and bug reports.
Last modified on May 3, 2026