6.2mediumCONDITIONAL GO

WASM Geo-Viz SDK

A Rust/WASM library for rendering tens of thousands of moving entities on interactive 3D maps in the browser.

DevToolsDevelopers and companies building fleet management, logistics, drone monitori...
The Gap

Developers building logistics dashboards, fleet trackers, or IoT monitoring tools struggle with browser performance when rendering thousands of real-time moving objects on maps—JS-based solutions choke.

Solution

A drop-in SDK (Rust compiled to WASM) that handles high-performance 3D globe and 2D map rendering with smooth zoom, entity scaling, and projection correctness out of the box. Developers get a simple JS API backed by near-native performance.

Revenue Model

freemium — open-source core with free tier for <1K entities; paid tiers ($99-499/mo) for higher entity counts, clustering, heatmaps, analytics overlays, and commercial licensing.

Feasibility Scores
Pain Intensity7/10

The pain is real and well-documented—the HN comments on flight-viz.com directly demonstrate it. But it affects a narrow audience (developers building high-entity dashboards), and many teams work around it by using deck.gl or moving rendering server-side. It's a genuine pain for the teams who hit it, but most mapping users never need 10K+ moving entities.

Market Size5/10

TAM is limited. The addressable market is developers at companies building fleet/logistics/IoT/defense dashboards who need 10K+ real-time entities in-browser AND find existing tools insufficient. That's maybe a few thousand companies globally. At $99-499/mo, ceiling is likely $5-20M ARR. It's a solid niche but not a huge market—closer to a great indie business than a VC-scale opportunity.

Willingness to Pay6/10

Companies in fleet/logistics/defense have budgets and pay for tools (Mapbox, Cesium Ion, HERE). But developers strongly prefer open-source mapping libs (deck.gl, MapLibre are free). The entity-count paywall is clever but gameable—developers will batch/cluster client-side. Defense/enterprise will pay; startups and hobbyists will stick to free tier or deck.gl. You're selling performance, which is a harder sell than features.

Technical Feasibility6/10

A solo dev CAN build the core WASM renderer in 4-8 weeks—the flight-viz.com demo proves the concept works. But an SDK is far more than a demo. You need: tile loading, multiple projections, smooth zoom/pan, label collision, clustering, icon atlases, touch/mouse interaction, a clean JS API, documentation, cross-browser testing (WebGPU/WebGL fallback), npm packaging. Getting to 'drop-in SDK' quality is more like 4-6 months of focused work for a skilled Rust/graphics dev.

Competition Gap6/10

deck.gl is the 800-pound gorilla and it's free. It handles 100K+ entities with GPU instancing. The gap you're exploiting is: (1) WASM/Rust vs JS performance ceiling, (2) true 3D globe (deck.gl is 2.5D), (3) simpler API for the specific moving-entity use case. Gap #1 matters but deck.gl is 'good enough' for most. Gap #2 is real but CesiumJS covers it (poorly). Gap #3 is the strongest angle—a focused, opinionated SDK vs. deck.gl's general-purpose layer system. But you're competing with free.

Recurring Potential7/10

Entity-count tiers map naturally to subscription pricing and scale with customer growth (more vehicles = more entities = higher tier). Commercial licensing for defense/enterprise is sticky recurring revenue. But the open-source core creates pressure—if the free tier is too generous, paid conversion suffers. If too stingy, adoption suffers. The 1K entity free limit is reasonable but may need tuning.

Strengths
  • +Proven technical differentiation—the flight-viz.com demo already demonstrates the WASM performance advantage with real traction (86 upvotes, engaged comments)
  • +Clear pain point validated by user feedback: zoom behavior, projection bugs, entity scaling, and performance ceilings are real problems developers complain about
  • +Defense/logistics verticals have real budgets and value performance—these aren't price-sensitive hobbyists
  • +Rust/WASM is a defensible moat—few developers can build this, and the ecosystem is 2-3 years from catching up with mature alternatives
  • +The 'drop-in SDK' positioning is strong—deck.gl requires assembling multiple layers/plugins, CesiumJS is bloated, Mapbox chokes at scale
Risks
  • !deck.gl is free, battle-tested, and 'good enough' for 90% of fleet-tracking use cases—you're fighting for the remaining 10% who need extreme performance
  • !Maintaining a mapping SDK is a long-tail commitment: tile formats evolve, browsers change WebGPU APIs, projections have edge cases, every basemap provider has quirks—this is not a 'ship and forget' product
  • !The Rust/WASM mapping ecosystem is maturing fast (MapLibre RS, Galileo)—in 2-3 years, free alternatives may close your performance gap
  • !Selling performance to developers is hard—they'll benchmark, find deck.gl at 60fps for their 5K entities, and not pay for your 120fps
  • !Defense/government sales cycles are 6-18 months with procurement hurdles—can't rely on this vertical for early revenue
Competition
deck.gl

Open-source WebGL2/WebGPU layer-based visualization framework

Pricing: Free (MIT open-source
Gap: No true 3D globe—only 2.5D extrusions. No built-in basemap (bring your own MapLibre/Mapbox). No built-in position interpolation or tween engine for smooth entity movement. Steep learning curve. WebGPU path still experimental. Not compiled to WASM—still JS/WebGL overhead ceiling.
CesiumJS

True 3D virtual globe engine with terrain, 3D Tiles, CZML temporal animation, and sensor rendering. The standard for aerospace/defense geospatial visualization.

Pricing: CesiumJS library is free (Apache 2.0
Gap: Performance collapses past ~10-20K entities due to heavy object-per-entity overhead. Older WebGL1 renderer. 3-4MB bundle size. Dated UI/DX. 2D mode is an afterthought. Verbose, older API patterns. No WASM performance path.
Mapbox GL JS

Full-featured proprietary map rendering SDK with vector tiles, 3D terrain, globe projection, and a rich styling system. Best-in-class map aesthetics.

Pricing: Free: 50K map loads/mo. Pay-as-you-go: ~$5 per 1K map loads. Enterprise negotiable. v3+ is proprietary (not open-source
Gap: GeoJSON source updates trigger full re-serialization—performance degrades past ~5K frequently-moving points. Most fleet-tracking teams layer deck.gl on top because native entity rendering can't handle scale. Proprietary lock-in. Costs escalate at scale. No built-in animation/interpolation for moving entities.
Google Maps JavaScript API

The ubiquitous web map with vector rendering, WebGL overlay view, and deep integration with Google's geocoding/directions/places APIs.

Pricing: $200/mo free credit (~28.5K map loads
Gap: Terrible for high-entity-count rendering—DOM-based markers collapse past 2-3K entities. No GPU-instanced rendering. WebGLOverlayView is raw Three.js with no abstraction. Heaviest vendor lock-in. No temporal animation. Compounding costs. Fundamentally wrong tool for fleet-scale viz.
Kepler.gl

High-level geospatial analytics UI built on deck.gl. Drag-and-drop interface for exploring large datasets with time-series animation, filters, and layer controls.

Pricing: Free (MIT open-source
Gap: Not designed for real-time data—loads static datasets upfront, no live ingestion. Hard to embed/customize (opinionated Redux store). No programmatic high-frequency entity updates. Limited 3D. An analytics tool, not a real-time rendering SDK.
MVP Suggestion

Ship a focused npm package: @wasm-geoviz/core. MVP scope: (1) 2D map + 3D globe toggle with smooth transitions, (2) entity layer accepting {id, lat, lng, heading, icon} arrays with 60fps updates for 50K+ entities, (3) built-in smooth position interpolation between updates, (4) MapLibre basemap integration, (5) 3 entity types (circle, icon, model). Skip clustering, heatmaps, and analytics overlays for v1. The demo that sells this: a live ADS-B feed rendering all global flights in the browser, side-by-side FPS comparison with deck.gl and CesiumJS. The flight-viz.com demo is already 80% of this—productize it.

Monetization Path

Free open-source core (<1K entities, watermark) → Dev tier $99/mo (10K entities, no watermark) → Team tier $249/mo (50K entities, clustering, heatmaps) → Enterprise $499+/mo (unlimited, commercial license, priority support, SLA) → Scale via per-seat or per-deployment licensing for defense/gov contracts. Early revenue: offer paid 'integration consulting' ($5-10K) to help first enterprise customers embed the SDK. This funds development while building case studies.

Time to Revenue

3-4 months to MVP with npm package and docs. First paying customer likely at month 5-6 via direct outreach to fleet/logistics companies who have already hit deck.gl performance walls. Meaningful recurring revenue ($5K+ MRR) likely at month 8-12, assuming you land 2-3 enterprise customers through the consulting-to-license path.

What people are saying
  • 10,000+ aircraft rendered entirely in the browser using Rust compiled to WebAssembly (demonstrates the technical gap JS tools leave)
  • all the flights in the world can be represented in a <500KB api call (surprise at data efficiency suggests existing tools are bloated)
  • planes should probably scale up a bit as you zoom—they become impossible to spot (common unsolved UX problem in geo-viz)
  • zooming on a mouse wheel on windows is nearly unusable (existing map libs have poor zoom/interaction defaults at scale)
  • when you pan around after zooming the planes shift their location (projection bugs plague custom map renderers)