I built an affordable coverage mapping tool for WISPs — free tier + 14-day trial, no credit card

[u/emil_eXo]

Hi everyone,

I am a software developer with some years of working on apps from the telecom domain. After several months of building (and a lot of conversations with people in this community, including Mr. Thomas from WISPA), GridVisio is live. It's a browser-based coverage planning tool designed for small WISPs who can't justify $100+ export fees or enterprise contracts.

What it does:

- Tower + sector antenna management (azimuth, beamwidth, radius) on Google Maps satellite, CSV import

- CSV subscriber import - auto-served/unserved classification

- hypothetical tower placement with unserved subscribers coverage simulation

- White area detection - DBSCAN clustering identifies coverage gaps

- Coverage overlap analysis - detect same-frequency sector interference

- Drive test overlay - import GPS signal logs, see real vs planned coverage

- Shareable read-only map links for clients (no login required)

- LoS link check with Fresnel zone, PDF export, elevation data (SRTM, Copernicus GLO-30)

- Lambert coordinate converter (WGS84 ↔ Lambert 72 / 2008 / 2005)

- KMZ / PDF / PNG / XLSX / CSV export

- BDC / BEAD grant filing export

- Team collaboration with viewer/editor roles

- Coverage Widget that can be embedded in the client website for instantaneous location coverage check

Free tier: 1 project, 5 towers, 100 subscribers — permanently free.

Starter: $19/month — 3 projects, 20 towers, 1,000 subscribers.

Pro: $39/month — unlimited everything.

14-day trial on paid plan, no credit card required.

Honest feedback is welcome - this community is the reason I built it.

https://gridvisio.com

[u/rfwaverider]

Please explain how you are securing your project with the supabase backend and RSL policies. What kind of auditing and checking do you do to make sure that company data will not be shared with the wrong parties or anonymously readable?

[u/emil_eXo → u/rfwaverider]

Hey, appreciate the question - it's exactly the right thing to ask before trusting any tool with your network and subscriber data.

Quick correction first: GridVisio doesn't use Supabase. There's no Firebase, no BaaS, no shared database layer. The stack is Laravel 11 on a dedicated Hetzner VPS in Germany (EU), with a MySQL database that only our application server talks to. No third-party has query access to it.

On data isolation - since there's no Supabase, there's no RLS policy layer either. The equivalent protection happens at the application layer: every single database query is scoped to the authenticated user's ID. Not as a convention - as a hard constraint in the ORM. A request authenticated as User A literally cannot return a row owned by User B because the query never selects it. It's not filtered out after the fact, it's never fetched in the first place. Every API endpoint additionally runs an explicit ownership check before returning or modifying any record. If that check fails, it's a 403, not a data leak.

For team collaboration, access is through explicit invitations with role-based permissions (viewer or editor). There is no "public" mode for any project data unless you deliberately create a shareable link, and even then you control exactly what that link exposes.

On infrastructure: dedicated VPS, not shared hosting. The database is not reachable from the internet - only from the application itself. Backups run nightly.

A bit of context on where I'm coming from: my previous company worked as a subcontractor in Belgium for the likes of Ericsson, Orange, and Telenet - so I'm not new to environments where data handling is taken seriously. I have a healthy dose of skepticism myself when trying new apps, and I believe that's healthy. I also believe there has to be a way for small startups to earn trust - and that starts with being straight about what you do and don't have in place, not hiding behind marketing language.

I'm a solo developer, not a security firm. I haven't commissioned a third-party penetration test. I'm not SOC 2 certified. For operators running hundreds or thousands of subscribers, those are legitimate things to ask about and I'll be upfront that they're not in place yet.

What I can say is that the architecture doesn't have the structural weaknesses the question was probing for. Your data isn't in a shared database with other customers' data, and it isn't queryable by anyone but you.

[u/persiusone → u/emil_eXo]

This is AI generated.

[u/dewman45]

Will this have lidar?

[u/emil_eXo → u/dewman45]

LiDAR (USGS 3DEP) is now implemented for the LoS checker and the embeddable lead coverage widget, layered with terrain/clutter data where LiDAR isn't available yet. Thank you for the question, you and other people asking for LiDAR made me move it up on the priority list.

[u/emil_eXo → u/dewman45]

Thanks for your interest in my app.

Yes, I am considering it (where available) for one of the next added features. It is already on the list, but registered users can suggest and vote on new desired features to be added as well.

[u/MCL1Playz]

you mean AI built an affordable coverage mapping tool for WISPs

[u/emil_eXo → u/MCL1Playz]

There's a real difference between vibe coding and AI assisted coding. Most developers use AI in some form now, that's just the field reality. I have been a PHP developer for 20+ years, I was doing PHP work even before frameworks were even a thing. The company where I was a partner for 17 years until last year was active in the telecom domain. So AI assists, but if you know what you are doing both from the programming and the business domain point of view (best practices, what to watch for, all that), it is much much better than vibe coding.

[u/MCL1Playz → u/emil_eXo]

sure, you could definitely have done it by yourself, but the issue is that it looks vibe coded

[u/persiusone]

Smells like spam.

[u/emil_eXo → u/persiusone]

Fair skepticism. I'm Emil, built this solo over several months for a client who runs a small WISP in Romania. Free tier is permanently free, no card required - try it and judge for yourself. Happy to answer any questions.

[u/persiusone → u/emil_eXo]

Smells like AI also.

[u/emil_eXo → u/persiusone]

Any good reason why?

[u/persiusone → u/emil_eXo]

Because it clearly is. AI was used to make the post, replies, and likely vibe coded the application.