Use cases

What companies run on SOVA

Branches, phones, cameras, servers and people on one private network — on one VPS you own, with nothing opened at the branches.

A phone system across every branch

  1. 1 · The problem

    The IP PBX sits at the main branch. Other branches, staff at home and mobile extensions need it, but opening SIP and web ports to the Internet invites attacks, and the vendor's cloud plan costs every year and limits call time.

  2. 2 · With SOVA
    • The PBX stays on a private network; branch phones register on its private address through the tunnels
    • The PBXs of two cities trunk to each other inside SOVA, with no port open at either end
    • Mobiles get a remote user with always-on WireGuard and use the vendor's softphone app directly
    • Desk phones away from a branch connect over OpenVPN with their own certificate
    • One public number on the main PBX, an extension range and a ring group per branch
  3. 3 · The result

    A real customer moved every remote extension off the vendor's cloud subscription and now runs the whole phone system through SOVA, programming the PBX through SOVA's API.

Retail chains, kiosks and small branches

  1. 1 · The problem

    Dozens of small shops behind consumer lines, carrier NAT or a 4G SIM, each with a till, a phone and a camera that head office must reach.

  2. 2 · With SOVA
    • A small MikroTik per shop (hAP ax lite, or LTE6 with a SIM) becomes a site in two minutes
    • Works behind NAT, CGNAT and 4G: the branch dials out, nothing to open at the shop
    • Every shop gets the same layout: tills, phones and cameras on the same third octet everywhere
    • Router security in one click; app and website blocking for staff networks
  3. 3 · The result

    New shops are added without touching the others — they learn each new branch by themselves.

Cameras from every branch to one recorder

  1. 1 · The problem

    Recorders and cameras at every site, viewed from head office, without port forwards on each branch line.

  2. 2 · With SOVA
    • Head office reaches every camera by its real address — no NAT inside the network
    • Policies let only the security team's network reach the camera networks
    • Live traffic and Performance show which branch line limits the video
  3. 3 · The result

    One recorder or viewing station for the whole company, with nothing published on the Internet.

One ERP, accounting or file server for all branches

  1. 1 · The problem

    Odoo, an accounting package or a file server runs at headquarters; branches need it all day, reliably.

  2. 2 · With SOVA
    • WireGuard per branch with L2TP/IPsec as automatic backup: failover in about 4 seconds
    • Internal names such as erp.hq.corp for every branch and remote user
    • Direct links between branches when their lines allow it, the hub as a safety net
  3. 3 · The result

    Branches work on the central system as if they were in the same building.

Remote employees and contractors

  1. 1 · The problem

    Staff at home, on the road or abroad need some company systems — not all of them.

  2. 2 · With SOVA
    • A fixed VPN address per person, so logs and policies know who it is
    • Access per site or per network, groups, and expiry dates for contractors
    • WireGuard, built-in L2TP/IPsec or OpenVPN; QR codes and one-line installers
  3. 3 · The result

    Hand out access in a minute and take it back in one click.

IT providers and ISPs with many MikroTik routers

  1. 1 · The problem

    Many customer or tower routers behind NAT, managed one by one through Winbox and open management ports.

  2. 2 · With SOVA
    • Every router reached over its tunnel, no public management port
    • Health, updates, backups, time and DNS in bulk; traffic history per interface and per app
    • Alerts on Telegram, email and WhatsApp the moment a site drops
  3. 3 · The result

    One panel for the whole fleet, and a high-availability cluster when the hub must never stop.

Automation through the API

  1. 1 · The problem

    Operations teams want scripts, not clicks: create users, read a device's status, change a setting on a branch device.

  2. 2 · With SOVA
    • A REST API with scoped tokens for everything the panel does
    • HTTP(S) to devices inside the branches through the hub — for tools that can only use ports 80 and 443
    • Signed webhooks for site, user and alert events; every call in the audit log
  3. 3 · The result

    Daily administration — devices, addresses, extensions, permissions — done from code.

Replacing a tangle of site-to-site tunnels

  1. 1 · The problem

    Hand-built IPsec tunnels between every pair of branches, overlapping address plans and routes nobody remembers.

  2. 2 · With SOVA
    • A derived address plan: branch N owns 10.N.0.0/16
    • OSPF learns and shares every network; a branch can only announce its own block
    • A paste-ready script per branch that never touches the WAN or the default route
  3. 3 · The result

    One design for every branch, documented by the panel itself.

Use cases

The IP PBX sits at the main branch. Other branches, staff at home and mobile extensions need it, but opening SIP and web ports to the Internet invites attacks, and the vendor's cloud plan costs every year and limits call time. A real customer moved every remote extension off the vendor's cloud subscription and now runs the whole phone system through SOVA, programming the PBX through SOVA's API.

Dozens of small shops behind consumer lines, carrier NAT or a 4G SIM, each with a till, a phone and a camera that head office must reach. New shops are added without touching the others — they learn each new branch by themselves.

Recorders and cameras at every site, viewed from head office, without port forwards on each branch line. One recorder or viewing station for the whole company, with nothing published on the Internet.

Odoo, an accounting package or a file server runs at headquarters; branches need it all day, reliably. Branches work on the central system as if they were in the same building.

Staff at home, on the road or abroad need some company systems — not all of them. Hand out access in a minute and take it back in one click.

Many customer or tower routers behind NAT, managed one by one through Winbox and open management ports. One panel for the whole fleet, and a high-availability cluster when the hub must never stop.

Operations teams want scripts, not clicks: create users, read a device's status, change a setting on a branch device. Daily administration — devices, addresses, extensions, permissions — done from code.

Hand-built IPsec tunnels between every pair of branches, overlapping address plans and routes nobody remembers. One design for every branch, documented by the panel itself.

FAQ

Questions we are asked

Can SOVA carry our IP phone system?

Yes. The PBX stays on a private network; branch phones, desk phones over OpenVPN and mobile softphones over WireGuard reach it through the tunnels, and PBXs in different cities trunk to each other inside SOVA, with no SIP port open on the Internet.

Do we still need the PBX vendor's cloud subscription?

Not for remote extensions or remote management: mobiles reach the PBX over the VPN and administrators reach its web page and API through SOVA.

Our branches only have 4G. Does it work?

Yes. The branch router dials out to the hub, so carrier NAT and 4G are fine. A MikroTik LTE6 with a SIM is enough for a small branch.

Do branches need a public IP?

No. Only the hub, on your own VPS, needs a public IP.

How much does it cost?

Free for two branches and one remote user. Paid plans add branches and users; every paid plan is free for its first month.

Start with two branches, free.

One command on a fresh Ubuntu VPS. Every paid plan is free for its first month.