Public origin contract
Everything customers interact with lives on one of a small set of public origins. This page is the canonical list. There are no private URLs, port-forwards, or internal service names you need to know about as a customer.
The public origins
Section titled “The public origins”| Surface | Purpose | Where you use it |
|---|---|---|
| Console | Authenticated web UI for creating tests, running them, and reading results. | Browser — https://app.maxoperf.com (or your dedicated console origin). |
| Platform API | HTTPS API for automation and integrations. | CI pipelines, scripts, SDKs. |
| Results ingest | Dedicated endpoint that receives run data from authorized engines. | Engines and infrastructure with run-scoped credentials. |
| Status page | Live operational status of the MaxoPerf platform. | Anyone, no auth required. See Status page. |
| Documentation portal | The site you are reading right now. | Anyone, no auth required. |
| Marketing site | Pricing, blog, comparisons, and product pages. | Anyone, no auth required. |
Stability promise
Section titled “Stability promise”- The console and Platform API are versioned. Breaking changes go through a deprecation window communicated in release notes and on the API reference.
- Results ingest is a contract-versioned endpoint. Engines authorized by MaxoPerf are kept in sync; you do not need to call this endpoint manually.
- The status page is always reachable, even when other surfaces are degraded.
Authentication summary
Section titled “Authentication summary”- Console uses a single-sign-on flow through your identity provider.
- Platform API uses bearer tokens issued from the console or from your CI integration. See Run tests from CI.
- Results ingest uses run-scoped, write-only credentials that MaxoPerf issues to authorized engines automatically.
- Status page has no authentication.
What is not a public surface
Section titled “What is not a public surface”You do not need (and should not depend on) any of the following:
- Per-service hostnames.
- Internal cluster URLs.
- Direct database, cache, or message-bus endpoints.
If you find yourself trying to reach something that is not on the list above, treat it as a sign that the workflow you are after has a higher-level surface. Reach out to support if you cannot find the right one.
Where to go next
Section titled “Where to go next”- API reference — full HTTP surface and request shapes.
- Status page — operational status, history, and incident updates.
- Run tests from CI — how to use the Platform API from a build pipeline.