Case studies
In production · Dominican Republic

WELLNET ISP

How we operate an entire ISP with our own software.

WELLNET is our Internet provider in the Dominican Republic. Every customer, every invoice, every router, every e-CF sent to DGII goes through software we write, operate, and improve ourselves. It’s the real-world lab that validates everything we offer.

1,506

Customers in DB

full WELLNET history

1,140

Active connections

running in production today

25,360

Invoices issued

since May 2024 (~21k paid)

2+ years

In production

since May 2024 without interruption

The challenge

Running a serious ISP in DR without depending on closed software.

When we launched WELLNET, most local ISPs depended on expensive proprietary billing, poorly integrated with MikroTik, without real support for DGII electronic documents, and without decent portals for their end customers.

We needed: recurring billing that wouldn’t fail at month-end, native network integration (PPP, Hotspot, bandwidth, late-payment suspensions), e-CF for DGII compliance, and a system that scaled with the business without vendor lock-in.

The answer wasn’t to buy — it was to build, operate, and improve based on real use.

The solution

ISP-CORE: the SaaS born from operating a real ISP.

We built ISP-CORE as multi-tenant SaaS: WELLNET is tenant 1, but the architecture from day zero assumed other ISPs would come. Today it’s the same software we use to serve thousands of our own customers.

In parallel we built our own PSFE provider certified by DGII so we don’t depend on third parties for e-CF. And we set up WellTech Bot on WhatsApp as a support and collection channel.

On the network side, we set up WireGuard multi-ISP between MikroTik routers distributed in customer routers. That gives us upstream backup, captive-portal late-payment portal, and centralized observability.

Deployed stack

One stack, not a zoo.

Everything runs on the same VPS, in Docker, behind Caddy. If something breaks, we know exactly where to look.

ISP-CORE

Multi-tenant Next.js SaaS — billing, CRM, portals

MikroTik APIs

PPP/Hotspot, bandwidth control, monitoring

WireGuard multi-ISP

late-payment portal and upstream backup

PSFE DGII

our own certified provider, E31 + E32 live

Postgres + Prisma

transactional data, DB per tenant

Caddy + Docker

25+ containers on GCP VPS with automatic SSL

Prometheus + Grafana

24/7 observability

Twilio + Claude

WellTech Bot as WhatsApp support channel

What changed

Every feature passed the "does your own ISP rely on it?" filter.

  • Month-end without working weekends — recurring billing generates invoices and notifies late payers on its own.
  • e-CF issued in production to DGII (E31 and E32 live), no certificate custody by a third party.
  • Captive portal for late payers via WireGuard running on real routers — not a mockup.
  • 24/7 WhatsApp support with a bot that classifies and escalates critical issues to humans.
  • Network growth without depending on a single upstream — WireGuard multi-ISP with automatic failover between providers.

What’s next

Upcoming milestones (2026–2028)

Activate IPv6 dual-stack once block assignment and BGP announcement are complete, starting with customers on compatible CPE.

On-net CDN with local caches to reduce latency toward major content providers.

Coverage expansion with INDOTEL authorization in new Cibao zones.

Open ISP-CORE to more ISPs in the country as the platform supports operations without our daily intervention.

Run an ISP or about to start one?

Let’s talk. If WELLNET can run on it, so can your ISP.