Interactive product preview

From product choice to production evidence—in one governed path.

Explore a synthetic OEM developer project where rights bind program and environment, credentials inherit only effective scope, traces are redacted before storage, conformance is versioned and promotion fails closed until every mandatory gate is satisfied.

M
Mappls AutoDeveloper Cloud · reference
Organization / Program / ProjectAurora Mobility · synthetic OEM / Aurora EV MY27 / Cockpit Integration
synthetic sandbox
Public reference

No real organization, production data, entitlement, credential or workload is connected.

Production promoted: false
integration · IN region

Overview

Everything required to move from product choice to a diagnosable sandbox journey.

ENVIRONMENTsandboxproduction connected false
INTEGRATION PATH

Sandbox → production readiness

50%
  1. ProjectConfigured
  2. Entitlement2 effective
  3. Identity1 active
  4. First callSucceeded
  5. 5ConformanceRequired
  6. 6ProductionBlocked
API requests · today2,12697.7% successful
p95 latency184 mssynthetic sandbox window
Effective modules2exact environment rights
Readiness blockers3promotion remains false
MAP SDK + LOCATION API SANDBOX

Real Mappls interaction surface

Search places, inspect the basemap and validate the project’s browser integration. Production entitlement remains separate.

web SDK configured
Loading Mappls map
Project prj-sim-cockpitEnvironment sandboxProduction data false
EFFECTIVE PRODUCTS

Program scope

CV
Connected Vehicle Cloudvehicle.state.read · IN · oem_cloud
effective
EV
EV Journey & Charging Cloudjourney.energy.plan · IN · oem_cloud
effective
RECENT EVIDENCE

Activity

vehicle.state.readcorr-sim-veh-state-8842 · 200 · 142 ms
!
journey.energy.plancorr-sim-energy-7731 · 422 · 96 ms
!
ACTION REQUIRED · RELEASE LIFECYCLE

Routing profile v3 migration

126 synthetic calls use the affected profile. Move to v4 and acknowledge before 2026-11-30.

01

Visibility is not entitlement.

Every effective right carries environment, module, territory, platform, quota, term and policy revision. A request remains visibly distinct from approval or access.

02

A secret is a one-time response.

The persistent credential has only a masked identifier and fingerprint. Secret material is absent from project state, audit, traces, URLs and subsequent reads.

03

Promotion is an evidence decision.

Contract, security, operations, quota and network gates remain explicit. Passing conformance never silently creates a production identity.

One governed path across cloud, console, vehicle and embedded integration.

Developer onboarding is independently scopeable, while the first product contracts remain exact, entitled and release-versioned.

Developer Cloud + Automotive Console

Make the first sandbox journey—and every production gate—measurable.

Scope developer onboarding →Review the console blueprint ↗Review the cloud blueprint ↗