> ## Documentation Index
> Fetch the complete documentation index at: https://uncoded.ch/docs/llms.txt
> Use this file to discover all available pages before exploring further.

# Roadmap — Where unCoded Is Heading

> What's shipping next, what's in research, and how operator demand drives the priorities. The honest forward-looking view.

<Info>
  **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.
</Info>

## How the roadmap is built

<AccordionGroup>
  <Accordion title="Operator demand drives priorities" icon="users">
    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.
  </Accordion>

  <Accordion title="Architectural fit matters" icon="puzzle-piece">
    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.
  </Accordion>

  <Accordion title="Stability over speed" icon="balance-scale">
    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.
  </Accordion>
</AccordionGroup>

## Recently shipped

<AccordionGroup>
  <Accordion title="Hand-tuning to 17 production-ready exchanges" icon="building-columns">
    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.
  </Accordion>

  <Accordion title="Tax export with EUR conversion" icon="circle-euro">
    For EU operators wanting native EUR-denominated tax reporting. ECB-published rates via Frankfurter API.
  </Accordion>

  <Accordion title="Dashboard's two-role authentication (admin + viewer)" icon="user-shield">
    Viewer role for trusted observers (partner, accountant) without giving up control.
  </Accordion>

  <Accordion title="SignalEditor visual canvas" icon="wand-magic-sparkles">
    No-code strategy authoring. 136 indicators across 9 categories, 41 conditions across 9 categories, 4 trigger modes, 15 timeframes.
  </Accordion>

  <Accordion title="Backtester with share tokens" icon="flask">
    Read-only backtest sharing without account creation. Useful for second-opinion validation.
  </Accordion>
</AccordionGroup>

## Currently shipping

<AccordionGroup>
  <Accordion title="Validation status → production for selected exchanges" icon="rotate">
    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.
  </Accordion>

  <Accordion title="Mobile-friendly Dashboard improvements" icon="mobile">
    The Dashboard already works on mobile (responsive design). Ongoing improvements to make critical actions (kill switch, position close) one-tap-friendly on mobile.
  </Accordion>

  <Accordion title="Per-strategy P&L analytics" icon="chart-bar">
    Better aggregation and visualization of per-mode, per-pair, per-strategy performance. Helps operators understand which parts of their setup are working.
  </Accordion>

  <Accordion title="Operator runbook templates" icon="book">
    Pre-built operator runbook templates for common operator profiles (starter, multi-venue, multi-mode). Easier for new operators to maintain disciplined operations.
  </Accordion>
</AccordionGroup>

## In research / consideration

<AccordionGroup>
  <Accordion title="2FA at the application layer (Dashboard)" icon="lock">
    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.
  </Accordion>

  <Accordion title="Discord / Slack notification integration" icon="paper-plane">
    Currently: Telegram-only.

    Future: similar notification-only integrations for Discord, Slack, possibly Mattermost. Operator demand will determine priority.
  </Accordion>

  <Accordion title="Custom indicator authoring" icon="wand-magic-sparkles">
    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.
  </Accordion>

  <Accordion title="Per-strategy backtest comparisons" icon="balance-scale">
    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.
  </Accordion>

  <Accordion title="Operator skill / certification" icon="graduation-cap">
    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.
  </Accordion>
</AccordionGroup>

## Explicitly not on the roadmap

<Warning>
  **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.
</Warning>

## How operators influence the roadmap

<AccordionGroup>
  <Accordion title="Feature requests through support" icon="envelope">
    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.
  </Accordion>

  <Accordion title="Operator community discussions" icon="users">
    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.
  </Accordion>

  <Accordion title="GitHub issues / public bug tracker" icon="github">
    For confirmed bugs and feature discussions you're willing to discuss publicly. Public issues create pressure for resolution.
  </Accordion>

  <Accordion title="Direct conversations with operators" icon="phone">
    Operators with substantial setups, interesting use cases, or bespoke needs sometimes have direct conversations with the team. Their input weighs in on architectural decisions.
  </Accordion>
</AccordionGroup>

## Honest expectations

<Warning>
  **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.)
</Warning>

## What's next

<CardGroup cols={2}>
  <Card title="Why unCoded" icon="lightbulb" href="/about/why-uncoded">
    The deeper case for unCoded's choices.
  </Card>

  <Card title="Comparison" icon="scale-balanced" href="/about/comparison">
    How unCoded compares to alternatives.
  </Card>

  <Card title="Security philosophy" icon="shield" href="/about/security-philosophy">
    The architectural commitments.
  </Card>

  <Card title="Quickstart" icon="forward" href="/quickstart">
    Start operating with current capabilities.
  </Card>

  <Card title="Pricing" icon="dollar-sign" href="/pricing">
    The full cost picture.
  </Card>

  <Card title="Support" icon="life-ring" href="/operations/support">
    For feature requests and bug reports.
  </Card>
</CardGroup>