Join the discussion

Write your take first — we'll ask for email only when you're ready to publish.

  • Hacker News
  • Stopped reading at proprietary. Seriously why would I care tying my app to something proprietary and have no way out of it?
  • What makes you think you can download it and use it yourself? This is just CloudFlare discussing their internal tech stack.
  • clever name
  • What does it mean ?
  • Another un-google-able (OXY as in Occidental Petroleum Corp?) name for a Rust project. We just cannot help ourselves.
  • You google "Rust oxy proxy" and the first like 10 hits are Cloudflare's blog about it, a few HN posts.....

    seems fine to me?

  • Look at the ADA language: GPS (GNAT Pro Studio) AWS (ADA Web Server) and ADA itself (American with disabilities act).
  • The article states that it's a proprietary project
    by jalk
  • How does it compare to Pangora?
  • Is it the same thing? Perhaps oxy was later renamed to pingora?
  • The linked blog post has an entire section about that:

    https://blog.cloudflare.com/introducing-oxy/#relation-to

    > Although Pingora, another proxy server developed by us in Rust, shares some similarities with Oxy, it was intentionally designed as a separate proxy server with a different objective.

  • Oxy sounds cool, but proprietary stuff is a hard pass for me. Just give me open-source any day.
  • (2023)
  • So why is this surfacing again now and why not a up to date article on Oxy? Which sounds very useful btw.
  • There are always people who haven't heard about stuff. https://xkcd.com/1053/
    by wmf
  • Interesting. No mention of kernel bypass, which Cloudflare was also discussing in 2023-2024.
  • Outside of HPC/HFT most people will never need kernel bypass. If you just got off Nginx you probably have years of optimizations left to do. (Username checks out though.)
    by wmf
  • Although Oxy is a closed, internal project, seems like they released part of it under a BSD license. Not the networking part, but a Rust library to create "production-grade systems".

    https://github.com/cloudflare/foundations

  • A proprietary project. I was surprised to realize how little interest I have in these things anymore. I mean genuinely surprised. I suppose I have just seen so many large-corporation-does-something in isolation projects that I make two possibly wrong assumptions.

    1) It will never work 2) The article is just advertising. Jobs, products whatever.

    There is a third conclusion which is worrisome. That the leadership of the organization just doesn't get it.

    I'm not advocating these as correct, just wondering if other readers share my instantaneous reaction of been-there, seen-that, know-how-it-ends.

  • I spent some time on Friday trying out Cloudflare tunnel and boy was it a bad experience. The big killer was that the tunnel endpoint they gave me had an IPv6-only endpoint that I'm not sure was even valid. None of my devices could connect to it, including macbook, phone, linux, AWS instance...

    On top of that I keep running into unexpected roadblocks with Cloudflare, like when I was trying to set up the tunnel they required me to set up a dedicated domain, you can't set up a subdomain of an existing domain. Probably fine if you are rolling it out as a production service, but for just testing it to make sure it even works (see IPv6 comments above), I just wanted to set it up as a subdomain.

  • localtunnel[1] is one good option, at least for now.

    [1] https://localtunnel.github.io/www/

  • Haven't used Cloudflare in a while, but in the past you needed $200/month Business plan to be able to use subdomains of an existing domain with DNS hosted elsewhere.
  • We spent 3 days trying to properly integrate their tunnels to our internal network. I took us 3 hours to integrate tailscale.

    Tunnels are poorly documented.

  • We're using Cloudflare Zero Trust quite extensively, and I find them quite easy to use. Works perfectly from AWS as well, all their endpoints have both IPv4 and IPv6 IPs.
  • That really sums up the cloudflare experience and this is from someone heavily invested in their workers platform. They have lots of products and keep pumping more but except for DNS, most of them are half assed with weak maintenance/support.
  • It was a smooth experience for me. Just start the cloudflared container with the provided key in the environment and you are done. I also don't have ipv6 but it is not required and if I remember correctly I did not have to specify any endpoints, just the key.
    by Jnr
  • I'm very surprised to see all of the negativity toward Cloudflare's usability and value here.

    It's been relatively painless for me to set up tunnels secured by SSO to expose dashboards and other internal tools across my distributed team using the free plan. Yes, I need to get a little creative with my DNS records (to avoid nested subdomain restrictions), but this is not really much of a nuisance given all of the value they're giving me for free.

    And after paying just a little bit ($10-20 per month), I'm getting geo-based routing through their load balancers to ensure that customers are getting the fastest connection to my infra. All with built-in failover in case a region goes down.

  • Works great for me, 5 subdomains coming to various ports on my dev pc for whatever project I'm testing (8000 for laravel, 3000 for nextjs). Way better than ngrok.