MapplsAutoBuild your program
Developer docs · SaaS assurance

Eleven cloud products. Twenty-two contracts. No optimistic authority.

Each Mappls Auto SaaS product connects canonical requirements, synchronous and event contracts, deterministic domain behavior, a public synthetic workflow and explicit production gates. Analytics, intent and receipts stay separate from partner, human, vehicle and physical outcomes.

Explore APIs →Application assurance ↗Define a cloud program ↗
Portfolio evidence

A complete contract and authority index for SAAS-01 through SAAS-11.

Three supporting domains remain named adjuncts rather than silently changing the canonical catalogue.

11

Canonical SaaS products

Every SAAS ID binds requirements, synchronous and event contracts, domain logic, tests and a public lab.

22

Versioned contracts

OpenAPI and AsyncAPI entry points for every canonical SaaS product.

3

Adjunct domains

Embedded navigation, video evidence and rider guidance stay explicit without inflating the catalogue.

0

Implied outcomes

No analytic, intent, receipt or UI state silently becomes a vehicle, partner, human or physical result.

Canonical SaaS catalogue

Authority, degradation and terminal truth—service by service.

Every product card states the evidence it may trust and the outcome it cannot claim.

SAAS-01Contracts + domain

Connected Vehicle Cloud

Authority

Verified device/vehicle binding, purpose-qualified telemetry and a monotonic digital twin

Degraded states
  • ↘Offline journal
  • ↘Sequence gap
  • ↘Late evidence
  • ↘Consent withdrawn
Terminal boundary

Ingest, projection, command receipt and physical execution remain distinct.

Run public lab →
SAAS-02Contracts + domain

InTouch Fleet Control Tower

Authority

Source-qualified asset state, canonical case revision and proof-gated closure

Degraded states
  • ↘Stale asset
  • ↘Source conflict
  • ↘Off-duty privacy
  • ↘Media denied
Terminal boundary

Case actions do not prove driver contact, dispatch or physical resolution.

Run public lab →
SAAS-03Contracts + domain

RouteNet Optimization

Authority

Versioned demand, eligible resources, declared constraints and an explicit objective

Degraded states
  • ↘Partial feasibility
  • ↘Unassigned work
  • ↘Stale matrix
  • ↘Locked work
Terminal boundary

A feasible plan, assignment or publish receipt does not dispatch work.

Run public lab →
SAAS-04Contracts + domain

Map & Content Lifecycle

Authority

Signed immutable manifest, quality evidence, compatible cohort and population receipts

Degraded states
  • ↘Quality blocked
  • ↘Invalid signature
  • ↘Activation failed
  • ↘Rollback required
Terminal boundary

Release, download, verification, activation and installed population stay separate.

Run public lab →
SAAS-05Contracts + domain

EV Journey & Charging

Authority

Fresh BMS context, vehicle calibration, versioned energy model and qualified chargers

Degraded states
  • ↘Stale BMS
  • ↘Reserve breach
  • ↘Charger excluded
  • ↘Low confidence
Terminal boundary

Prediction and discovery do not prove battery state, availability, reservation or payment.

Run public lab →
SAAS-06Contracts + domain

eHorizon & HD Map Cloud

Authority

Signed corridor content, consumer allowlist, current localization and probable path

Degraded states
  • ↘Ambiguous path
  • ↘Stale content
  • ↘Low localization
  • ↘Outside coverage
Terminal boundary

Map context does not replace perception, decide a function or control a vehicle.

Run public lab →
SAAS-07Contracts + domain

Mobility Orchestration

Authority

Eligible quote, canonical booking/trip revisions and trip-scoped pickup evidence

Degraded states
  • ↘Out of area
  • ↘Quote expired
  • ↘Assignment offered
  • ↘Pickup mismatch
Terminal boundary

Quote, booking, assignment and arrival do not prove dispatch, presence or trip completion.

Run public lab →
SAAS-08Contracts + domain

Geoanalytics Command Center

Authority

Qualified incident location, eligible resource snapshot and canonical provider state

Degraded states
  • ↘Ambiguous location
  • ↘Emergency boundary
  • ↘No resource
  • ↘CRM mismatch
Terminal boundary

Recommendation and provider state do not prove dispatch, repair or customer outcome.

Run public lab →
SAAS-09Contracts + domain

AI Cockpit Orchestration

Authority

Bound session/context, signed typed tools, policy and fresh consequence confirmation

Degraded states
  • ↘Model unavailable
  • ↘Local fallback
  • ↘Tool rejected
  • ↘Moving blocked
Terminal boundary

Model proposals and confirmations never become tool, partner or vehicle execution.

Run public lab →
SAAS-10Contracts + domain

Developer & Entitlement Cloud

Authority

Exact project/environment revision, effective rights and signed conformance

Degraded states
  • ↘Request pending
  • ↘Scope denied
  • ↘Credential revoked
  • ↘Promotion blocked
Terminal boundary

Request, credential intent, conformance and production promotion remain separate.

Run public lab →
SAAS-11Contracts + domain

Charging Intelligence Operations

Authority

Qualified asset picture, versioned demand, explainable scoring and entitled work intent

Degraded states
  • ↘Stale asset
  • ↘Source conflict
  • ↘Coverage gap
  • ↘No field capacity
Terminal boundary

Analysis, candidate score and work intent do not imply investment or field action.

Run public lab →
Production cloud gates

A domain test is evidence—not a production SLA.

A released tenant adds real identity, data, capacity, resilience, security and accountable customer operations.

Tenant & region

Program, organization, environment, territory, residency and isolation are explicit.

Contract lifecycle

Schemas, errors, retries, idempotency, compatibility and deprecation are governed.

Data rights

Source rights, purpose, consent, minimization, retention, deletion and transfer are product behavior.

Capacity & recovery

Budgets, SLOs, backpressure, backups, restore and dependency failure are tested.

Operational evidence

Logs, metrics, traces, gaps, incidents, support and billing definitions remain attributable.

Release acceptance

Security, migration, open deviations and accountable customer approval remain external gates.

Cross-service failure containment

A failure stays with the authority that can prove and recover it.

Adjacent services may degrade their own view; they cannot fabricate continuity.

Stale source evidenceSuppress freshness-dependent decisionsRetain last observation with ageDo not label it live
Contract incompatibilityReject or quarantineRetain request and version evidenceNo best-effort mutation
Dependency timeoutReturn pending or uncertainApply bounded retry/idempotencyNo inferred partner result
Partial outageExpose affected capabilityPreserve unrelated authoritiesRecord gaps and recovery
Target reference boundary

The public labs use synthetic evidence. They contain no live tenant, credential, customer payload, production data source, billing record, operational SLA or customer acceptance.

OEM program workshop

Bring us the vehicle. Leave with the program shape.

Choose the surfaces, modules, deployment and lifecycle that fit your next RFQ. We will turn it into a focused discovery brief.

Build your program Open developer hub ↗