System Architecture
How Twilio Tools works — pipeline flow, system diagram, and live status
How Twilio Tools works — pipeline flow, system diagram, and live status
289 subaccounts through automated A2P 10DLC compliance
Next.js 16 + Python FastAPI on Hetzner, proxied via NPM with SSL
10 routes — every page is a Server Component with Suspense streaming
| Route | Description |
|---|---|
| Dashboard | Quick links to all features |
| Company | Search by SID, name, or Pete DB ID. Pipeline phase bar per company. |
| A2P Onboard |
43
API Endpoints
289
Subaccounts
10
Frontend Routes
12
Cursor Rules
289 Twilio subaccounts need A2P 10DLC compliance. Each requires a 5-step chain: customer profile, trust product, brand registration (1-7 day TCR wait), messaging service, and campaign. Manual execution is not viable.
A background cron loop auto-advances companies with complete data through the pipeline. A separate batch scan emails companies that need action. Safety gates prevent accidental live operations.
Python FastAPI (43 endpoints, Playwright for crawling) + Next.js 16 frontend. Server Actions auto-generated via AST parser. Both containers on Hetzner behind NPM reverse proxy with SSL.
confirm_production=true| 7-step pipeline wizard. Create profiles, brands, campaigns. |
| Analytics | Error trends across all 289 subaccounts. |
| Errors | Twilio error code lookup with resolution guides. |
| Phone | PhoneInfoga — carrier, location, OSINT. |
| Settings | DRY RUN/LIVE, cron interval, email cooldown, safety gates. |
| Architecture | This page — diagrams, route map, live status. |