SwiftRoute — Website

*SwiftRoute — Website

The marketing website for SwiftRoute, the communication-orchestration platform for MENA. It connects your apps to multiple SMS providers and directly to WhatsApp via the Meta Business Platform through a single API and dashboard — with automatic failover, intelligent routing, and full cost control.

One platform for every message. Every provider. Every channel.

✨ Highlights

Bilingual (EN / AR) — full English and Arabic versions with proper LTR/RTL handling, toggled live in the page.

Animated message-flow diagram — an interactive SVG hero showing a message's journey from your app, through SwiftRoute orchestration, out to providers, and onto the user's phone. Click any provider to take it down and watch traffic reroute.

Developer code samples — copyable POST /api/v1/SMS/send examples in Shell, Node.js, PHP, and Python.

Contact / demo form — lead capture with name, work email, company, monthly volume, and message.

Scroll-reveal animations and responsive layout down to mobile.

🧩 What SwiftRoute does (sections on the page)

Section Summary

Why SwiftRoute Multi-provider orchestration, direct WhatsApp via Meta (no resellers), failover & high availability.

Features Intelligent routing, cost transparency & reconciliation, unified dashboard & reporting, one API for many providers, built for MENA, enterprise-grade security.

Developers A single documented API replaces every provider-specific integration — SMS and WhatsApp included.

Contact Tailored pricing; regional phone numbers (KW, AE, EG) and email.

🛠️ Tech & structure

The site is built as a single self-contained design component — no build step, no dependencies to install.

.

├── SwiftRoute Website.dc.html # Source (editable design component)

├── SwiftRoute Website.html # Standalone, self-contained build

├── support.js # Runtime that powers the .dc.html

├── assets/ # Logos & SVG art

├── export/ # Exported artifacts

└── README.md

Type: IBM Plex Sans, IBM Plex Sans Arabic, and IBM Plex Mono (loaded from Google Fonts).

Styling: inline styles only — no external CSS framework.

No backend required for the static site; the contact form is wired to a submit handler.*