07Why Not Cloud
What makes this different from cloud-based voice agents
Turkish voice assistant providers in the market are predominantly cloud-based. The architectural and scale differences are decisive on cost and data sovereignty.
fig. 03 · data flow — cloud vs on-prem
voice data path
existing cloud solutions
- Service stops when internet drops
- Call-forwarding + per-minute fees
- No Turkish proper-name correction
this project · on-prem edge
proposed- Keeps running when the internet drops
- One-time hardware cost, no per-minute fees
- KVKK-aligned · voice data never leaves the premises
Axis-by-axis comparison
A concise comparison with cloud-based Turkish voice-assistant providers on the market.
| Existing cloud solutions | This project | |
|---|---|---|
| Where it runs | Cloud server | On the customer's edge computer |
| When the internet drops | Service stops | Keeps running |
| Where voice data lives | Leaves the premises (often abroad) | Stays on-premises |
| Call-forwarding requirement | Required | None — direct cellular reception |
| Turkish proper-name correction layer | Not present | Present |
| Free-form location → administrative unit | Not present | Present |
| Pre-record hallucination guard | Not present | Present |
| Pricing model | Subscription + per-minute usage | One-time hardware cost |
| Adapting to a new sector | Re-engineering | Configuration file |