One studio, one gateway, every API.
AudicLabs is the customer-facing studio. Middleware is the governed front door for published APIs, handling identity, metering, permissions, documentation and upstream health while studio tools such as the Noise Suppressor keep their own product experience.
How traffic travels
Noise Suppressor
The studio validates the user session and sends the upload through the Middleware gateway with its server-only token, so every call is authenticated, metered and logged like a customer call.
Accounts and data
Accounts, workspaces and keys live in Cloud SQL Postgres, reached from the app server over TLS with the instance CA pinned.
New catalog service
Register an upstream and endpoint in Middleware; the live catalog makes it appear in the API Explorer without a frontend deployment.
What changes when an API is added
Adding a service is a Middleware configuration change. The service becomes visible to AudicLabs when it is active, has enabled endpoints, and the workspace token or plan has the matching scope.
- 1. Register the upstream base URL, authentication and health path.
- 2. Add endpoint schemas, content types, pricing and scopes.
- 3. Grant the workspace token or plan access.
- 4. Middleware probes the service and publishes the catalog.
- 5. AudicLabs fetches the catalog and renders the endpoint form automatically.
Status and health monitoring
The public status page probes the studio, the database, the Middleware gateway and the Noise Suppressor. Middleware independently probes every active registered upstream.
Public status
The public page reports Middleware health as an aggregate such as “2/2 upstreams up”. Machine monitoring is available at /api/status.
Individual service detail
The Middleware admin console shows each service row, health state and manual probe at internal.audiclabs.com/admin.
Production surfaces
AudicLabs
Studio · Docs · Status · Status JSON
Staging
No separate staging hostname is configured or verified in the current deployment, so no staging URL is shown here.