Howdy, Stranger!

It looks like you're new here. If you want to get involved, click one of these buttons!


New on LowEndTalk? Please Register and read our Community Rules.

All new Registrations are manually reviewed and approved, so a short delay after registration may occur before your account becomes active.

CDNShark beta program: looking for ~25 testers (CDN, VPS, hosting, email, storage, 1 year included)

13»

Comments

  • edited November 17

    Some thoughts (I have more and I'll post them later this is just briefly from what I've used so far). Overall I'm very happy with the service and I think it is really great, so the following will focus mainly on issues I found / things I'd hope would be improved a bit. But my overall impression is by no means negative.

    • Lots of features, nice. Looks like you guys are maybe trying to compete with cloudflare which is definitely nice, it is always good to have more players
    • At least for me 1TB bw on CDN is a bit limited, Cloudflare offers unlimited bw so that's nice. But I think this might not be an issue for "normal" users (lol)
    • 10GB storage.. give me 300TB :D
    • Site could use a bit of organization. I get there are a lot of products, that is good. But it feels like maybe it started as just a ew products and more and more got added on one by one. I think it would really help to rethink how this is all organized / perhaps merge some "products" into one.

      • E.g., "Stream (VOD)" + "Live Stream" -> just a Stream product.
      • "LLM Gateway" again can probably be merged into something else
      • "CDN storage" + "Backups & Sync" into one
      • A lot of these products require an active CDN plan. Perhaps they could all be merged into one? But honestly maybe it makes more sense to separate this from a CDN plan. E.g. why do I need a CDN plan for object storage? Maybe would make it easier for people who don't use CDN product to use other services.
    • UI could use a bit of organization too. Sidebar has wayyy too much. A bit difficult to get to where I want to go. Analytics sidebar item already expands/collapses, maybe reorganize into something like:

      • CDN

        • Zones (domains, move DNS under domains, + under attack)
        • Captcha
      • Cloud

        • Compute (VPS + hosting)
        • Email
        • Storage (S3 + backups)
        • Stream (VOD + live)
        • Tunnels (merge LLM gateway into this)
      • etc. (you get the idea)

    Tldr: good product, many well implemented features, could use a bit of work w/ organization and focus/direction IMO. But ofc it is still quite early.

    Good luck!

    Thanked by 1BasToTheMax
  • Also no offense but Sharky is a bit dumb. Like Clippy but not annoying. But I like the concept. Maybe give it access to more of the account, let it take on tasks for the user, access VPS's etc. (with approval ofc)

    Thanked by 1itzsenu
  • CDNSharkCDNShark Member, Patron Provider

    @averagedatahoarder

    Thanks for taking the time to write this up, and for the kind words.

    Organisation: You are right, and we were already planning it. The product list did grow one service at a time, and the portal shows it. There are some products we designed for our existing customers for their customer applications, like SharkMQ and Valkey Cache, also showing in the sidebar.

    We're regrouping the sidebar into sections along the lines you suggested (CDN & Security, Storage, Stream with VOD and Live together, Compute, Network, Email), with billing and developer tools folded away. It should be much quicker to get where you want to go.

    Why some products need a CDN plan: for most of them it's because the traffic actually runs through the CDN. Hosting, VOD, Live and Tunnels are all served through our edge network, so your server/hosting origin IP stays hidden and you get caching, WAF and DDoS protection in front of them. That traffic uses bandwidth, and the CDN plan is where the bandwidth allowance comes from. Products that don't touch the edge (VPS, Email, CAPTCHA) don't need a CDN plan at all.

    Limits (1 TB bandwidth, 10 GB storage): the beta plans are deliberately conservative. We will be happy to increase the limit if a tester asks for a valid reason for testing. We won't promise "unlimited", but limits will be revisited before launch, and feedback like yours helps set them.

    300 TB might take a little longer :). Our S3 storage runs on a multi-region cluster, and every object is stored 3 times, each copy in a different region. So 1 GB of a user's storage is 3 GB for us.

    Merging products: grouping them in the portal is the first step.

    Looking forward to the rest of your notes. Please do post them, or send them through the bug reporter in the portal.

    Nath, CDNShark

    Thanked by 1averagedatahoarder
  • @CDNShark said: Why some products need a CDN plan: for most of them it's because the traffic actually runs through the CDN. Hosting, VOD, Live and Tunnels are all served through our edge network, so your server/hosting origin IP stays hidden and you get caching, WAF and DDoS protection in front of them. That traffic uses bandwidth, and the CDN plan is where the bandwidth allowance comes from. Products that don't touch the edge (VPS, Email, CAPTCHA) don't need a CDN plan at all.

    Ah I see, that makes sense!

    @CDNShark said: Limits (1 TB bandwidth, 10 GB storage): the beta plans are deliberately conservative. We will be happy to increase the limit if a tester asks for a valid reason for testing. We won't promise "unlimited", but limits will be revisited before launch, and feedback like yours helps set them.

    Yeah that completely makes sense ... I just think that for the average user you may need something really competitive to offset Cloudflare offering unlimited / unmetered bandwidth. Of course there are those of us (some of my sites as well) that are kicked off of Cloudflare or at risk of being kicked off Cloudflare but I doubt you would want to take on these sorts of sites either.

    So of course limiting bandwidth makes sense but IMO the other products need to pretty clearly offset this limitation

    @CDNShark said: 300 TB might take a little longer . Our S3 storage runs on a multi-region cluster, and every object is stored 3 times, each copy in a different region. So 1 GB of a user's storage is 3 GB for us.

    Ah yeah makes sense

  • Damn, I didn't even know there was a beta testing program going on. I would have been happy to test network security, look for L2 management plane traffic leaks and unknown-unicode leaks, etc.

  • rpqurpqu Member

    @forest said:
    Damn, I didn't even know there was a beta testing program going on. I would have been happy to test network security, look for L2 management plane traffic leaks and unknown-unicode leaks, etc.

    Too bad man. It was gone in less than an hour.

  • @rpqu said:

    @forest said:
    Damn, I didn't even know there was a beta testing program going on. I would have been happy to test network security, look for L2 management plane traffic leaks and unknown-unicode leaks, etc.

    Too bad man. It was gone in less than an hour.

    Wow!

  • @CDNShark @averagedatahoarder

    My opinion about the site's design is different. This is something I wanted to mention, though I haven't yet since we've focused on functionalities and bugs. I find the site's organization clear, easy to read, and easy to navigate. We have reported bugs and missing features, but the service feels professional, mature, and well-organized, and so far we have not hit any of the technical walls that sometimes come with a provider's architecture choices.

    The reason some items may look like they could be grouped is precisely because they are easy to read and understand as separate entries. Merging them risks turning each page into a dense block where only the services you already use are visible, while the others become obscure links. For example, Stream VOD (upload, transcode, playback tokens) and Live Stream (ingest, HLS/WHEP, DVR) are different workflows; a single "Stream" page could hide that distinction. The CDN plan requirement is a packaging question, not a reason to merge the navigation.

    When I applied for the beta, the list of services alone was enough to see the fit with our project. I did not have to dig through the site to understand what CDNShark actually offers, which is exactly what a clear product organization should achieve.

  • @Amari said:
    @CDNShark @averagedatahoarder

    My opinion about the site's design is different. This is something I wanted to mention, though I haven't yet since we've focused on functionalities and bugs. I find the site's organization clear, easy to read, and easy to navigate. We have reported bugs and missing features, but the service feels professional, mature, and well-organized, and so far we have not hit any of the technical walls that sometimes come with a provider's architecture choices.

    The reason some items may look like they could be grouped is precisely because they are easy to read and understand as separate entries. Merging them risks turning each page into a dense block where only the services you already use are visible, while the others become obscure links. For example, Stream VOD (upload, transcode, playback tokens) and Live Stream (ingest, HLS/WHEP, DVR) are different workflows; a single "Stream" page could hide that distinction. The CDN plan requirement is a packaging question, not a reason to merge the navigation.

    When I applied for the beta, the list of services alone was enough to see the fit with our project. I did not have to dig through the site to understand what CDNShark actually offers, which is exactly what a clear product organization should achieve.

    Was this written by a LLM?

  • Grouping the nav isn’t merging the workflows. “Stream -> VOD / Live” keeps both pages exactly as they are, one click away, just without a dozen top-level entries competing for attention. Nothing gets hidden. It gets organized.

    And of course the flat list feels clear to you: you’re using nearly every product on the platform. Most users run two or three services and have to scroll past everything else to reach them. A sidebar should be judged by the person looking for one thing, not the one using all of them.

    As for the service list being what sold you on applying: that’s what the marketing site and the beta thread are for. The control panel is for getting work done, not for showing off the catalogue.

    CDNShark has already regrouped it along these lines. Every product is still there, and it’s far easier to navigate. If that’s “obscure links,” I’ll take it.

    If you tag me with a post written by a LLM, I shall feed my thoughts into a LLM and respond back with an AI-written reply. Generated by Claude Fable 5.2.

  • @averagedatahoarder said:

    @Amari said:
    @CDNShark @averagedatahoarder

    My opinion about the site's design is different. This is something I wanted to mention, though I haven't yet since we've focused on functionalities and bugs. I find the site's organization clear, easy to read, and easy to navigate. We have reported bugs and missing features, but the service feels professional, mature, and well-organized, and so far we have not hit any of the technical walls that sometimes come with a provider's architecture choices.

    The reason some items may look like they could be grouped is precisely because they are easy to read and understand as separate entries. Merging them risks turning each page into a dense block where only the services you already use are visible, while the others become obscure links. For example, Stream VOD (upload, transcode, playback tokens) and Live Stream (ingest, HLS/WHEP, DVR) are different workflows; a single "Stream" page could hide that distinction. The CDN plan requirement is a packaging question, not a reason to merge the navigation.

    When I applied for the beta, the list of services alone was enough to see the fit with our project. I did not have to dig through the site to understand what CDNShark actually offers, which is exactly what a clear product organization should achieve.

    Was this written by a LLM?

    Why would an LLM express an opinion like that one?

Sign In or Register to comment.