Product · September 30, 2026
A model you host stays where you put it
An endpoint on your cloud, including a weight without a vendor refusal layer, is still your endpoint. The allow-list still applies.
Separator can sit in front of an endpoint the customer runs. That includes a model the customer hosts because it wants a different refusal layer than a vendor API provides.
The weights stay on the customer's cloud. VeloxitySI does not download them, does not host them, and does not rename the output as the work of another model.
Attaching that endpoint does not move a refused part onto another lane. The allow-list still binds. The customer remains responsible for the endpoint and for the law that applies to what it returns.
Evading a vendor's policy on that vendor's own service is a different matter, and the acceptable use policy refuses it. Hosting your own endpoint is not a way to present that vendor's service as something else.