WingNews logo WingNews
top | item 30433104

Launch HN: Hyperbeam API (YC W22) – Multiplayer embeds of any website

96 points| declan_g | 4 years ago

Hi HN, we’re Philip, Amby, and Declan from Hyperbeam (https://www.hyperbeam.dev). Hyperbeam is an API that makes it easy for developers to embed real-time multiplayer capabilities into their web apps—including any other web app that you want to provide multiplayer access to.

Building software to connect people in real time is hard. We experienced this in college when we built a “watch party” site for people to watch movies together (https://hyperbeam.com). Other watch party solutions were unreliable, so we spent two years building tech to allow friends to watch stuff together with ease.

The key piece was a “multiplayer web browser”. By that we mean a Chromium instance that you embed inside your own web app (i.e. web browser inception) which is actually hosted on a server and streamed via WebRTC, and so can be shared and controlled by multiple people at the same time.

For example, say you have an online tutoring platform. An instructor can open any application in the embedded web browser and then work on it with the student together.

Another use case is making non-multiplayer apps multiplayer. One of our customers wanted to add a collaborative version of Google Slides to their product, so multiple participants could navigate the slides at once. Google doesn't provide an API for that, so users had to screen share, which isn't multiplayer. With Hyperbeam, you just open up a shared instance of Google Slides and then multiple people can control it.

We didn’t learn about those use cases until later, though. What happened was that we grew hyperbeam.com to 150k monthly active users and over 1M hours of video per month, but then it stopped growing. Despite this, we got into YC, and soon had multiple companies asking to buy our multiplayer browsing tech. After closing three deals, we decided to sell our multiplayer web browsers as an API. That way other companies can build products to connect others without going through two years of WebRTC hell like we did.

We allow developers to embed multiplayer web browsers in their web apps with a few lines of code. Users can then visit any website from inside that web app together. Developers can specify control permissions, programmatically navigate to specific URLs, and hide the browser UI so apps appear as if they are natively integrated.

Unlike screen share solutions that upload your personal computer stream to participants, Hyperbeam’s multiplayer web browsers run on our own virtual machines. This eliminates the upload speed bottleneck that many users experience.

We host a Chromium browser instance on our server, record the video and audio output and stream it to all participants using WebRTC. That sounds simple, but hosting full-blown Chromium instances is challenging, especially doing it cost-effectively: what we learned is Chromium instances, at scale, love memory bandwidth a lot more than the amount of memory. Also, network unreliability, like last-mile packet loss, is also a problem, especially audio packet loss which is a lot more noticeable than video packet loss. A simple hack we have in place is literally sending every audio RTP packet twice, which improves audio quality drastically over spotty connections.

Anyone is welcome to get a free playground API key and try our product! Rather than spend time building a UI for that, we’ve just put up a Google Form in the spirit of do-things-that-don’t-scale. Go to https://forms.gle/RSQhbFXbdrcqwqsc9, fill in your email and we promise to send you an API key right away. The API docs are here: https://showy-backpack-b3f.notion.site/Hyperbeam-API-eb9874b...

Pricing is not transparent on our website yet—we’re still working it out. However, we’re going to use the same business model as CPaaS companies such as Agora and Twilio. We’ll charge customers a minimum amount per month and provide a set amount of participant hours. If a customer exceeds the provided participant hours, we continue charging at a fixed rate.

If you want to try our tech in action, you can do that by signing up for free and creating a room using our original Hyperbeam watch party platform: https://hyperbeam.com/app/register

Alternatively, we'll be answering questions live in our HN watch party here: https://gg.hyperbeam.com/invite/w0c6n-Ko

We’re happy to answer any questions you have, and would love to hear your ideas for other potential use cases as well. Thanks!

63 comments

order

vgel|4 years ago

Curious about how concurrent edits work. In, say, Figma, two users can simultaneously each create a text box and type into it. In my naive understanding of how Hyperbeam works, the remote Chrome instance would be receiving two streams of input events. Would those streams be interleaved, resulting in typing going to the wrong text box for one user? Or is there a different approach?

viewfinderjs|4 years ago

I love Hyperbeam! Such a good name. You guys definitely have the best name out of all the remote embeddable browser co-browsing products.

I've also got embeddable multiplayer web browsers you can stick in an iframe at https://dosyago.com and an instant demo live now at https://freebrowsers.dosyago.com plus there's also an source-available version on GitHub at https://GitHub.com/crisdosyago/Viewfinder

And I also applied for YC S22. I guess... there goes my application! and I don't need to wait for the rejection now, heh.

Seriously tho, I love your polish and how you've beautifully marketed it to a particular social watch party niche. Very cool!

And looking at your demo, the way it's running a desktop browser from mobile, I'm guessing you maybe use Guacamole and VNC to a remote virtual desktop?

ambyjkl|4 years ago

Thanks! That name took a lot of thinking for sure :D

Good luck for YC, and don't give up if you get rejected, it took us three tries to get in haha.

We don't use VNC, we send an H.264 stream over WebRTC. Also, checked out your demo, and it seems you use VNC?

omarfarooq|4 years ago

We would love an API key at https://color.museum to experiment with using Hyperbeam to enable collaborative art (ie. through our https://color.museum/gallery)

Looking forward to it! Thank you.

ScottyFillups|4 years ago

We sent an API key! Feel free to email us at founders@hyperbeam.com if you need anything else.

Donckele|4 years ago

On my latest mobile safari I’m getting a blank screen. How come?

chinathrow|4 years ago

Is your site satire? You are selling colors?

dustymcp|4 years ago

Did you actually Sell any colors?

edmcnulty101|4 years ago

Is there a tutorial that I can check out to understand this better?

declan_g|4 years ago

If you're looking for a demo of the API specifically, you can check out the demo video on https://hyperbeam.dev.

If you're looking to try out the embedded web browsers, you can check out our watch party site https://hyperbeam.com, create an account, create a room, and then start up a multiplayer web browser! However, it only shows off a subset of the functionality of the API.

Finally, you can view our API documentation here if you prefer: https://showy-backpack-b3f.notion.site/Hyperbeam-API-eb9874b...

jwkane|4 years ago

Spent some time blocking a big pile of abuse from users utilizing hyperbeam.com for IP anonymity. It left a bad taste for legitimate uses of the system.

ScottyFillups|4 years ago

Hi jwkane,

I'm sorry that you've been negatively affected by hyperbeam.com. I'd be happy to discuss the abuse you're experiencing, and what we can do to help.

We try our best to discourage hyperbeam.com as an ad-hoc proxy — the goal of the product is to provide hassle-free watch parties.

Edit: my email is scotty@hyperbeam.com

trevor-e|4 years ago

Your demo video won't play: "Video can't be played because the file is corrupt."

declan_g|4 years ago

Weird, it's working for me? What browser are you using?

vgel|4 years ago

Since AFAIU it's a video stream without any DOM, is there any accessibility affordance?

ambyjkl|4 years ago

Currently, we do not have accessibility support for the browser, we only do the video stream. The reason we haven't worked on this yet is because of our focus on watch parties, and the video stream being streamed was usually that of a video itself, so not a lot of accessibility could be added to that use case. But now that we are looking at the bigger picture, we could implement full-fledged accessibility support where we serialize the accessibility tree and send that over instead of the video stream.

mwcampbell|4 years ago

Congrats on your launch. I do have one concern though:

> a Chromium instance that you embed inside your own web app

Have you considered the accessibility ramifications of this, e.g. for blind people using screen readers? It will certainly be possible to make this accessible; indeed, that's an advantage of your approach over screen sharing. It won't be easy, but of course I believe it's still important and worth doing. My email address is in my profile if you want to discuss this further.

ScottyFillups|4 years ago

Thank you!

> Have you considered the accessibility ramifications of this, e.g. for blind people using screen readers?

We are considering the accessibility ramifications now since we've pivoted toward a general API. We didn't focus on accessibility for blind people initially because we were building a watch party platform.

I think offering accessibility features would give us a massive edge against technologies like screenshare! Is there a specific use-case you're thinking of?

unfocussed_mike|4 years ago

> indeed, that's an advantage of your approach over screen sharing.

In what way, particularly? it's streaming the video and audio from a remote browser instance, so surely that means all participants will have the same accessibility settings in the remotely viewed instance.

notacanofsoda|4 years ago

Neat, looks like Mighty app but multi-user. Interesting that both companies are YC funded.

ScottyFillups|4 years ago

Yeah, that's one way of looking at it: a multiplayer Mighty app that you can iframe into your own website.

In terms of how we're different, Mighty focuses on performance while we focus on collaboration.

nichol4s|4 years ago

Interesting! Something pretty similar to what enable at https://www.surfly.com the difference is that we focus more on B2B types of integrations and stream the actual DOM instead of a WebRTC videostream.

Good luck!