Skip to content
SMSRay

About SMSRay

OTP that actually arrives in Nepal

SMSRay exists for one reason: a verification code or an order update is only useful if it reaches the phone in time. So we send from real local numbers and tell you honestly what happened to every message.

SMSRayOTPReceiptAlertReplyReminderOTP

Why we built it

The message that matters most is the one that didn't arrive

Every app that signs people in with their phone number depends on a text message. When that code arrives late, or never, the person on the other end can't log in, can't pay and often doesn't come back.

SMSRay sends OTP, transactional and two-way SMS for businesses that reach people in Nepal. Instead of relying on a distant gateway, messages go out from a pool of company SIM cards in phones we operate, so they arrive the way a message from a person does.

Around that pool sits a platform built for developers: a clean API, a live dashboard, signed webhooks, built-in OTP with sensible limits, and billing that refunds what fails.

What makes it different

Built around the phone in someone's pocket

Four decisions shape everything SMSRay does.

Real local numbers

Messages leave company-owned SIM cards on NTC, Ncell, Smart, in Android phones we manage ourselves. Recipients see a normal local number, not an unfamiliar sender.

Routing that thinks

On-net SIMs first, paced so no phone hits Android's send limit, daily quotas tracked on Nepal time, and stale or failing SIMs skipped. A failed send gets one retry on another SIM.

You only pay for what could be sent

Every message is charged per segment from a prepaid balance, and anything that finally fails is refunded to your balance automatically.

Receipts you can build on

Status moves from queued to sent to delivered, and you hear about it through signed webhooks retried up to 8 times, or by polling the API.

Principles

How we make decisions

Honest delivery status

We report what actually happened to each message, including failures. We don't mark a message delivered until the network says so, and we don't hide a failure behind a vague status.

Privacy by default

OTP codes are stored only as hashes and hidden in logs. API keys and session tokens are stored as hashes too. We process recipient data to send your messages, never to advertise.

Developer-first

A small REST API with one auth header, one error shape, idempotency keys for safe retries and clear documentation. You should be sending your first message within minutes of activation.

Built by Lacspace

A focused product from a global technology company

SMSRay is built and operated by Lacspace, a country-neutral technology company that builds software and AI products for customers around the world. Lacspace runs many products; SMSRay is the one focused on messaging for Nepal.

The legal entity behind SMSRay is Lacspace Corporation Pvt. Ltd., which signs your agreement and operates the SIM pool, the API and the portal.

Visit lacspace.com
  • Our own phones and SIMs

    The sending pool is owned and managed by Lacspace, not rented from a reseller.

  • One accountable company

    The same team builds the API, runs the pool and answers your support email.

  • Shipped like software

    SMSRay is built with the engineering practices Lacspace uses across its products.

Let's get your codes delivered

Create a workspace with your phone number or email. Lacspace reviews and activates new workspaces, then you're ready to send.