Infrastructure

How SwiftQuantum is hosted and monitored

Where SwiftQuantum runs, how it is monitored, and what we do not promise. Everything is built from standard AWS services.

What runs where

Layer	Runs on	Worth knowing
This website	Static files on Amazon S3, served by CloudFront behind AWS WAF	No server, no database. Analytics only after you consent.
App backends & web apps	Containers on AWS Fargate (Amazon ECS) behind an application load balancer, Seoul region	Each product is its own service; one shared sign-in service serves all eight apps.
Data	Amazon RDS managed database and object storage, both encrypted at rest (AES-256)	Hosted in Seoul (ap-northeast-2). Deleting your account removes your sign-in data immediately; app data is removed separately.
Payments	Stripe (web) and the Apple App Store (in-app)	Card numbers never touch our servers.
AI Tutor	OpenAI (in the apps) and Anthropic (on the web)	Tutor chats are sent without your name or email.

Monitoring

01CloudWatch alarms on error rate, response latency and container health for every backend service.
02Database alarms on connections, CPU and free storage.
03An external uptime check pings each service’s health endpoint every minute.
04Sign-in failures are treated as the most severe incident, because they affect all eight apps at once.
05Every deploy is verified against the origin before it is called done.

HTTPS on every public connection (TLS 1.2 or later).
On the Q-Bio web app, compound inputs are sealed with ML-KEM-768 (NIST FIPS 203) and AES-256-GCM before they are sent.
Account deletion on request (GDPR Art. 17).

No public uptime SLA and no availability commitment on self-serve plans; Enterprise SLAs are agreed in contract.
No certifications. Our practices are aligned to published standards, but we are not certified against them.
A small team runs this and handles incidents directly. Write to support@swiftquantum.tech.

Free to start on iPhone, iPad, Mac and the web. Paid plans from $4.99/mo.

Cancel anytime in your settings.