Hosted and embed
Configure a hosted link or classic cross-origin embed with deliberate activation and exact origins.
Read the guideDevelopers
One service. Your interface.
Choose the amount of Overa interface you need. The same managed service keeps decisions, permissions and provider limits consistent.
Components and headless
Supported Overa components, delivered package exports, lifecycle and plain Node headless use.
Read the guideManaged HTTP API
Versioned API operations, confidential backend authentication, canonical decisions, errors and quotas.
Read the guideProperty sources
Registered property snapshots, source status, lifecycle, completeness and supported territory.
Read the guideStart with an issued integration
Your setup specifies the service origin, integration ID, source, territory, supported capabilities and limits. Do not treat a public origin check as confidential authentication. Backend keys stay on your server; a browser uses its own short-lived visitor capability.
Distribution is managed
The classic embed is served by the configured Overa service. Components are supported package exports delivered through an agreed artifact or source arrangement. There is no public registry installation or universal standalone Map and Results SDK.
Ordinary documentation pages do not create a map, calculate a journey or sign you in. Evaluation access is separately configured and deliberately activated.
Plan your integration