Your Pre-Flight Checklist

Zero smoke, zero mirrors. You pay a flat monthly rate. We don’t do hidden fees, sneaky in-app purchases, or surprise "pro-plus-turbo" tiers designed to punish you for succeeding.

You bet. You get the full, unlocked experience for the entire trial period. We need a card to get you started (to keep out the bots and time-wasters), but if you cancel before the trial ends, your bank account remains untouched.

Sorry, operator. Since you get the full software instantly, all sales are final. The free trial is your time to kick the tires, light the fires, and make sure our gear is right for your mission. Canceling just stops future payments.

We don't do forced auto-updates that can break your setup. When a new version of Key Commander or Lynx-Relay drops, you'll get a notification. You then download the new version from your account and deploy it on your own schedule. For Key Commander, it's as simple as pulling the new Docker image. For Lynx-Relay, you just replace the executable.

Safer than a dragon's hoard. All our tools run on your hardware. We use top-shelf encryption to lock down your secrets on your local machine. We never see them, we never store them, and we built them to be tough enough to make a cryptographer nod in approval.

Yell at us! We're live on Telegram and X. We're always ready to help a fellow operator out of a jam.

We're the renegades. A small squad of engineers and traders who got sick of automation tools that were overpriced, unreliable, or both.

Fueled by late nights and questionable amounts of caffeine, we built the gear we wanted to use. Now we’re sharing it with you.

The catch is there's no catch. We're not bankrolled by VCs and we don't have yachts to pay for. We built these tools for ourselves and priced them for people like us.

Go use the money you save to buy a better graphics card or another case of energy drinks. You've earned it.

Our roadmap is basically a community wishlist. We build what you ask for. Hit us up on Telegram or X with your genius ideas. The most-wanted features get built next.

Both. At its core, it's a badass license manager. But we also built it to be the entire backend for a MicroSaaS. It handles Stripe webhooks, generates keys, sends emails, runs its own health checks, and automatically backs itself up. Pair it with our free website template, and you've got a complete business stack.

Nope. The template is a freebie to get you started faster. Key Commander is a headless FastAPI server. If you already have a website, just point its API calls to your Key Commander instance for validation, and you're good to go.

Yep. Key Commander has a CSV import tool. As long as you can get your data out of your old system and into a CSV file, you can import your entire history of licenses, customers, and keys. We have a template in the docs to make it easy.

It's a two-stage process. On startup, a 'fast sync' grabs recent changes to keep you current. Then, a 'daily sweep' runs in the background to deep-check history and fix any data drift. It's designed to be relentless, so even if your server was offline, it will automatically correct any missed webhooks and ensure your local database always matches Stripe's records.

Yep. We call it the 'Comms Relay.' You can create messages with titles, HTML content, images, and clickable links right from the Key Commander GUI. Your app fetches these messages on validation, so you can push updates, promotions, or downtime alerts directly to your users.

Key Commander includes a built-in error reporting pipeline. Your app (and our free website template) can send error logs directly to a secure endpoint on your Key Commander server. You can view, manage, and track these reports right from the admin GUI. No need to pay for a third-party logging service.

Pretty much, yeah. For your security, there is absolutely no recovery for the master password. We can't reset it. Nobody can. If you lose it, you'll have to perform a "scorched earth" reset: delete your server's data directory and set up Key Commander from scratch. You can then use the Stripe reconciliation feature to rebuild your customer and license history. It’s a pain, but it proves we can't access your encrypted data, even if we wanted to.

We hate terminals too (for this kind of stuff). After the initial one-line Docker command, Key Commander is 100% GUI-driven. If you can click a mouse, you can manage a licensing empire. No command line, no editing weird .env files.

Everything. Generates keys, manages customers, processes payments, delivers licenses, handles revocations, reissues... all from a slick Admin Portal. It's your entire back-office in a box.

Yes. One flat rate. All the features. No add-ons, no tiers, no "call for pricing" nonsense. Scale to a million users; we don't care. Your success is yours, not ours.

A low cost VPS with Docker is perfect. We recommend OVHcloud. The VPS 2 is solid for just Key Commander. If you plan to host website static assets on the VPS, get a VPS 3+. Always grab the NVMe drive - it's not optional in our book.

You deploy one Docker container. That's it. The Admin Portal then holds your hand through the rest of the setup.

It's a two-part system: a headless server that does all the heavy lifting, and the GUI Admin Portal you use to command it. Once you set it up and lock it with your master password, the server runs completely on its own.

No. The desktop admin GUI connects to the server over a single, secure HTTPS port (the same one your app uses for validation). It's designed to be firewall-friendly. You can run the GUI on your local machine or even a different server..

Right now, it's deeply integrated with Stripe. We're adding more. Let us know who you want to see next!

One-time purchases, recurring subscriptions, time-limited trials and bundles. It handles all of these right out of the box.

Yep. Each license key gets chained to a unique machine ID upon activation. No more one-to-many license sharing.

There's a two-tiered solution. First, a self-serve option in the user's account lets them reset their own machine ID. Second, Admin's always have manual override.

Nope. You can enable offline session tokens. The user's app checks in once, gets a token, and can then work offline until the next renewal period.

Based on OWASP and industry-standard protocols, built-like-a-bunker secure. We take this stuff very seriously.

Of course. As the admin, you can mint custom keys on the fly for whatever purpose you need.

Unlimited products. You can configure a distinct license definition for every tier, plan, or bundle you sell.

Yep. It has manual and automated backups. It also constantly cross-references with Stripe to keep your data pristine.

It can. Restore from a backup, run a reconciliation with Stripe, and all your customer data and licenses are back from the dead. (Dev keys need a backup to be restored, though).

100%. After a purchase, keys are generated and can be emailed instantly, if this setting is selected. We support SMTP, Brevo, and Amazon SES.

The Key Commander README is packed with code examples. If you get stuck, hit us up on Telegram or X. We'll get you sorted.

It's not magic, it's just efficient engineering. It installs the whole security stack: NGINX for reverse proxy, adjusts your computer's clock sync, Memurai/Redis for an in-memory database, and NSSM to make sure services stay running. Plus, it wraps everything in a shiny SSL certificate.

It does, but only gently. Just a few tweaks to optimize performance of Lynx-Relay. And yes, it knows how to clean up after itself if you decide to uninstall.

While rare, it can happen. A restart and a reinstall usually fixes it. If that does not work, you can go old-school and configure your computer manually. The README has the full, step-by-step instructions for a manual override.

Check your perimeter. You must log into your internet router and configure Port Forwarding for Port 443 to your trading machine.

Check the Router tab in Signal Shield—it displays the Local IP address you need to target. (Verify this matches your actual LAN setup if you have a complex network).

Crucial: Standard routers can only forward Port 443 to one single device on the network at a time.

Absolutely. The uninstaller is as thorough as the installer.

Windows 10/11 and Server 2016+ are our bread and butter. Linux and macOS versions are brewing in the lab.

Either. You can run it on your main trading desktop. But for 24/7, set-it-and-forget-it automation, we strongly recommend running it on a dedicated machine or a Virtual Private Server (VPS) that's always online. If the machine running Lynx-Relay goes to sleep, so does your trading bot.

Our software is lean and mean. It'll run on just about anything without bogging it down.

Your call. Run it on your daily driver, a dedicated desktop, or your gaming beast. If you want 24/7 uptime without your electric bill screaming in terror, a Virtual Private Server (VPS) is your best bet.

Only if it plays musical chairs with your IP address. You need a static (unchanging) IP for TradingView's webhooks to find their target. If your IP changes, the signal gets lost in the ether.

Not on our watch. Signal Shield builds a fortified, encrypted tunnel just for your webhooks. It's like a VIP entrance with a bouncer that only lets TradingView in.

We support trading on Alpaca (stocks & crypto), Binance.US, Gemini, and Kraken.

New: We are currently rolling out Beta support for Binance Global. International users are invited to test this capability and provide feedback as we finalize the integration.

Paper/Sandbox: We support Alpaca, Binance Global and Gemini paper/sandbox environments. Note: Kraken and Binance.US do not have this capability.

In Lynx-Relay, open Update Keys → Exchange API, then select the Paper Trade / Sandbox option in the exchange selector. That’s it.

Everything else behaves exactly like live accounts (and you can swap back to live the same way).

Important: paper/sandbox environments require their own API keys — your live keys won’t work there.

Same as Signal Shield: Windows 10/11 and Server 2016+. Linux/macOS support is on the horizon.

Less than 15 minutes. Seriously.

Your Mission, Should You Choose to Accept It:

1. Run Signal Shield (the 1-click part).
2. Fire up Lynx-Relay.
3. Punch in your master password and webhook passphrase.
4. Slap in your license key.
5. Feed it your Telegram Bot Token and Chat ID.
6. Plug in your exchange API keys.

Point TradingView to your webhook URL. Go live. Done.

We support a whole arsenal for spot trading:

• Kraken: Limit, Advanced Limit, Market, Take Profit, Stop Loss.
• Gemini: Limit, Advanced Limit, Take Profit, Stop Loss. (We cleverly emulate market orders since they don't offer them directly).
• Binance.US: Limit, Advanced Limit, Market, Take Profit, Stop Loss.
• Binance Global (Beta): Market & Limit.
• Alpaca: Market & Limit (Stocks & Crypto).

Close. It's JSON. You craft a JSON payload in your TradingView alert message. Lynx-Relay receives it, deciphers your commands (buy, sell, quantity, etc.), and executes the trade. It's your strategy, spoken in the language of machines.

We know that hunting for a rogue bracket when there's money on the line is nobody's idea of a good time. So, we built the tool we wanted - a configurator that writes the code for you. Once you're an operator, you get access to our exclusive Webhook Configurator.

Go to a "what is my IP" site. Copy that address. Paste it into your TradingView webhook URL like this: https://YOUR.PUBLIC.IP.ADDRESS/webhook. Boom.

It can handle up to 10 alerts per second without breaking a sweat. If you're sending more than that, you're either a god-tier HFT or you've made a terrible mistake in your script.

Your entire operation at a glance: system status, incoming alerts, trade results, connection health, a full audit log, and P&L tracking. Total transparency.

Yep. The Telegram integration means you get real-time pings for every move your bot makes, so you can look busy while secretly monitoring your trading empire.

Positive. They're encrypted and stored on your machine. We couldn't see them even if we wanted to (and we don't).

If the signal can't get through, trading pauses. Lynx-Relay needs a live connection to receive webhooks and execute trades.

Nope. We don't believe in forcing updates on you. When a new version drops, you'll grab it from your account and just replace the old executable. No re-setup needed.

Two ways: for a total system halt, just stop the Lynx-Relay service. For a more surgical approach, pause individual alerts inside TradingView.

Not totally, but you'll have to perform a "scorched earth" reset. For security, there's no recovery. You'll need to delete the SignalLynx_Vault.encrypted file, restart Lynx-Relay, and re-enter your keys. It’s a pain, but it's secure. You'll be back online in 10 minutes.

More exchanges, more dashboard widgets, more power. Tell us what you want, and we'll probably build it.

Lynx-Forge is the upcoming Signal Lynx graphical trading workstation for systematic traders. It is designed to let you create or import Python strategies, test them against historical and live market data, optimize them for current conditions, validate them with walk-forward and Monte Carlo testing, then run qualified strategies in paper or live spot trading.

No. A backtest is only one checkpoint. The Forge is the strategy factory inside Lynx-Forge: scout ideas, optimize parameters, pressure-test robustness, tune risk controls, compare live behavior against expectations, and keep the strategy lifecycle moving from idea to paper trading to guarded live execution.

No. Lynx-Forge is being built as a full graphical application. The goal is a visual trading workstation where normal operators can configure strategies, inspect candle data, review trades, run optimization jobs, monitor paper/live performance, and control execution without living in a terminal.

Lynx-Forge is intended to be a standalone trading application. It shares the same hardened exchange-management philosophy as Lynx-Relay, including local-first API-key handling, webhook ingestion, exchange connectivity, order routing, trade logging, and Telegram-style operator alerts. Lynx-Relay remains the focused webhook bridge; Lynx-Forge is the full research-to-execution trading station.

No. You own your stack. Lynx-Forge is designed to run on your own computer or VPS, and your exchange API keys stay on that machine. Secrets are stored locally in an encrypted vault using the same vault approach as Lynx-Relay. We do not want your keys, and the product is being built so we do not need them.

The first Lynx-Forge deployment is planned around the same exchange foundation as Lynx-Relay, focused on spot trading first: Kraken, Binance.US, Gemini, Binance Global where available, and Alpaca support where applicable. The exact production support matrix will be finalized before release.

That is the core idea. Strategies are designed around Python plugin scripts so users can create, import, test, and evolve their own logic without modifying the core executable. Built-in Signal Lynx strategies and examples provide the on-ramp, but the long-term mission is independent strategy development.

Yes. The product direction includes built-in and proven Signal Lynx strategy families such as Super-AO and Gypsy Bot style modules, alongside user-authored plugin strategies. The goal is to give operators both a clean starting point and room to build their own edge.

That is on the intended architecture path. Lynx-Forge is being built so advanced users can go beyond fixed presets and bring their own classification, filtering, or optimization logic where appropriate.

Paper trading is the live-candle validation stage. After a strategy passes historical testing, optimization, walk-forward checks, and stress validation, it can be promoted into monitored paper trading so real-time behavior can be compared against the backtest evidence before the strategy is considered for live money.

Yes. The intended workflow does not stop at research. Lynx-Forge is being built to run qualified strategies in paper trading and, when the operator explicitly chooses, guarded live spot trading. Live execution is paired with risk controls, order tracking, exchange state checks, logs, alerts, and guardrails to help protect the portfolio.

The intended monitor workflow includes reconciliation against expected backtest behavior, portfolio progress tracking, drift detection, risk guardrails, panic-stop style controls, and reoptimization paths. The goal is to catch strategy decay before it becomes a real-money problem.

Rolling optimization is the planned workflow for periodically refreshing strategy and risk-management variables against changing market conditions. The goal is to improve real-world PnL, reduce drawdown, and preserve the user's portfolio by keeping strategy settings aligned with the market instead of frozen in an old backtest.

Lynx-Forge requires an internet connection for live data, monitoring, and order execution. If the computer, VPS, or connection goes down, Lynx-Forge is designed to reconcile when it comes back online by checking exchange state, open orders, fills, balances, and strategy status before resuming normal operation.

For now, we are targeting the same baseline as Lynx-Relay, but final requirements are still being validated. Normal monitoring and execution should be lightweight, but strategy research, optimization, Monte Carlo testing, and walk-forward analysis can become CPU-heavy depending on symbols, timeframes, history depth, and search settings.

The product direction includes detailed execution controls for how orders are placed, where they route, which exchanges are used, what sizing method applies, and whether orders are value-based, percentage-based, or tied to strategy-specific parameters. It is being built for algo traders who care about execution details.

Yes. Lynx-Forge is intended to include candle data inspection, trade plots, equity curves, strategy diagnostics, trade logs, and artifact history so operators can inspect not just the result, but why the result happened.

AI and LLM-assisted workflows are on the development slate, but they are not the core promise of the first teaser. The core promise is the trading station: strategy creation, optimization, validation, monitoring, paper trading, live execution, and portfolio protection.

No. Anybody promising guaranteed trading profits is selling smoke. Lynx-Forge is being built to improve the process: stronger evidence, cleaner strategy lineage, stricter validation gates, rolling optimization, risk controls, and fewer leaps of faith before a strategy gets near live capital.

It is still in active development. The teaser page is going live early so interested operators can see where the platform is headed and get on our radar before the first public release.