VMGate Cloud Public beta

Managed cloud platform for operators running multiple GSM termination endpoints. The cloud orchestrates SIP and routes traffic to multi-profile VMGateClient devices — with native GSM audio through the VMGate USB audio dongle.

Free tier is VMGate Cloud only. VMGate Classic is $99 per device — request a license.

Now live

SMS outbound is live

Something big just landed on VMGate Cloud. Send SMS through the same VMGateClient fleets you already run. Manage Connections, rates, routing, and history in the tenant portal. Connect your switch with an SMS connection (SMPP) when your plan includes SMS. Choose Voice or Voice + SMS on Subscription — prices match the portal catalog.

Voice was the foundation. SMS outbound is here. And more to come.

  • SMS outbound on your existing fleets
  • Portal SMS workspace built for operators
  • SMPP SMS connection for your switch
  • Voice + SMS on Cloud plans
Get started View plans Open portal

Who VMGate Cloud is for

VMGate Cloud is built for tenants — operators who run a fleet of phones, manage downstream customers and resellers, and need centralized routing, billing, and operations — not for a single DIY handset registered to your own Asterisk box (see VMGate Classic).

How VMGate Cloud works

VMGateServer sits on the boundary between the public Internet (customer SIP and SMS ingress) and your isolated VMGate network (handset control links). Each field phone runs VMGateClient. Voice uses the SIM plus a USB audio dongle; SMS outbound uses the SIM path and does not require the dongle.

VMGate Cloud architecture — SIP and SMS ingress, VMGate network, and field phones Customer SIP and SMS traffic reach VMGateServer on the public Internet. VMGateClient phones join the tenant VMGate network. Voice uses USB audio dongles; SMS outbound uses the SIM without requiring a dongle. PUBLIC INTERNET Customer SIP · SMS connection (SMPP) · tenant portal (HTTPS) VMGATE NETWORK Encrypted tenant network · VMGateClient control · voice + SMS outbound · isolated per tenant Customer SIP switch Voice traffic Customer SMS switch SMPP · SMS outbound Tenant portal HTTPS VMGateServer Public ingress + tenant VMGate network member SIP front-end SMS (SMPP) Orchestrator Portal API Billing · CDR · SMS · routing · VMGateClient registry Voice + SMS outbound on the same fleets 1 SIP / RTP 5 SMPP SMS Handset VMGateClient voice + SMS USB audio dongle ↕ GSM Mobile carrier Handset VMGateClient voice + SMS USB audio dongle ↕ GSM Mobile carrier Handset VMGateClient SMS ready No dongle required SIM · SMS out ··· more handsets 2 DIAL · SMS · control 3 Call audio (dongle) 4 Portal
VMGateServer receives customer SIP and SMS (SMPP) on the public Internet and participates in your tenant VMGate network. Handsets join with VMGateClient. Voice uses the SIM and USB audio dongle; SMS outbound uses the SIM and does not require the dongle.
① SIP — Customer switch sends SIP to the cloud SIP front-end (public Internet).
② VMGate network — Orchestrator selects a handset and sends DIAL or SMS dispatch over the tenant VMGate network.
③ Call audio — GSM voice path through the USB dongle (native-quality bridge).
④ Portal — Networks, join codes, routing, SMS workspace, and dongle setup.
⑤ SMS outbound — Customer SMS switch connects via SMPP; messages go to VMGateClient SIMs. No USB dongle required for SMS.

Call & SMS flow (summary)

  1. SIP traffic arrives at the cloud SIP front-end; SMS arrives via SMPP when your plan includes SMS.
  2. The orchestrator selects a VMGateClient and instructs it to place the GSM call or send SMS over the VMGate network.
  3. Voice audio flows through the USB audio dongle; SMS uses the SIM path without a dongle.
  4. Handsets are provisioned from the tenant portal; dongle firmware via Dongle management when you run voice.

What you manage in the portal

  • Account and subscription (Voice or Voice + SMS)
  • VMGate networks and ingress
  • VMGateClient onboarding and policies
  • SMS workspace (Connections, rates, routing, history)
  • Customers, trunks, routing, rate plans, billing

Tenant portal (screenshots)

Operate VMGate Cloud from the browser — dashboard, handset fleet, onboarding, networks, and routing. Jump: Dashboard · VMGateClients · Map · Onboarding · Networks · Routing. Open tenant portal

English UI shown; portal available in seven languages. Sensitive IPs, numbers, codes, and locations redacted on these marketing captures.

Dashboard

Plan capacity, live calls, quick actions, and recent call activity at a glance.

VMGate tenant portal — dashboard with status bar, KPI cards, and recent calls
Dashboard — ports, online VMGateClients, customers, and call history.

VMGateClients

Fleet view — online/offline, SIM slots ready, and per-device status.

VMGate tenant portal — VMGateClients table with status and SIM slots
VMGateClients — handset registry and slot readiness.

Map

Geographic view of deployed handsets (location redacted on this capture).

VMGate tenant portal — VMGateClients map view
Map — last-seen location per VMGateClient.

Join codes

Generate codes to onboard handsets onto the correct VMGate network.

VMGate tenant portal — Join Codes management
Join codes — per-network onboarding tokens.

Client QR codes

Stable VMGateClient APK download for installers enrolling hardware.

VMGate tenant portal — Client app QR download page
Client QR Codes — scan-to-install VMGateClient.

Networks

Multiple VMGate networks per tenant — each with its own SIP ingress and handset pool.

VMGate tenant portal — Networks list with SIP ingress
Networks — isolated VMGate networks and ingress endpoints.

Dialpeers

Connect each retail customer to a routing rule and trunk rate plan.

VMGate tenant portal — Dialpeers routing configuration
Dialpeers — origin customer → routing rule → trunk.

VMGateClient app (screenshots)

Representative handset captures — multi-profile app connected to VMGate Cloud. Jump: Main · Profiles · Settings & OTA · IVR · Dongle · Earnings. Phone minimum requirements (no root): VMGateClient features (Cloud).

VMGateClient on your phones

Each handset runs VMGateClient — multi-profile, live voice status, and per-SIM control. SMS outbound uses the SIM path and does not require the USB audio dongle (dongle is for voice/GSM audio). Real bench captures; not mockups.

VMGateClient main screen — dual SIM slots enabled, connected to VMGate Cloud
Dual SIM ready — both SIM slots enabled on a voice-capable handset (USB audio dongle for GSM call audio when you place calls).
VMGateClient main screen — connected, SMS-capable without USB audio dongle attached
SMS without dongle — same VMGateClient, no USB audio dongle attached. SMS outbound uses the SIM; the dongle is only required for voice/GSM audio.

Multiple profiles on one phone

VMGateClient is multi-profile: each profile is a saved VMGate network connection (tenant network, credentials, and policy). Add profiles from the app, switch which one is Active, and return to the main screen — no reinstall when you move a handset between networks or keep a staging profile alongside production.

VMGateClient Profiles list — multiple VMGate network profiles, one active, add profile
Profiles — list saved networks; tap to activate; Add profile for onboarding another VMGate network on the same device.

App language & over-the-air updates

VMGateClient is multi-profile and multilingual: app language is independent from the phone OS. Built-in Check for updates delivers OTA app and VMGate Audio helper builds without reinstalling from the portal.

VMGateClient Settings — app language picker, OTA update check, diagnostics including USB dongle detected
Settings — choose app language (seven languages in production portal); check for updates; diagnostics show cloud link and USB dongle status.

Seven app languages

English, French, Spanish, Italian, Arabic, Russian, and Simplified Chinese — same set as the tenant portal.

OTA in the app

Tap Check for updates to pull VMGateClient and VMGate Audio builds when Startel publishes them.

Field diagnostics

Connection state, active network profile, and USB dongle detection — before you escalate to support.

Screenshots from representative handsets; sensitive IDs redacted where noted.

Internal IVR for inbound GSM

In Settings, configure Incoming GSM calls — reject all inbound GSM or play prepared audio from a folder after a short ring (on-device IVR, no external media server).

VMGateClient Settings — internal IVR, audio folder, prepare files, max duration
Incoming GSM calls — folder picker, file preparation, max IVR duration.

VMGate Dongle Manager

VMGateClient includes Dongle management — flash and maintain the VMGate USB audio dongle from the handset. The app walks operators through port selection (flash vs operational), runs the firmware update on the phone, and confirms when the board is ready to move to the left port for GSM audio.

VMGate Dongle Manager in VMGateClient — guided dongle flash from the phone
Dongle Manager — connect to the right port for flashing; tap Flash the dongle now when enabled.

Per-profile earnings in the app

Each VMGateClient profile includes an Earnings panel — earned, to be paid, and paid totals by range (today, week, month, year). Figures are authored on VMGateServer; the app shows read-only snapshots per active profile.

VMGateClient profile earnings — earned, to be paid, and paid for this month
Profile → Earnings — month view with earned, to be paid, and paid (illustrative amounts on this marketing capture).

Screenshot uses representative USD amounts for layout; your devices show live totals from VMGateServer after the App syncs.

Start on the free tier

Create a free account — not a time-limited trial. When you need more concurrent capacity, paid plans start from $200/month (Voice) or choose Voice + SMS. Details on Plans and in the portal. SMS outbound is live — and more to come.

The tenant portal is available in English, French, Spanish, Italian, Arabic, Russian, and Simplified Chinese. This website is in English.

Create free account Compare with Classic