A Saudi e-commerce platform receives its monthly Google Cloud invoice.

SAR 87,000 this month.

Most of that cost comes from route calculations, geocoding requests, map rendering, distance matrix queries, and delivery-driver navigation. As order volume grows, the bill grows with it. The company owns neither the map data nor the routing engine, and the addresses still are not validated against Saudi Arabia's National Address System (WASL). Arabic map rendering remains inconsistent across new developments, while entire areas of NEOM may not yet be represented accurately.

What many Saudi businesses do not realise is that there is now a mature open-source alternative. A self-hosted mapping stack built on OpenStreetMap, Valhalla, PostGIS, and MapLibre can reduce monthly infrastructure costs to approximately SAR 1,200–2,800 regardless of API volume while adding features that Google Maps does not support well in Saudi Arabia.

This guide from LogioLegion explains what that architecture looks like, what it costs, and when replacing Google Maps becomes financially compelling. For broader software architecture guidance, see our custom software development company in Saudi Arabia guide.

What Google Maps Platform actually costs at Saudi operational scale

Most businesses underestimate how aggressively Google Maps Platform pricing scales.

The pricing model appears inexpensive at low volume. However, once a platform reaches tens of thousands of requests per day, mapping infrastructure often becomes one of the largest recurring software expenses.

Google Maps Platform pricing (2026)

Service	Pricing
Maps JavaScript API	$7.00 per 1,000 map loads
Routes API (Basic)	$0.004 per request
Routes API (Advanced)	$0.008 per request
Distance Matrix API	$5.00 per 1,000 elements
Geocoding API	$5.00 per 1,000 requests
Places API (Text Search)	$32.00 per 1,000 requests
Monthly Credit	$200 free usage

For many Saudi delivery and fleet platforms, routing costs become the primary expense.

Scenario 1: 10,000 route requests per day

Metric	Value
Daily requests	10,000
Monthly requests	300,000
Approximate monthly cost	SAR 18,000
Approximate annual cost	SAR 216,000

At this level, Google Maps remains manageable for many startups.

Scenario 2: 50,000 route requests per day

Metric	Value
Daily requests	50,000
Monthly requests	1.5 million
Approximate monthly cost	SAR 90,000
Approximate annual cost	SAR 1,080,000

This is where many Saudi logistics businesses begin evaluating alternatives.

The annual mapping spend now exceeds the cost of several engineering salaries.

Scenario 3: 200,000 route requests per day

Metric	Value
Daily requests	200,000
Monthly requests	6 million
Approximate monthly cost	SAR 360,000
Approximate annual cost	SAR 4,320,000

At this scale, continuing with Google Maps becomes a strategic financial decision rather than a technical one.

A business is effectively renting infrastructure it could potentially own.

Fleet tracking costs grow even faster

Fleet management platforms generate significantly more map activity than delivery platforms.

A fleet operator with 500 vehicles reporting GPS coordinates every 30 seconds generates millions of location updates every month. Combined with driver applications, dispatch dashboards, route calculations, and historical playback, Google Maps costs commonly reach:

• SAR 45,000–70,000 per month
• SAR 540,000–840,000 per year

This is one reason why companies building fleet management software development Saudi Arabia solutions increasingly move toward self-hosted mapping infrastructure.

PropTech and real estate mapping costs

Saudi PropTech platforms face a different problem.

Interactive property maps, neighbourhood search tools, project overlays, and daily active users create high Maps JavaScript API consumption.

Typical monthly spend:

• SAR 20,000–40,000 per month
• SAR 240,000–480,000 per year

The challenge becomes even greater when developers need custom layers for:

• NEOM developments
• ROSHN communities
• Government infrastructure projects
• Smart-city planning zones
• Utility and zoning overlays

Google Maps was not designed for highly customised Saudi development layers.

Address validation costs

Saudi e-commerce businesses frequently underestimate geocoding expenses.

Every delivery address search, checkout address validation, warehouse lookup, and route destination calculation contributes to API usage.

Typical costs:

• SAR 15,000–30,000 per month
• SAR 180,000–360,000 per year

Despite this spend, Google Maps still does not provide complete WASL-native address handling for many Saudi delivery workflows.

The financial case for ownership

The central question is not whether Google Maps works.

It does.

The question is whether paying hundreds of thousands—or millions—of riyals every year for infrastructure you do not control still makes sense once your platform reaches operational scale.

Consider a Saudi delivery platform spending SAR 90,000 monthly on Google Maps.

Category	Google Maps
Monthly Cost	SAR 90,000
Annual Cost	SAR 1,080,000
Five-Year Cost	SAR 5,400,000
Data Ownership	No
Routing Ownership	No
WASL Native Support	Limited
Offline Support	Limited

Many CTOs discover that their mapping bill eventually exceeds the cost of building a dedicated mapping platform.

That realisation is usually what starts the migration conversation.

In the next section, we'll examine the complete open-source mapping stack that replaces Google Maps: OpenStreetMap, Valhalla, MapLibre, PostGIS, WASL integration, and self-hosted tile infrastructure—and compare its operating costs directly against Google's pricing model.

The open-source mapping stack — what replaces Google Maps and what it costs

The common misconception is that replacing Google Maps means replacing a single product.

In reality, Google Maps Platform bundles several independent services together: map data, map rendering, routing, geocoding, search, spatial storage, and analytics. The open-source approach simply replaces each component with a specialised alternative that you control.

The result is often lower operating costs, greater customisation, and significantly better support for Saudi-specific requirements such as WASL integration, Arabic RTL labels, offline operation, and custom geospatial layers.

Component 1: OpenStreetMap (OSM) — the map data layer

OpenStreetMap is the foundation of most modern open-source mapping systems.

Unlike Google Maps, OSM data is community-maintained and available under the Open Database License (ODbL). Businesses can download the entire Saudi Arabia map dataset, host it internally, and customise it as required.

Key advantages include:

• Free map data
• No API call charges
• Full ownership of deployment
• Ability to add proprietary Saudi layers
• Monthly or weekly update cycles

For Saudi Arabia, OSM coverage is strong across:

• Riyadh
• Jeddah
• Dammam
• Khobar
• Madinah
• Makkah

Coverage in NEOM and other Vision 2030 developments continues improving as new infrastructure is mapped.

Unlike Google Maps, OSM also allows organisations to overlay their own geographic intelligence without restrictions.

Examples include:

• WASL address boundaries
• ROSHN developments
• NEOM zones
• Aramco facility perimeters
• Government infrastructure projects
• Internal logistics zones

Component 2: Self-hosted tile server

Google Maps serves map tiles from Google's infrastructure.

The open-source alternative serves vector tiles from infrastructure owned by the business.

A typical Saudi deployment uses:

• OpenMapTiles schema
• AWS S3
• AWS CloudFront CDN
• EC2 tile generation servers

Architecture flow:

OSM Data → OpenMapTiles → Vector Tiles → CloudFront CDN → User Device

Monthly hosting costs typically range from:

Component	Monthly Cost
EC2 tile generation	SAR 300–700
S3 tile storage	SAR 100–300
CloudFront CDN	SAR 400–1,000
Total	SAR 800–2,000

The critical difference is that traffic volume has a far smaller impact on cost compared to Google's per-request pricing model.

Whether a platform serves 100,000 or 1 million map views, infrastructure costs remain relatively predictable.

Arabic RTL rendering done properly

Saudi businesses frequently encounter issues with Arabic map rendering.

Google Maps Arabic support is acceptable in major cities but often inconsistent in:

• Secondary roads
• Industrial zones
• New developments
• Rural areas

A custom tile pipeline solves this problem.

OpenStreetMap already stores Arabic labels using dedicated Arabic language tags.

Example:

• name = King Fahd Road
• name:ar = طريق الملك فهد

During tile generation, Arabic labels can be rendered using:

• Noto Sans Arabic
• ICU text shaping
• Bidirectional text support

The result is Arabic-first map rendering with proper RTL behaviour at every zoom level.

Component 3: Valhalla — the routing engine

Routing is where most Saudi businesses spend the majority of their Google Maps budget.

Valhalla replaces:

• Routes API
• Directions API
• Distance Matrix API

Valhalla is an open-source routing engine originally developed by Mapzen and remains one of the most advanced routing frameworks available.

Supported routing modes:

• Car
• Truck
• Motorcycle
• Pedestrian
• Bicycle

Unlike Google Maps, Valhalla allows businesses to modify routing logic directly.

Saudi-specific routing examples include:

• Heavy vehicle restrictions
• Makkah exclusion zones
• Industrial access rules
• Restricted government areas
• Custom delivery preferences

Infrastructure cost:

Component	Monthly Cost
AWS EC2 instance	SAR 400–800
Storage	SAR 50–150
Monitoring	SAR 50–100
Total	SAR 400–800

Compared with SAR 90,000 monthly Google routing bills, the economics become obvious quickly.

Prayer-time-aware routing

Saudi traffic patterns change dramatically around prayer times.

A standard routing engine treats every hour equally.

A Saudi-aware routing engine does not.

Using the Aladhan API, Valhalla can incorporate:

• Dhuhr congestion patterns
• Asr congestion patterns
• Maghrib congestion patterns
• Friday Jummah congestion zones

Routes passing major mosque corridors can receive temporary scoring penalties during prayer windows.

This enables dispatch systems to make routing decisions based on actual Saudi operational behaviour rather than generic road-network assumptions.

Heat-aware route optimisation

Saudi Arabia's outdoor work restrictions create another routing challenge.

During summer months, outdoor labour restrictions affect:

• Delivery operations
• Construction logistics
• Field service scheduling

Custom routing logic can flag:

• Heat-sensitive stops
• Outdoor walking distances
• High-temperature service windows

This type of operational intelligence simply does not exist within commercial mapping APIs.

Component 4: MapLibre GL JS — the frontend map layer

MapLibre GL JS is the most common replacement for Google Maps on web and mobile applications.

It originated from Mapbox GL JS before the project changed licensing.

Capabilities include:

• Vector tile rendering
• Smooth zooming
• 3D visualisation
• Rotation and tilt
• Custom styling
• Offline support

For Saudi applications, MapLibre provides complete visual control.

Businesses can create:

• Arabic-first maps
• Brand-specific map themes
• Custom POI layers
• Fleet tracking interfaces
• Delivery heatmaps
• Smart-city dashboards

React integration is straightforward through:

• React
• Next.js
• React Native

This makes it particularly attractive for businesses already building software on the React ecosystem.

Component 5: Geocoding with WASL + Nominatim

Geocoding converts addresses into coordinates.

This is one of the areas where Saudi-specific implementations outperform Google Maps significantly.

The recommended architecture is:

WASL API → Primary Lookup

Nominatim → Secondary Lookup

PostGIS Precision Layer → Coordinate Enhancement

WASL first

Saudi deliveries increasingly rely on WASL.

A WASL code identifies a precise location rather than an approximate street address.

Google Maps frequently resolves Saudi addresses to approximate locations.

WASL resolves them to exact buildings.

Benefits include:

• Higher delivery accuracy
• Lower failed delivery rates
• Better route optimisation
• Better customer experience

Many operators report delivery failure reductions of 20–35% after implementing WASL-native workflows.

Nominatim fallback

For international addresses and free-text searches, Nominatim provides:

• Arabic search
• English search
• OpenStreetMap indexing
• Address lookup
• Reverse geocoding

Photon can also be introduced for faster autocomplete performance.

Component 6: PostGIS — the spatial intelligence layer

PostGIS is arguably the most powerful component in the stack.

It transforms PostgreSQL into a geographic database capable of advanced spatial analysis.

Data commonly stored includes:

• Fleet GPS history
• Delivery zones
• Geofences
• Warehouse locations
• WASL records
• NEOM boundaries
• ROSHN developments
• Government zones

Typical queries include:

"Find all vehicles within 500 metres of a restricted area."

"Calculate delivery coverage from Riyadh warehouse."

"Identify customers outside current service areas."

"Locate drivers nearest to a pickup request."

PostGIS enables these calculations directly inside the database without relying on external mapping services.

Monthly cost comparison

The complete open-source stack generally costs:

Component	Monthly Cost
Tile infrastructure	SAR 800–2,000
Valhalla routing	SAR 400–800
PostGIS database	SAR 200–500
Monitoring and backups	SAR 100–300
Total	SAR 1,200–2,800

Compare that to a Saudi platform paying:

Platform Type	Typical Google Maps Cost
Delivery startup	SAR 18,000/month
Mid-size logistics platform	SAR 90,000/month
Large-scale operation	SAR 360,000/month

Even at modest scale, the cost difference becomes substantial.

Break-even calculation

Assume a Saudi logistics platform currently spends:

• SAR 40,000/month on Google Maps
• SAR 480,000/year

Custom mapping platform build:

• SAR 220,000–380,000

Infrastructure:

• SAR 2,000/month

Annual operating cost after launch:

• SAR 24,000

Annual saving:

• Approximately SAR 456,000

For most organisations, the investment pays for itself within the first year.

The larger the platform becomes, the stronger the financial argument for ownership over subscription-based mapping infrastructure.

The open-source mapping stack — what replaces Google Maps and what it costs

The common misconception is that replacing Google Maps means replacing a single product.

In reality, Google Maps Platform bundles several independent services together: map data, map rendering, routing, geocoding, search, spatial storage, and analytics. The open-source approach simply replaces each component with a specialised alternative that you control.

The result is often lower operating costs, greater customisation, and significantly better support for Saudi-specific requirements such as WASL integration, Arabic RTL labels, offline operation, and custom geospatial layers.

Component 1: OpenStreetMap (OSM) — the map data layer

OpenStreetMap is the foundation of most modern open-source mapping systems.

Unlike Google Maps, OSM data is community-maintained and available under the Open Database License (ODbL). Businesses can download the entire Saudi Arabia map dataset, host it internally, and customise it as required.

Key advantages include:

• Free map data
• No API call charges
• Full ownership of deployment
• Ability to add proprietary Saudi layers
• Monthly or weekly update cycles

For Saudi Arabia, OSM coverage is strong across:

• Riyadh
• Jeddah
• Dammam
• Khobar
• Madinah
• Makkah

Coverage in NEOM and other Vision 2030 developments continues improving as new infrastructure is mapped.

Unlike Google Maps, OSM also allows organisations to overlay their own geographic intelligence without restrictions.

Examples include:

• WASL address boundaries
• ROSHN developments
• NEOM zones
• Aramco facility perimeters
• Government infrastructure projects
• Internal logistics zones

Component 2: Self-hosted tile server

Google Maps serves map tiles from Google's infrastructure.

The open-source alternative serves vector tiles from infrastructure owned by the business.

A typical Saudi deployment uses:

• OpenMapTiles schema
• AWS S3
• AWS CloudFront CDN
• EC2 tile generation servers

Architecture flow:

OSM Data → OpenMapTiles → Vector Tiles → CloudFront CDN → User Device

Monthly hosting costs typically range from:

Component	Monthly Cost
EC2 tile generation	SAR 300–700
S3 tile storage	SAR 100–300
CloudFront CDN	SAR 400–1,000
Total	SAR 800–2,000

The critical difference is that traffic volume has a far smaller impact on cost compared to Google's per-request pricing model.

Whether a platform serves 100,000 or 1 million map views, infrastructure costs remain relatively predictable.

Arabic RTL rendering done properly

Saudi businesses frequently encounter issues with Arabic map rendering.

Google Maps Arabic support is acceptable in major cities but often inconsistent in:

• Secondary roads
• Industrial zones
• New developments
• Rural areas

A custom tile pipeline solves this problem.

OpenStreetMap already stores Arabic labels using dedicated Arabic language tags.

Example:

• name = King Fahd Road
• name:ar = طريق الملك فهد

During tile generation, Arabic labels can be rendered using:

• Noto Sans Arabic
• ICU text shaping
• Bidirectional text support

The result is Arabic-first map rendering with proper RTL behaviour at every zoom level.

Component 3: Valhalla — the routing engine

Routing is where most Saudi businesses spend the majority of their Google Maps budget.

Valhalla replaces:

• Routes API
• Directions API
• Distance Matrix API

Valhalla is an open-source routing engine originally developed by Mapzen and remains one of the most advanced routing frameworks available.

Supported routing modes:

• Car
• Truck
• Motorcycle
• Pedestrian
• Bicycle

Unlike Google Maps, Valhalla allows businesses to modify routing logic directly.

Saudi-specific routing examples include:

• Heavy vehicle restrictions
• Makkah exclusion zones
• Industrial access rules
• Restricted government areas
• Custom delivery preferences

Infrastructure cost:

Component	Monthly Cost
AWS EC2 instance	SAR 400–800
Storage	SAR 50–150
Monitoring	SAR 50–100
Total	SAR 400–800

Compared with SAR 90,000 monthly Google routing bills, the economics become obvious quickly.

Prayer-time-aware routing

Saudi traffic patterns change dramatically around prayer times.

A standard routing engine treats every hour equally.

A Saudi-aware routing engine does not.

Using the Aladhan API, Valhalla can incorporate:

• Dhuhr congestion patterns
• Asr congestion patterns
• Maghrib congestion patterns
• Friday Jummah congestion zones

Routes passing major mosque corridors can receive temporary scoring penalties during prayer windows.

This enables dispatch systems to make routing decisions based on actual Saudi operational behaviour rather than generic road-network assumptions.

Heat-aware route optimisation

Saudi Arabia's outdoor work restrictions create another routing challenge.

During summer months, outdoor labour restrictions affect:

• Delivery operations
• Construction logistics
• Field service scheduling

Custom routing logic can flag:

• Heat-sensitive stops
• Outdoor walking distances
• High-temperature service windows

This type of operational intelligence simply does not exist within commercial mapping APIs.

Component 4: MapLibre GL JS — the frontend map layer

MapLibre GL JS is the most common replacement for Google Maps on web and mobile applications.

It originated from Mapbox GL JS before the project changed licensing.

Capabilities include:

• Vector tile rendering
• Smooth zooming
• 3D visualisation
• Rotation and tilt
• Custom styling
• Offline support

For Saudi applications, MapLibre provides complete visual control.

Businesses can create:

• Arabic-first maps
• Brand-specific map themes
• Custom POI layers
• Fleet tracking interfaces
• Delivery heatmaps
• Smart-city dashboards

React integration is straightforward through:

• React
• Next.js
• React Native

This makes it particularly attractive for businesses already building software on the React ecosystem.

Component 5: Geocoding with WASL + Nominatim

Geocoding converts addresses into coordinates.

This is one of the areas where Saudi-specific implementations outperform Google Maps significantly.

The recommended architecture is:

WASL API → Primary Lookup

Nominatim → Secondary Lookup

PostGIS Precision Layer → Coordinate Enhancement

WASL first

Saudi deliveries increasingly rely on WASL.

A WASL code identifies a precise location rather than an approximate street address.

Google Maps frequently resolves Saudi addresses to approximate locations.

WASL resolves them to exact buildings.

Benefits include:

• Higher delivery accuracy
• Lower failed delivery rates
• Better route optimisation
• Better customer experience

Many operators report delivery failure reductions of 20–35% after implementing WASL-native workflows.

Nominatim fallback

For international addresses and free-text searches, Nominatim provides:

• Arabic search
• English search
• OpenStreetMap indexing
• Address lookup
• Reverse geocoding

Photon can also be introduced for faster autocomplete performance.

Component 6: PostGIS — the spatial intelligence layer

PostGIS is arguably the most powerful component in the stack.

It transforms PostgreSQL into a geographic database capable of advanced spatial analysis.

Data commonly stored includes:

• Fleet GPS history
• Delivery zones
• Geofences
• Warehouse locations
• WASL records
• NEOM boundaries
• ROSHN developments
• Government zones

Typical queries include:

"Find all vehicles within 500 metres of a restricted area."

"Calculate delivery coverage from Riyadh warehouse."

"Identify customers outside current service areas."

"Locate drivers nearest to a pickup request."

PostGIS enables these calculations directly inside the database without relying on external mapping services.

Monthly cost comparison

The complete open-source stack generally costs:

Component	Monthly Cost
Tile infrastructure	SAR 800–2,000
Valhalla routing	SAR 400–800
PostGIS database	SAR 200–500
Monitoring and backups	SAR 100–300
Total	SAR 1,200–2,800

Compare that to a Saudi platform paying:

Platform Type	Typical Google Maps Cost
Delivery startup	SAR 18,000/month
Mid-size logistics platform	SAR 90,000/month
Large-scale operation	SAR 360,000/month

Even at modest scale, the cost difference becomes substantial.

Break-even calculation

Assume a Saudi logistics platform currently spends:

• SAR 40,000/month on Google Maps
• SAR 480,000/year

Custom mapping platform build:

• SAR 220,000–380,000

Infrastructure:

• SAR 2,000/month

Annual operating cost after launch:

• SAR 24,000

Annual saving:

• Approximately SAR 456,000

For most organisations, the investment pays for itself within the first year.

The larger the platform becomes, the stronger the financial argument for ownership over subscription-based mapping infrastructure.

The four highest-value Saudi use cases

Fleet management platforms

Fleet operators are usually the first businesses to hit the limits of Google Maps Platform pricing.

A fleet of 500 vehicles transmitting GPS updates every 30 seconds can generate hundreds of thousands of mapping events every day. Combined with route calculations, geofencing checks, and driver map rendering, monthly Google Maps costs can easily reach SAR 45,000–70,000.

A custom mapping stack replaces variable API costs with fixed infrastructure costs.

The biggest advantage is not cost alone. Fleet operators gain complete control over routing logic.

Saudi-specific routing rules can be implemented directly inside Valhalla:

• Heavy vehicle bridge restrictions
• Truck exclusion zones in Makkah
• Aramco facility access boundaries
• Driver route compliance monitoring
• Prayer-time congestion avoidance
• Outdoor work ban route warnings

The result is a mapping platform designed around operational reality rather than generic consumer navigation.

For organisations building fleet products, our guide to fleet management software development Saudi Arabia explores the broader architecture in detail.

Last-mile delivery and logistics

Delivery platforms often experience the fastest return on investment when migrating away from Google Maps.

A platform processing 50,000 route calculations per day can spend approximately SAR 90,000 monthly on mapping APIs.

Most of that expenditure comes from:

• Route calculations
• Distance matrix queries
• Address geocoding
• Driver map rendering

A Saudi-specific mapping stack significantly improves address accuracy because it uses WASL as the primary source of truth.

Instead of approximating addresses through conventional geocoding, delivery drivers receive exact Saudi National Address coordinates.

Benefits include:

• Fewer failed deliveries
• Reduced driver call volume
• Lower fuel consumption
• Better ETA accuracy
• Higher first-attempt delivery success

Offline mapping also becomes important for industrial zones, construction projects, and remote logistics corridors where cellular coverage is inconsistent.

MapLibre mobile applications can preload operational regions before dispatch begins.

Drivers continue navigating even when connectivity drops.

For logistics-focused platforms, our guide to logistics app development Saudi Arabia — Aramex API explains how mapping integrates with broader logistics operations.

PropTech and real estate platforms

Saudi real estate platforms increasingly require map layers that simply do not exist inside Google Maps.

Examples include:

• NEOM development zones
• ROSHN communities
• REGA-aligned property regions
• Planned infrastructure corridors
• Mixed-use development boundaries
• Construction phase overlays

Google Maps generally focuses on public road networks and mainstream consumer destinations.

Real estate platforms often require significantly more granular information.

With PostGIS and MapLibre, developers can create custom spatial layers that display:

• Parcel boundaries
• Property ownership zones
• Utility corridors
• School catchments
• Future infrastructure plans
• Community master plans

Because the underlying stack is self-hosted, new layers can be deployed immediately without waiting for Google to update its datasets.

This becomes particularly important in rapidly developing regions where infrastructure changes monthly.

Smart city and government platforms

Saudi Vision 2030 initiatives are generating entirely new mapping requirements.

Government platforms frequently need to combine dozens of datasets into a single operational view.

Examples include:

• Riyadh Metro infrastructure
• Port authority zones
• Industrial cities
• Public utility corridors
• Smart city sensor networks
• Environmental monitoring systems
• Emergency response regions

A self-hosted mapping platform provides complete control over data ownership and security.

Sensitive infrastructure layers remain inside the organisation's cloud environment rather than being transmitted through third-party mapping APIs.

Custom government deployments often include:

• Role-based map visibility
• Classified infrastructure layers
• Internal geospatial analytics
• High-frequency sensor integration
• Real-time incident monitoring
• Secure spatial reporting dashboards

For public-sector organisations, data ownership often becomes as important as cost reduction.

How LogioLegion builds the migration — 5-phase implementation

Migrating away from Google Maps does not require rebuilding an entire platform from scratch.

The transition is typically performed through a structured five-phase process.

Phase 1 — Infrastructure setup (3–4 weeks)

The foundation layer includes:

• AWS EC2 deployment
• OpenStreetMap ingestion
• PostGIS configuration
• Tile storage architecture
• CDN configuration
• WASL data preparation

Saudi geographic data is loaded into the spatial database and indexed for routing and search.

Phase 2 — Tile generation (2–3 weeks)

OpenMapTiles generates vector tiles from OpenStreetMap data.

During this stage we configure:

• Arabic label rendering
• RTL text shaping
• Custom Saudi map styling
• WASL overlays
• NEOM layers
• ROSHN overlays

Tiles are then distributed through CloudFront for low-latency delivery.

Phase 3 — Routing engine deployment (2–3 weeks)

Valhalla is configured with Saudi-specific routing profiles.

Examples include:

• Delivery vehicles
• Heavy trucks
• Passenger vehicles
• Motorcycles
• Pedestrian navigation

Prayer-time penalties and operational restrictions are introduced during this phase.

Phase 4 — Frontend integration (3–4 weeks)

Application interfaces are connected to the new mapping stack.

Deliverables include:

• Next.js map components
• React mapping libraries
• React Native offline maps
• WASL search tools
• Geocoding interfaces
• Route visualisation tools

This stage replaces Google Maps rendering inside web and mobile applications.

Phase 5 — Testing and migration (2–3 weeks)

This is the most important phase.

An API compatibility layer is introduced that accepts Google Maps-style requests and translates them into calls against the new infrastructure.

Benefits include:

• Minimal application code changes
• Faster migration timelines
• Lower engineering risk
• Easier rollback testing
• Side-by-side accuracy comparison

A/B testing then compares:

• Route quality
• Geocoding accuracy
• Search relevance
• Rendering performance
• Infrastructure cost

Only after validation is complete does traffic fully transition away from Google Maps.

What does custom mapping software cost in Saudi Arabia?

The cost of building a custom mapping platform depends primarily on three variables:

1. Daily request volume
2. Saudi-specific requirements
3. Infrastructure availability and redundancy requirements

For most Saudi businesses, the objective is not simply replacing Google Maps.

The objective is replacing Google Maps while gaining:

• WASL integration
• Arabic RTL rendering
• Offline capability
• Saudi-specific routing
• Ownership of map infrastructure
• Predictable operating costs

Basic custom mapping stack

Suitable for:

• Early-stage logistics companies
• Fleet startups
• Delivery platforms
• Internal operational tools

Includes:

• OpenStreetMap deployment
• Tile server infrastructure
• Valhalla routing engine
• Geocoding services
• PostGIS setup
• Basic React integration

Scope	Cost
Development	SAR 120,000–200,000
Timeline	10–16 weeks
Monthly infrastructure	SAR 1,200–2,000

Capacity:

• Up to 100,000 requests/day

This tier typically replaces Google Maps for companies experiencing their first meaningful API costs.

Full Saudi mapping platform

Suitable for:

• Regional logistics operators
• Enterprise fleet management platforms
• Delivery marketplaces
• PropTech products

Includes:

• Everything in Basic
• WASL integration
• Offline map packages
• Arabic RTL optimisation
• NEOM custom layers
• ROSHN layers
• Prayer-time routing
• React Native SDKs
• Custom Saudi map styling

Scope	Cost
Development	SAR 220,000–380,000
Timeline	16–22 weeks
Monthly infrastructure	SAR 1,800–3,200

Capacity:

• Hundreds of thousands of daily requests

This is the most common implementation for Saudi organisations migrating from Google Maps.

Enterprise mapping infrastructure

Suitable for:

• National logistics providers
• Government projects
• Smart city platforms
• High-volume marketplaces

Includes:

• Multi-region deployment
• High availability architecture
• AI route intelligence
• Custom data pipelines
• Advanced analytics
• Dedicated operational dashboards
• Disaster recovery environment
• Large-scale geospatial processing

Scope	Cost
Development	SAR 400,000–700,000
Timeline	22–32 weeks
Monthly infrastructure	SAR 3,000–6,000

Capacity:

• More than 1 million requests/day

At this scale, Google Maps costs often exceed infrastructure costs by a significant margin.

The break-even calculation

Consider a Saudi platform currently spending:

Metric	Amount
Google Maps cost	SAR 40,000/month
Annual spend	SAR 480,000/year

Custom platform:

Metric	Amount
Build cost	SAR 220,000–380,000
Infrastructure	SAR 2,000/month
Annual infrastructure	SAR 24,000

Annual savings after migration:

Metric	Amount
Previous annual cost	SAR 480,000
New annual cost	SAR 24,000
Annual saving	SAR 456,000

For most organisations, break-even occurs within 4–8 months.

After that point, savings continue accumulating every year while the business retains full ownership of its mapping infrastructure.

AI-powered route intelligence

Once the mapping stack is owned and controlled internally, organisations gain access to optimisation opportunities that are difficult to achieve using commercial mapping APIs.

Examples include:

• Demand forecasting
• Driver allocation prediction
• Dynamic route scoring
• Delivery clustering
• Traffic pattern learning
• Dispatch optimisation

These capabilities increasingly rely on AI systems that analyse historical fleet and delivery data.

The underlying AI architecture is similar to the systems covered in our guide to the best agentic AI models in 2026.

Instead of merely displaying maps, the platform begins making operational recommendations.

Why LogioLegion for custom mapping development in Saudi Arabia

LogioLegion builds Saudi-focused software systems where mapping is part of the operational backbone rather than a visual component.

Our team develops custom platforms using React, Next.js, Node.js, Laravel, React Native, PostGIS, and AWS Middle East infrastructure. We design mapping systems around Saudi requirements including WASL address integration, Arabic-first interfaces, offline field operations, fleet routing, logistics workflows, and Vision 2030 development zones.

Unlike generic mapping deployments, our implementations incorporate Saudi-specific routing intelligence, geospatial compliance requirements, and PDPL-conscious cloud architecture. We also provide fixed-scope project pricing, full source-code ownership, and complete IP assignment at project completion.

Conclusion

Every month a Saudi platform pays Google Maps Platform fees is a month paying for maps that do not know what WASL is, cannot render Arabic street names consistently, and have never heard of the outdoor work ban or Friday Jummah routing.

The open-source alternative is mature, fast, and costs a fraction of the price. More importantly, it gives businesses ownership of their mapping infrastructure, routing logic, and geographic intelligence instead of renting access to it indefinitely.

Building on Google Maps in Saudi Arabia? Book a free discovery call with LogioLegion — we scope the full migration architecture and deliver a fixed-price proposal within 5 business days.

---