Everything runs on Google Cloud Platform, primarily in US regions today. Each service scales on Cloud Run. Your data lives in Cloud SQL running PostgreSQL, your files in Cloud Storage, and everything is encrypted in transit and at rest — TLS 1.2 or higher on every request, standard AES-256 for data at rest.
You don't manage any of it. You point a domain at Giant Context and the site is live, served from a CDN close to your visitors, with HTTPS handled for you. No servers to patch, no deployment pipeline you set up when tired.
Add the domain you own, follow the DNS steps at your registrar, and Giant Context provisions SSL and serves the site. You can also assign a verified project domain to a specific site, so one organization can run several sites on their own addresses. A staging subdomain is provisioned for you when you want to review a site before the root domain moves.
Automated daily backups of every database.
Restore to any point within a 30-day window.
Download a full JSON and CSV dump of your project on demand, any time.
Files sit on GCP's standard, redundant object storage.
What ships is public. The changelog shows every change as it lands, and a health surface shows the current state of the services. The status page exists but is new, and it isn't yet watched by an independent external monitor — moving to one is on the list.
There is no formal SLA during alpha. Our target is a first response within an hour during business hours, best-effort outside them, with one person on call. Data residency is US regions today; EU residency is an enterprise option on the roadmap, not shipped. If you need EU residency or a written SLA now, this isn't your tool today — and we'd rather tell you than invent a date we can't hit.
Custom domains with SSL are supported today. Bring a site over, review it on a staging subdomain, and cut over when you're sure. If you have a specific hosting or compliance question, ask in chat — the AI answers from the trust center.