Transparency
Frontend
React 18 + Vite 8 application, TypeScript, Tailwind, Radix/shadcn components. Static build served as SPA. FR / EN / HT i18n via i18next and `/:locale/…` routes.
Transparency
System architecture
Real facts about the public beta platform — no fictional datacenter maps or invented metrics.
This page describes the current repository and deployment state. Productivity apps (Mail, Docs, Drive) are not separate applications in this monorepo yet.
Simplified flow
Browser (SPA)Static hosting (Azure SWA / Vercel-compatible)Supabase (Auth · DB · avatar Storage)
External services (e.g. Palmis, GTLNav in research)
UI preview · Planned
Transparency
Identity layer (GTL ID)
Supabase Auth for authentication. `profiles`, `user_product_memberships`, `roles` tables and RLS policies. Account hub `/account`, console `/account/console`, settings, and avatar storage.
Transparency
Data & storage
PostgreSQL via Supabase for identity and product catalog. Storage buckets: `avatars` (public, profile) and `gtl_drive` (private, user file MVP) with `user_drive_files` metadata table.
Transparency
Deployment
GitHub Actions CI to Azure Static Web Apps (workflow in repo). Vercel config (`vercel.json`) with SPA rewrites. No application Node server in production.
Transparency
Ecosystem structure
Marketing pages: infrastructure, security, connectivity, public roadmap, technical journal. Palmis Search is a live external service (`palmis.godtechlabs.com`). GTLNav is a hosting/deployment portal in research — temporarily unavailable (infrastructure migration in progress).
Transparency
Security model
HTTPS, Supabase sessions, RLS on user data. Security & Trust Center = documented philosophy. No displayed SOC2/ISO certification.
Transparency
Not included today
No Supabase Edge Functions in this repo, no VPS/Kubernetes orchestration from UI, no measured public uptime metrics, no hyperscaler-style cloud console.