Installing DRADIS

Subscribe on the AWS Marketplace listing, then launch from the AMI on t3.medium or larger. Before you open the dashboard, restrict the security group: ports 80 and 443 to your own address only, and port 22 only if you want SSH.

The Control Tower dashboard controls real money once you provide venue credentials. Treat reaching it exactly as you would treat an exchange login, and do not leave it open to the internet.

Open https://<instance-public-ip>/ in a browser. The instance generates its own TLS certificate at first boot, so your browser will warn that the certificate is self-signed. That is expected on a fresh instance.

Sign in with user admin and your EC2 instance ID as the password. The instance ID is a first-run claim token rather than the standing credential: the setup page immediately requires you to create an admin password, which is hashed and becomes the real one. The instance ID stops working at that point.

Select Kalshi, Polymarket International or Polymarket US in the setup page. All three binaries ship in the image, but one instance trades one venue at a time.

The change applies when the engine restarts. Restart from the setup page when prompted.

Venue API credentials are entered in the setup page and stored on your instance. They are never transmitted anywhere else, and there is no external service in the trading path.

Signal source keys, such as equity market data, are optional and shown separately with a required, recommended or optional tag. A signal source with no key simply idles and publishes a neutral snapshot, and the remaining strategies operate normally. You can add these later.

Conservative, balanced and aggressive profiles can be applied in one click and then adjusted individually. Conservative is the compiled default and the right starting point.

Applying a profile does not turn ghost mode off. Going live is always a separate, deliberate action.

A new install starts in ghost mode, which simulates fills against live order books without placing an order. Leave it on until you have watched the strategies act on real market data and understand why each one is trading or holding.

The dashboard names the specific gate blocking every idle strategy, so inaction is always explained. A strategy sitting still is reporting a reason, not failing.

Turn ghost mode off from the Control Tower when you are ready, and fund the venue account with an amount you are prepared to lose.

Then confirm it actually applied, before you rely on it. Open the Console view and watch a few minutes of output. Every simulated fill is logged with a ghost marker: GHOST_MODE on Polymarket International, and a 👻 line reading ghost entry on Polymarket US and Kalshi. If those keep appearing after you switch, the change has not reached the squadrons already running and you are still paper trading. Restarting does not clear it. Contact support rather than assuming it worked.

Every strategy can be disabled individually, and every risk parameter is tunable from the browser and applies without a restart.

The advisor reviews session history and proposes configuration changes with written reasoning. It runs against Anthropic, any OpenAI-compatible endpoint, or a local Ollama model, and defaults to recommend-only. Higher autonomy tiers, which apply changes within bounds you set, are opt-in.

Once the instance is configured the way you want it, export a configuration bundle from the Instance Migration panel in the setup page. This is the same bundle used to move to a new version, and it is worth having before you need it.

The bundle contains credentials, including your wallet key. Store it as securely as you would a private key.

Check the security group first. Ports 80 and 443 must allow your current address, and a changed home IP address is the most common cause of a dashboard that worked yesterday.

If the page loads but the login is rejected, confirm you are using the EC2 instance ID rather than the instance name, and that you have not already set an admin password on this instance. Once set, the instance ID no longer works.

If the engine reports missing credentials after a restart, the venue selected in setup and the credentials entered must match. Selecting Kalshi while holding only Polymarket keys leaves the engine idle by design rather than trading with the wrong venue.