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.
- PostgreSQL — relational storage for users, strategies, orders, trades and portfolio state, via Prisma ORM.
- Tailwind CSS — design system implementation for a consistent, accessible UI.
- lightweight-charts — TradingView's own open-source charting library, for price and indicator charts.
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.
AWS architecture
The production architecture, running entirely on AWS:
- Compute: AWS Amplify Hosting (Lambda-based), 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.
- Storage: Amazon S3 for user uploads and static assets.
- Rate limiting: Amazon DynamoDB for cross-instance request throttling.
- Email: Amazon SES for transactional account and security email.
- 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: automatic build-and-deploy on every push to the main branch, via Amplify Hosting's built-in pipeline.
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.
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
MyAlgoAgent 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.