> ## Documentation Index
> Fetch the complete documentation index at: https://docs.nikaplanet.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Developer Platform

> Build frontend geospatial experiences with OnlyMap JS and package, run, and host reproducible processing workers with NIKA GeoEngine.

## Build the NIKA geospatial stack

NIKA's Developer Platform has two complementary tools. **OnlyMap JS** is the frontend layer for building interactive WebGL maps in the browser. **NIKA GeoEngine** is the backend worker platform for packaging, testing, running, and hosting geoprocessing code with reproducible environments.

> [card] [OnlyMap JS — frontend map applications](https://docs.nikaplanet.com/onlymap/overview.md)
>
> Build interactive maps with HTML custom elements and WebGL. Declare layers, widgets, popups, interactions, and stories without setting up deck.gl directly or maintaining a bespoke map UI framework.

> [card] [NIKA GeoEngine — backend processing workers](https://docs.nikaplanet.com/nika-geoengine/overview.md)
>
> Package Python or R geoprocessing workloads in isolated containers, test them locally, version them, and make them available in the cloud and through QGIS or ArcGIS Pro.

## Choose where to start

**1. Build an interactive map**

Start with [OnlyMap JS](https://docs.nikaplanet.com/onlymap/overview.md) when your goal is a browser-based map application, a visualisation, or an embeddable map experience.

**2. Package a geoprocessing workflow**

Start with [NIKA GeoEngine](https://docs.nikaplanet.com/nika-geoengine/overview.md), then follow [Installation & Setup](https://docs.nikaplanet.com/guides/custom-geoprocess-deployment/installation.md) and [Your First Worker](https://docs.nikaplanet.com/guides/custom-geoprocess-deployment/step-by-step.md).

**3. Connect processing to GIS users**

After publishing a worker, use the [QGIS](https://docs.nikaplanet.com/nika-geoengine/qgis.md) or [ArcGIS Pro](https://docs.nikaplanet.com/nika-geoengine/arcgis.md) integration so GIS users can run it without managing the local runtime themselves.

## Frontend and backend, clearly separated

OnlyMap JS owns the map interface: it renders data, responds to user interaction, and presents a geospatial experience in the browser. GeoEngine owns processing: it gives each worker its declared dependencies, compute environment, version history, tests, and deployment path.

Use either independently. Use both when an application needs a rich map interface alongside repeatable, compute-intensive geoprocessing.


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.