Development · head-to-head
BrewPage vs CORS Proxy
BrewPage is a free, account-less content host: a POST to endpoints like brewpage.app/api/html turns HTML, Markdown, JSON, key-value pairs, or a whole multi-file site into a short public URL, protected by an anonymous owner token instead of a login. Pages default to a 15-day TTL (30-day max) and can be password-protected, and the project ships both an MCP server (brewpage-mcp on npm) and a Claude Code plugin for programmatic publishing.
CORS Proxy is a small open-source Node.js server (54 GitHub stars) that forwards a POST request's urlToGet body param to the target URL server-side and relays the response back with permissive CORS headers, sidestepping browser CORS errors for GET-able resources. It is a deploy-it-yourself utility, not a hosted service — the README's old Heroku demo link is dead since Heroku retired free dynos in 2022, so it only works once cloned and deployed to your own host.
| BrewPage | CORS Proxy | |
|---|---|---|
| Authentication | None | None |
| Pricing | free | free |
| Formats | HTML, JSON, Markdown | JSON |
| CORS | no | yes |
| HTTPS | Yes | Yes |
CORS Proxy supports CORS, while BrewPage doesn't — pick CORS Proxy for direct browser calls.