Guard AI Trading is building a controlled stack for AI-assisted execution, symbol passports,
server-side licensing, Telegram administration, and operator-grade deployment. The public site is
being expanded now. The backend is already online and secured with live HTTPS.
Certificates are live for the root domain, `www`, and the license subdomain.
API
Health endpoint online
The production license API already answers through the public domain.
Backup
Daily retention enabled
SQLite snapshots are scheduled through a dedicated system timer.
Build
Website expanding next
Public presentation, screenshots, and release material are being added now.
What is already in motion
This is not just a domain placeholder. The public surface is still being polished, but the operating
layer behind it is already real and production-routed.
Execution
Breakout-driven workflow
Structured entry logic, multi-timeframe context, controlled risk, and an execution path designed for
disciplined operation instead of impulsive signal chasing.
Optimization
ML passports and parameter maps
Symbol-specific model passports and configuration maps are part of the operating model, not a side note
added after the trade logic.
Infrastructure
Server-side license control
Telegram-administered licensing, server verification, session-based AI access, daily backups, and
managed runtime services are already deployed on the VPS.
Live production surface
The rollout now uses the public domain, HTTPS, reverse proxying, and a dedicated license endpoint. That
means the website and the licensing contour can move independently without breaking each other.
$guardaitrading.com -> public landing page
$www.guardaitrading.com -> same public landing page
$license.guardaitrading.com -> license API and admin runtime
$HTTPS -> automatic renewal through Caddy and Let's Encrypt
$Daily backup timer -> active on the production server
Rollout path
The public website will keep evolving, but the launch sequence stays controlled: infrastructure first,
then the presentation layer, then broader distribution and onboarding.
Phase 01
Infrastructure live
Domain, HTTPS, reverse proxy, production license service, Telegram admin bot, and automated backups are
already in place.
Phase 02
Public presentation
Product story, screenshots, strategy visuals, FAQ blocks, and cleaner onboarding text are now being
added to the landing page.
Phase 03
Distribution layer
Windows and Linux delivery, operator documentation, and a smoother private release flow will sit on top
of the already running backend.