Evidence tier Source Confirmed · 7 captures on record
What the publisher says
As described on Microsoft Marketplace.
Liutong is a self-hosted LLM gateway that you deploy directly into your own Azure subscription as a containerized App Service. Your application traffic flows through a proxy you control, so prompts, completions, and the keys behind them never leave your tenant — while billing is handled for you, pay-as-you-go, through Azure Marketplace.
It is built for teams that want the convenience of a managed, metered LLM service without handing their data to a third-party SaaS endpoint.
Show the rest of the publisher’s description (10 more lines)
Key benefits:
Runs in your tenant. Deployed as a Linux container on Azure App Service inside your subscription. Traffic and credentials stay within your Azure boundary.
Usage-based billing, done for you. Consumption is metered per 1,000 prompt tokens and per 1,000 completion tokens and reported to Azure Marketplace, so charges appear on your existing Azure invoice, no separate contract or payment relationship.
Secure by default. HTTPS-only with TLS 1.2 minimum, HTTP/2 enabled, and FTP access disabled. The gateway authenticates to Azure using a system-assigned managed identity, no secrets to store or rotate.
Fast, repeatable deployment. A single solution template provisions the App Service plan, the gateway, identity, and role assignment. Choose your region and plan size during deployment.
Flexible sizing. Start on a Basic plan for evaluation and scale up to Premium v3 for production throughput, with no change to how the gateway works.
How it works:
Point your application or LLM client at the gateway URL that the deployment outputs. The gateway proxies requests and tracks prompt and completion token usage as it goes. Usage is aggregated and flushed to the Azure Marketplace metering service on a regular cycle, so your bill reflects what you actually consume.
Getting started:
Select a plan, choose a globally-unique site name and an Azure region, and deploy. When the deployment finishes, the gateway URL is provided as an output and is ready to receive traffic. See the support link for configuration details and client setup.
Agent build and provenance
See the full provenance
The layer-by-layer build, the evidence behind each claim, the risk basis and the cross-marketplace links are open to any account. Some rows are disclosed, some the source leaves Unknown; a free account shows you which.
Compliance
- FedRAMPConfirmedNot listed90%, registry-checkedNo FedRAMP Marketplace entry matched this vendor's domain, checked 2026-08-27registry recordas observed 2026-08-27
Confirmed means matched to a public authoritative registry. Claimed means the vendor or its listing states it, not yet cross-checked. A framework not shown was not found in any source we hold, which is not evidence against it. Not listed means a scoped registry check found no match for this vendor's domain: a No is a scoped registry check, not a compliance judgment. Confidence bands: 95% domain-verified, 90% registry-checked, 80% self-attested, 70% weak signal. Self-attested items marked “vendor's site” are gathered from the vendor's own website and are not verified by us.
Sources
Publisher resources
1 linkLinked repositories
Unknown means this listing does not publish a repository. It is not a statement that the code is closed, and a linked repository is not a claim that the publisher wrote it: the registry computes that relationship privately and does not publish it.
Evidence risk is the share of the build you cannot see before you deploy, not a security rating. Sign in to see the layer-by-layer basis for this band.