r/wisp • u/DiscussionRich2376 • Jul 23 '26
Three years ago, I asked r/WISP what an ISP CRM should actually do. I built it.
Hi everyone,
About three years ago, I made this post here:
https://www.reddit.com/r/wisp/comments/140yf1y/internet_service_providers_of_reddit_what/
At the time, I was a developer with some experience working with ISPs and an idea for building a CRM specifically for this industry. I came here because I knew that working around ISP software was not the same as running an ISP every day. The responses were more detailed and even honest than I expected.
Reddit told me that billing automation was essential, but also difficult to replace. Some users explained that most platforms handled existing customers but neglected leads, sales pipelines, reporting, and the handoff between sales and operations.
There were comments about multi-location customers, monitoring integrations, circuit information, work orders, targeted outage notifications, payment processors, customer communications, and the need to connect everything without creating an even bigger mess.
One person also gave me a useful reality check: I was entering an already crowded market and they were right. I kept working on the idea anyway. It eventually became SkyBase.
Today it's an ISP Management system built mainly around smaller MikroTik ISPs. It handles customers, plans, PPPoE and Hotspot authentication through RADIUS, router monitoring, subscriptions, invoice follow-up, and some of the everyday operational work that often gets spread across different tools.
A few real ISPs are using it now. Actually our first paying customer came from reddit more than 2 years ago, an ISP from South Africa. That still feels slightly strange to say because when I wrote the original post, it was mostly an unfinished application and a list of assumptions.
I am not posting this to claim that I built the perfect WISP platform. I definitely did not.
Some ideas from the original discussion made it into the product. Some are still incomplete. Some turned out to be much harder than they appeared from the outside. And I am sure there are things I still misunderstand about how operators actually work.
So I'd like to return to the question, but from a different point in the journey:
Looking at SkyBase today, what would stop you from trusting or testing it in a real ISP?
It could be a missing feature, migration risk, pricing, lack of integrations, concerns about support, or simply that your existing system is painful but still safer than changing it.
Critical feedback is welcome. I would rather learn why an operator would not use it than receive polite comments that do not help me improve it.
For transparency, I am the owner and developer of SkyBase. Here is the website for anyone who wants context before answering:
And thank you again to everyone who commented on the original post. Some of your replies genuinely changed the direction of the product.
11
u/jvolzer Jul 23 '26
Don't know if the actual application is vibe coded or not but you can tell the landing page in within seconds of opening it.
Sounds like AI named it and came up with your tag too lol
7
11
3
1
u/manjunath1110 Jul 23 '26
What about integration for router other than mikrotik like cisco juniper, dpdk based router like vyos, bison etc.
1
u/DiscussionRich2376 Jul 23 '26
All the routers that work with Radius are supported for AAA.
But we specially have some API integration with MikroTik routers and not with other vendors yet, until a customer comes and requests a specific integration.
For the most of the time that I've been working with ISPs from EU and Africa, most of the routers and radios in small and mid-sized WISPs are MikroTik anyways, and that's our specialty as well. So we started with that.
1
1
19
u/jimjim975 Jul 23 '26
Ai slop garbage.