Laravel Sms Gateway Self Hosted: In-Depth Guide

Laravel SMS gateway self-hosted — in-depth clarifies the split between your VPS and the Android SIM API. Laravel retry policies · Laravel API guide. Queues: laravel.com/docs/queues.

Devices and send volume. Docs: Developer Center.

Self-hosted Laravel ≠ self-hosted modem cloud

You own the PHP app, queue workers, and database. The SMS control plane and Android app pairing stay on the product side. That is still “self-hosted Laravel” in the way most teams mean it.

Building your own multi-tenant SMS SaaS on a CodeCanyon script is a different project — and not this guide.

How to wire Laravel to the gateway

1. API key in .env.
2. Job posts JSON with stable Idempotency-Key.
3. Webhook controller verifies HMAC.
4. OTP hash stays in your DB — not in the SMS alone.

curl -X POST "https://app.sms-gateway.app/api/v1/messages" \
  -H "Authorization: Bearer $SMS_GATEWAY_API_KEY" \
  -H "Content-Type: application/json" \
  -H "Idempotency-Key: 3f1b0c8a-9d2e-4c77-9f5a-2b6d1e0f4a83" \
  -d '{"to":["+14155552671"],"text":"Your verification code is 481920","type":"sms"}'

What you host vs what we host

Queues, retries, idempotency

Retry timeouts/5xx with backoff; fail closed on 4xx and allowance exhausted. Idempotent send.

Phone still on your desk

last-seen, charger, OEM exceptions. Overnight uptime · OTP.

Next steps

Deploy a staging job that sends one staff SMS and asserts DLR via webhook. Downloads. Free: 300 SMS lifetime.