Self-hosted or hosted Arabic LLM? A 30-second guide Silent video: no voiceover, music or sound effects. This transcript repeats every on-screen word and describes each scene. The film includes the topic label "Self-hosted or hosted LLM", the note "Illustrative diagram", the TecnoStack logo and progress numbers 1, 2, 3, 4, 5, 6. Elements enter and leave during transitions; in portrait, the closing sign-off replaces the footer. [0:00–0:05] Beat 1 of 6 (intro) Kicker: ARABIC LLM DEPLOYMENT Headline: Choose how your Arabic model runs Support: Match deployment to the workload Diagram (decision paths): Workload; Self-hosted; Hosted API Connections: Workload → Self-hosted; Workload → Hosted API Highlighted: Workload Scene: Branching diagram: Workload, Self-hosted, Hosted API. Connections: Workload to Self-hosted; Workload to Hosted API. Emphasis: Workload. [0:05–0:10] Beat 2 of 6 (step1) Kicker: 01 Headline: Check four decision factors Support: Before comparing costs Diagram (evidence checklist): Data location; Version control; Team capacity; Evaluation Highlighted: Data location Scene: Comparison without scores: Data location, Version control, Team capacity, Evaluation. Emphasis: Data location. [0:10–0:15] Beat 3 of 6 (step2) Kicker: 02 Headline: Read each checkpoint's terms Support: Check license and context limits Diagram (flow): Model card; License; Context; Fit decision Connections: Model card → License; License → Context; Context → Fit decision Highlighted: License Scene: Flow: Model card, License, Context, Fit decision. Connections: Model card to License; License to Context; Context to Fit decision. Emphasis: License. [0:15–0:20] Beat 4 of 6 (step3) Kicker: 03 Headline: Plan the operations work Support: Assign an accountable owner Diagram (layered stack): Re-evaluation; Monitoring / patches; Inference server; Capacity Connections: Re-evaluation → Monitoring / patches; Monitoring / patches → Inference server; Inference server → Capacity Highlighted: Monitoring / patches Scene: Layered diagram: Re-evaluation, Monitoring / patches, Inference server, Capacity. Connections: Re-evaluation to Monitoring / patches; Monitoring / patches to Inference server; Inference server to Capacity. Emphasis: Monitoring / patches. [0:20–0:25] Beat 5 of 6 (step4) Kicker: 04 Headline: Enforce approved data routes Support: Block fallback across data boundaries Diagram (hub and spokes): Routing policy; Self-hosted; Hosted; Audit log Connections: Routing policy → Self-hosted; Routing policy → Hosted; Routing policy → Audit log Highlighted: Routing policy Scene: Network: Routing policy, Self-hosted, Hosted, Audit log. Connections: Routing policy to Self-hosted; Routing policy to Hosted; Routing policy to Audit log. Emphasis: Routing policy. [0:25–0:30] Beat 6 of 6 (close) Kicker: TECNOSTACK Headline: Keep a tested exit plan Support: Read the full guide Diagram (timeline): Simplest fit; Decision record; Re-evaluate Connections: Simplest fit → Decision record; Decision record → Re-evaluate Highlighted: Decision record Sign-off: TecnoStack logo and tecnostack.com Scene: Sequence: Simplest fit, Decision record, Re-evaluate. Connections: Simplest fit to Decision record; Decision record to Re-evaluate. Emphasis: Decision record.