Technology & Cloud Infrastructure

Technology stack

The public site and application are built on:

• Next.js (React, TypeScript) — server-rendered frontend and marketing site, chosen for SSR/SSG so pages are crawlable and fast.
• Node.js / TypeScript services — application and trading-engine backend logic.
• PostgreSQL — relational storage for users, strategies, orders, trades and portfolio state.
• Redis — caching and background job/queue coordination for time-sensitive tasks like signal evaluation.
• Tailwind CSS — design system implementation for a consistent, accessible UI.

This list reflects the stack actually used to build the platform; it will be updated as the implementation evolves.

Why cloud infrastructure is needed

An algo-trading platform has workloads that a static site does not: persistent backend services, a database of user strategies and trade history, scheduled and event-driven jobs (market-data ingestion, strategy evaluation, backtest execution), authenticated APIs, and monitoring for a system where downtime or a stale risk check has real financial consequences for users.

Planned AWS architecture

The target production architecture, sized for a startup operating under a promotional AWS credit budget:

• Compute: containerized services on ECS Fargate (or a comparably managed compute service), so capacity scales with load instead of running always-on idle servers.
• Database: Amazon RDS for PostgreSQL for durable, transactional storage of accounts, strategies, orders and audit logs.
• Caching / queues: Amazon ElastiCache (Redis) for low-latency state and background job coordination.
• Storage: Amazon S3 for static assets, exported reports and backtest artifacts.
• Secrets: AWS Secrets Manager for broker API credentials and other sensitive configuration — never committed to source control.
• Networking / edge: Amazon CloudFront and Route 53 for HTTPS delivery, DNS and a single canonical domain.
• Monitoring: Amazon CloudWatch for logs, metrics, alarms and health checks on trading-critical services.
• CI/CD: a standard container build-and-deploy pipeline with separate development, staging and production environments.

Environments

Configuration is environment-based (development, staging, production) so the same application code can move between them without code changes — only environment variables and secrets differ.

Expected workloads & cost drivers

The primary cost drivers are expected to be: compute for the backend/trading-engine services, the managed database, market-data API costs (paid to third-party data providers, not AWS), and outbound data transfer. The architecture favors managed, pay-for-what-you-use services over always-on, oversized infrastructure, so a promotional AWS credit budget is used responsibly rather than burned on idle capacity.

Security posture

HTTPS/TLS everywhere, secrets never stored in source control or exposed to browser code, server-side authorization checks on every trading action, and audit logging for authentication and trading events. See the full Security page.

Important note

my ALGO agent is not endorsed, sponsored, certified or partnered with Amazon or AWS. AWS is used as third-party cloud infrastructure, the same way any software company uses a cloud provider.