Infrastructure

You don't operate Vendo's infrastructure — Vendo does. But when something breaks at 2am, or when you're deciding whether a feature is feasible, you want a real mental model of what's under your tool.

This section is that model. Each page is written from the perspective of a tool author who needs to debug, configure, or reason about behavior — not from the perspective of someone running the platform.

What runs where

• Runtime targets — which compute backend each tool type hits.
• Subdomains — how *.vendo.run resolves, custom domains.
• Regions — where deployments land.

The request path

• The proxy — what {provider}-proxy.vendo.run does to your call.
• Credentials worker — how credentials.vendo.run vends OAuth tokens.
• Healthchecks — the contract, and what happens when you fail it.

Configuration and observability

• Secrets and env vars — what gets injected at boot.
• Logs and observability — where to look when something is wrong.
• Scaling and limits — resource ceilings.
• Isolation — what's per-tenant, what's shared.
• Background workers — the cron workers whose names appear in logs and support tickets.

Vendo subdomain inventory

A quick map of which Vendo-owned hosts do what. Your tool generally only talks to the three at the top.