One Backbone.
Every Product.
Every TypexAI product — the website, Bardo Web, TypexAI Cloud, and note sync — runs on the same private, battle-tested backbone.
Every Connection, Visualized.
All traffic enters through Cloudflare's edge and is routed to the service it belongs to. Nothing bypasses the edge.
01 Users → Cloudflare Edge
Every request from web, Android and Windows clients hits Cloudflare first: TLS termination, WAF filtering, and DDoS protection at the door. Nothing reaches our origin servers directly.
02 Namecheap → Cloudflare Edge
Domain registration and DNS live at Namecheap. It only answers "where do I go" — it never carries traffic, which is why it sits outside the request path.
03 Edge → typexai.dev
The website is served from our own origin server, reachable only through the Cloudflare edge — the origin IP is never exposed.
04 Edge → Bardo Web / Windows
The Bardo Web application is delivered through the edge, while notes themselves live locally in the browser — local-first by design. Bardo for Windows is built on this same web shell, so the desktop app shares the identical delivery path and sync channel.
05 Edge → taistat.org
Health checks run continuously to the status page origin, which is hosted separately from everything else and stays online even during outages.
06 Edge → Opety
Opety, a document workbench for legal, HR, and finance teams, is hosted on TypexAI infrastructure. Files never leave the user's browser tab — we handle delivery and edge security, never document contents.
07 Bardo Web / Android / Windows → Zurich Sync API
Note synchronization runs through our own sync backend and is shared across the whole Bardo ecosystem — Bardo Web, Android and the Windows app all stay in step through the same end-to-end encrypted channel. Notes leave each client only in encrypted form — the server never sees plaintext.
08 Bardo Web → TypexAI Cloud
Bardo Plus workspace sync is handled by TypexAI Cloud on dedicated Swiss servers, fully encrypted client-side before anything is sent.
09 Bardo Web → AI Providers
When a user connects a model, the browser calls the provider they chose — OpenAI, Gemini, DeepSeek, OpenRouter, or Perplexity — with the user's own key. This line leaves the private network: prompts never transit our backbone.
10 Private backbone → Tuta Mail
All official TypexAI mailboxes run on Tuta's encrypted email infrastructure — there is no self-hosted mail server to attack.
11 Opety → Ailos
Ailos, an independent Asia-based monitor, performs external availability checks on Opety's public pages only — reachability, not workbench files.
12 Opety → Tuta Mail
Opety's support mailbox (opety@typexai.dev) rides on the same encrypted Tuta infrastructure as every other TypexAI mailbox.
The private backbone itself
The dashed boundary marks one private network. Every origin inside it — typexai.dev, Bardo Web, taistat.org, Zurich Sync, TypexAI Cloud — reaches the others over an internal mesh that is not routable from the public internet. Membership is the connection; there is no exposed port between them.
Verified Against Real Attacks.
TypexAI infrastructure has been verified against external threats — hacking attempts, cyberattacks, and DDoS.
- In-house security testing. Our infrastructure is stress-tested inside a closed, isolated environment using exploit and load-testing tools developed by TypexAI engineers.
- Powerful autonomous AI agents. Uncensored AI agents — equipped with known real-world exploits and attack tooling — are given controlled access to attempt to breach our systems. To date, none have succeeded.
- Continuous verification. These exercises run regularly, so potential weaknesses are identified and resolved by us before anyone else can find them.
Verify It Yourself.
Live uptime for every product on this backbone is published on our independent status page.
Open TAI Status