Skip to Content
🚧 This page is still under construction 🚧
v1.0 — 1M+ qps/read benchmark →

Geospatial search,built for speed.

Find the nearest location across millions of points in sub-millisecond time. Deploy a worker anywhere, query via REST, gRPC, or UNIX socket.

No credit card
POST /v1/query
live
{
"lat": 52.5200,
"lng": 13.4050,
"radius_km": 5
}
Results0
Latency0.42ms

Built for production geospatial workloads

< 1msavg query latency
REST · gRPC · UNIXquery interfaces
On-premisesself-hosted worker
Open SourceRust-powered core
Any hardwarePi → production

Why Orter

Stop fighting your geospatial stack.

Most geospatial setups are slow, bloated, or locked into a single cloud. Orter fixes all three.

The old way

Postgres + PostGIS tuning nightmares
Managed services that lock you in
Hundreds of ms per radius query at scale
Sending location data to a third party
Complex setup, weeks to production

The Orter way

One Docker command to deploy a worker
Run anywhere — your VPC, on-prem, or a Pi
Sub-millisecond queries by default
Your data never leaves your network
Production-ready in under 3 minutes

How it works

Up and running in minutes.

No infrastructure expertise required. Three steps from zero to sub-millisecond geospatial queries.

01

Upload your data

Add location datasets to Orter collections via the web dashboard or API. Any format, no schema changes needed.

02

Deploy a worker

Run a single Docker container anywhere — your server, a cloud VM, or even a Raspberry Pi. One command, zero config.

03

Query at speed

Call via REST, gRPC, or UNIX socket. Find the nearest location in under a millisecond, at any scale.

Capabilities

Everything you need, nothing you don’t.

Manage your data

Modern, easy-to-use management interface. Handle collections, worker nodes, and user access from one place.

Lightning fast performance

State-of-the-art tech stack and efficient lookup algorithm. Unprecedented latency and throughput.

Rust Language
Tokio

Modern tech stack

Built in Rust on a state-of-the-art tech stack. Blazingly fast while sipping minimal resources.

Developer experience

Drop into your stack.
no glue code.

Native SDKs for TypeScript, Python, and Rust. Raw HTTP and gRPC when you need it. UNIX socket for zero-latency local calls.

  • Typed responses with full IntelliSense
  • Built-in retries, timeouts, and connection pooling
  • OpenAPI spec and Protobuf definitions on GitHub
curl -X POST https://worker.orter.dev/v1/query \
  -H "Authorization: Bearer $ORTER_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{
    "lat": 52.5200,
    "lng": 13.4050,
    "radius_km": 5,
    "limit": 100
  }'

See it in action

From docker pull to first query in 60 seconds.

orter-worker — bash

Welcome to the React Terminal UI Demo!

Orter web dashboard shown on a laptop screen, with collection and worker management views

Manage from anywhere


Manage collections, worker nodes, and API access from a modern web dashboard — no CLI required.

Use cases

Built for whatever you're shipping.

Store locators

Find the nearest branch, warehouse, or pickup point in sub-millisecond time across millions of locations.

Logistics & dispatch

Route drivers, match orders to depots, and balance fleet load with live geospatial queries.

Mobile & on-device

Run the worker on edge devices or even a Raspberry Pi. Offline-capable geospatial lookups.

Real estate & property

Search listings, points of interest, and amenities within a radius — instantly, at any scale.

IoT & telemetry

Match incoming sensor pings to zones, geofences, or assets in real time.

Location-aware apps

Power discovery, recommendations, and personalization based on user location.

Focus on what matters


You provide location data. We handle storage, orchestration, and routing. No infrastructure expertise required.

Your data stays yours

Workers run on your own hardware. Location data never leaves your infrastructure.

Any interface, any language

REST, gRPC, and UNIX socket — use whichever fits your stack. SDKs and raw HTTP both work.

Scales with your load

Add more worker nodes as traffic grows. The Orter control plane routes queries automatically.

Diagram of Orter API interfaces: REST, gRPC, and UNIX socket query endpoints

Talk with Orter how you want


REST, gRPC, or local UNIX socket. Pick whatever fits your stack.

Create account, deploy worker, run first query — under three minutes.

Loved by developers

Don’t take our word for it.

Orter changed my life

With the help of Orter, I could locate the meaning of life in under one millisecond. Thank you Orter 🙏.

H
Helmut
I hate Orter

I found my wife cheating with the help of Orter. My life is destroyed now. Thanks Orter. But it was fast though. 2 stars.

R
Richard
Orter is the best

Orter made me rich. Best product ever.

CO
Creators of Orter
I only have a Raspberry Pi

Orter lets me make blazingly fast geospatial searches from my Raspberry Pi. I love it.

SW
Someone without any money

FAQ

Questions, answered.

Median radius queries against a 10M-point dataset return in 0.3–0.7ms on commodity hardware. See the benchmark page for full numbers, methodology, and source code.

On your worker, on your hardware. The Orter control plane only stores collection metadata and routing info — your raw geospatial data never leaves your network.

REST (HTTP+JSON), gRPC (Protobuf), and a local UNIX socket. Pick whichever fits your stack. SDKs for TypeScript, Python, and Rust are also available.

Yes. The worker is a single Docker image. It can run fully offline once provisioned. The control plane is optional for advanced features.

The Rust-powered worker core is open source. The control plane and dashboard are proprietary, free up to the generous free-tier limits.

Free forever for small workloads. Paid tiers scale by queries-per-second and number of worker nodes. No per-record fees, no surprise bills.

Get started

Start searching in minutes.

One Docker command. Any hardware. Sub-millisecond queries at any scale.

No credit card · Free forever