lokis.cloud

What It Is

lokis.cloud presents a cross-origin request proxy API whose core purpose is to let browsers send requests to arbitrary target URLs, with the proxy adding CORS headers to the response. It provides help on the root path, a /iscorsneeded test resource, and the ability to forward requests by appending the target URL to the proxy path. The page also links to the CORS Anywhere demo, source code, and documentation.

Core Capabilities

Functionally, it focuses on solving the CORS restrictions commonly encountered in frontend development. If the target protocol is omitted, http is used by default; when the port is 443, https is used. The service strips Cookies and disables Cookie forwarding, so it is not suitable for APIs that rely on login state or session Cookies. Redirects are followed automatically, up to 5 times, with redirect details recorded in debug response headers. It also provides X-Request-URL and X-Final-URL for checking the requested URL and the final URL.

Open Source, Self-Hosting, and Ecosystem

The page clearly provides the source code address github.com/Rob--W/cors-anywhere/, indicating that the implementation is based on the open-source CORS Anywhere project. Teams with backend capabilities can refer to the source code and self-host it to avoid the stability and compliance risks of using a public proxy. In terms of documentation, the page covers basic usage, request header requirements, redirects, and Cookie rules, and links to the GitHub documentation. However, there is no visible information about lokis.cloud’s own service status, maintainer, rate limits, error codes, or SLA.

Pricing and Limits

The captured text does not provide any pricing, plans, payment methods, or request quota information, so it is not possible to determine whether the service is free, rate-limited, or permitted for commercial use. The service requires requests to include an Origin or X-Requested-With header to prevent it from being used for ordinary web browsing. It also recommends not setting these headers manually, in order to avoid unnecessary OPTIONS preflight requests.

Pros, Cons, and Best-Fit Users

Its advantages are simple usage, clear debugging information, and traceable open-source origins. It is suitable for frontend developers who need to temporarily verify CORS issues, debug access to third-party resources, or use it as a reference implementation for a self-hosted proxy. Its drawbacks are that it has a narrow focus and is not a full API gateway; Cookie stripping limits many real-world business scenarios; and the public service lacks sufficient information about stability, security boundaries, privacy, and compliance.

Access from China and Alternatives

The page does not provide information about access from mainland China, so actual connectivity, latency, and availability need to be tested independently; the current assessment is unknown. If connectivity is unstable on domestic networks, alternatives include self-hosting CORS Anywhere, or building a controlled reverse proxy with Cloudflare Workers, Node.js/Express, or Nginx. For production environments, backend relay or proper CORS configuration on the target service is recommended instead of long-term reliance on a public proxy.