How long does the integration take?

Change one base URL in an OpenAI-compatible client, or install the Python or TypeScript SDK; the quickstart routes a first request in a few minutes.

Will this lock us into another vendor?

No. The router is Apache-2.0 open source, your provider keys stay yours, and the API is OpenAI-compatible, so leaving is a change of base URL.

What happens when a provider fails?

The router falls back to the next model your policy allows and records the fallback in the trace, so an outage costs a retry, not an incident.

product-site - Skill - OpenSmartRoute

Imported from zlovtnik/ssl-proxy (apps/product-site/AGENTS.md). Install upstream with npx skills add zlovtnik/ssl-proxy --skill product-site. Copyright stays with the author.

Product site

This is a static public marketing frontend, separate from the operator consoles.
Use Astro pages and SolidJS islands. Product demos use synthetic fixtures; Octopus operational metrics must come from the runtime feed, never fixtures.
Keep core navigation, product copy, and email contact available without JavaScript.
Analytics may be added only with explicit consent, minimal event data, no PII, and production-only configuration. Never add advertising or identity tracking.
Preserve the Search observation/identity caveat and SQL-file snapshot/backup caveat.
Run npm run build and npm test for site changes.
Keep accessibility evidence in docs/accessibility-matrix.md; distinguish automated evidence from pending assistive-technology and participant evaluation.
Shared branding, type, spacing, and controls live in src/styles/site.css. Route stylesheets compose those patterns and must not redefine them.
Copy lives in src/data/products.ts. Follow docs/messaging.md and docs/design-system.md when adding copy or patterns; publish mechanisms, not savings, latency, or market claims. The two caveats, the contact labels, and the audience statements belong to that model, not to a route or a component.
npm test measures rendered text, control boundaries, and focus rings on every route in the shared dark theme. Keep new colours and controls inside those targets.
Dark is the only theme; ignore saved theme values and system colour preferences. Preserve the other reading preferences and forced-colours support.
A public build needs PUBLIC_SITE_URL. Publication follows the reviewed Git deployment path; the local site does not provision hosting.

Install product-site and it becomes one more candidate the router can pick - when it fits.

A listing is a routing target with a manifest: what it does, which domains it covers, what it costs and who publishes it. Once installed it sits beside your own models and tools, is scored like any other candidate for each request, and shows up in the trace when it wins. Ratings come from workspaces that installed it, one per account.

product-site

About

Product site

Use it

Install product-site and it becomes one more candidate the router can pick - when it fits.

What it costs to adopt - in engineering time.

One base URL

No vendor lock-in

Failover built in

Manifest

Reviews