The APIs are flexible and easy-to-use, supporting authentication, user identity, and complex enterprise features like SSO and SCIM provisioning. Learn more →
BrowserBox Alternatives
Similar projects and alternatives to BrowserBox
-
Fenix
Discontinued ⚠️ Fenix (Firefox for Android) moved to a new repository. It is now developed and maintained as part of: https://github.com/mozilla-mobile/firefox-android
-
vscodium
binary releases of VS Code without MS branding/telemetry/licensing
-
SurveyJS
Open-Source JSON Form Builder to Create Dynamic Forms Right in Your App. With SurveyJS form UI libraries, you can build and style forms in a fully-integrated drag & drop form builder, render them in your JS app, and store form submission data in any backend, inc. PHP, ASP.NET Core, and Node.js.
-
-
ArchiveBox
🗃 Open source self-hosted web archiving. Takes URLs/browser history/bookmarks/Pocket/Pinboard/etc., saves HTML, JS, PDFs, media, and more...
-
-
MeshCentral
A complete web-based remote monitoring and management web site. Once setup you can install agents and perform remote desktop session to devices on the local network or over the Internet.
-
-
WorkOS
The modern identity platform for B2B SaaS. The APIs are flexible and easy-to-use, supporting authentication, user identity, and complex enterprise features like SSO and SCIM provisioning.
-
windmill
Open-source developer platform to turn scripts into workflows and UIs. Fastest workflow engine (5x vs Airflow). Open-source alternative to Airplane and Retool.
-
-
-
-
touchHLE
High-level emulator for iPhone OS apps. This repo is used for issues, releases and CI. Submit patches at: https://review.gerrithub.io/admin/repos/touchHLE/touchHLE
-
DownloadNet
💾 DownloadNet - All content you browse online available offline. Search through the full-text of all pages in your browser history. ⭐️ Star to support our work!
-
action-tmate
Debug your GitHub Actions via SSH by using tmate to get access to the runner system itself.
-
-
Viewfinder
Discontinued 📷 BrowserBox - Remote isolated browser API for security, automation visibility and interactivity. Run on our cloud, or bring your own. Full scope double reverse web proxy with multi-tab, mobile-ready browser UI frontend. Plus co-browsing, advanced adaptive streaming, secure document viewing and more! But only in the Pro version. Get BB today! Secure your document needs and internet, today! [Moved to: https://github.com/crisdosyago/BrowserBox]
-
-
ViewFinder
Discontinued :camera: ViewFinder - NodeJS product to make the browser into a web app. WTF RBI. CBII. Remote browser isolation, embeddable browserview, secure chrome saas. Licenses, managed, self-hosted. Like S2, WebGap, Bromium, Authentic8, Menlo Security and Broadcom, but open source with free live demos available now! Also, integrated RBI/CDR with CDR from https://github.com/dosyago/p2%2e [Moved to: https://github.com/i5ik/ViewFinderJS] (by c9fe)
-
-
InfluxDB
Power Real-Time Data Analytics at Scale. Get real-time insights from all types of time series data with InfluxDB. Ingest, query, and analyze billions of data points in real-time with unbounded cardinality.
BrowserBox reviews and mentions
-
Show HN: CloudTabs Web Browser – a web browser on every website
Is that right? Could be a recent acquire if it's DOM mirroring.
I heard CF acquired S2 a few years ago, and what S2 did is they created a WebAssembly binary that composited the browser SKIA draw instructions on the client, and streamed the SKIA draw instructions from the server. Not without its issues, but certainly useful.
What we do is just stream pixels to the client. Yes it's expensive in terms of bandwidth, relatively. But the advantage is simplicity. And with a close server and bandwidth trending faster and cheaper, with the increasing drive to video consumption across media, I don't see bandwidth as an issue.
If you're interested, our code is on GitHub: https://github.com/BrowserBox/BrowserBox
-
Tell HN: Reddit now blocks VPN access via browser, 'old' subdomain included
> Edit: parent commenter seems to be promoting their product. Looks like a random remote browser, perhaps avoid entering important credentials there.
True. Maybe I should have put a full disclosure? I thought it was obvious, but I get if it wasn't. I'm sorry for not being more clear!
It's a good point to advise people to avoid entering important credentials in something that probably looks untrusted. I'd also advise that at this stage as we have no SLAs for now, and are just testing this SaaS-to-be demo of this source-available product:
https://github.com/BrowserBox/BrowserBox
Thank you for pointing out the reasonable and important security concerns. Although I should have probably done that myself, I was just so eager to help!
Aside: I am surprised tho that you were unable to even login on your VPN. I would think that the IP blocks we run the browser form and those of a VPN would be in the same category of 'cloud IPs', so why should it work on CloudTabs but fail for you directly on a VPN? Who knows?
-
Apache Guacamole: a clientless remote desktop gateway
These are difficult problems and perhaps the modern web has developed at a pace that older tech like RDP has not kept pace with. But Guacamole bucks that trend. The video shows how far it has come.
Guacamole is good, and I love that it's clientles and works in the browsers, but VNC lacks sound so you need to do that separately. Also the input lag when remote frames increase in frequency is challenging.
If you're looking for something lighter weight and possibly smoother and faster (albeit non-free software with a non-commercial option), check out BrowserBox: https://github.com/BrowserBox/BrowserBox
Solving input lag, and maintaining responsiveness across a range of bandwidth situations has been one of our priorities and I think we've mostly achieved.
We've accomplished this through a combination of sensible heuristics for congestion control, and using WebRTC with a fallback to WebSockets when faster. We also have audio out of the box, no set up required!
However there's always room to improve, which is why it makes it so exciting to work on. Depending on how close you are to a server you may encounter lag issues, too. Check out a free live demo of it working here (sorry, signup is not supported yet!):
https://browse.cloudtabs.net/signupless_session
Some other problems we solve that are not always so easy to configure with Guacamole (and are harder to do with an RDP layer in general), but much easier for us as we virtualize the browser itself are first class mobile support.
Obviously that's an issue with remoting desktops from small form devices in general, but if a browser is all you need remotely then we got your back! :)
Same time, BrowserBox will not be for everyone. It all depends on what you need. Get on touch if you are interested!
-
Kernel Hardening – Protect Linux User Accounts Against Brute Force Attacks
Run your browser on a remote machine? Using say BrowserBox: https://github.com/BrowserBox/BrowserBox
Full disclaimer: my company develops it.
-
Over 100k Infected Repos Found on GitHub
This sucks. Supply chain is such an issue.
Even tho we don't currently target any npm releases, I make use of socket.dev to monitor my project by creating an npm release for it. But my project BrowserBox (lightweight virtualized web browser) only uses ~800 dependencies including all descendents, with only 19 top-level deps (cool your heels non-JavaScript folks, this is comparatively lightweight for a full stack boing).
I'm considering just snapshotting all 800 deps into a @browserbox namespace at npm. And then tracking any vulnerabilities discovered and patching the fixes.
It sounds crazy, but that's where we are. At least that way I "own" all the dependencies and can guarantee (up to company security at least) that we don't have supply chain vulns on the Node/JS side.
-
Unicode Characters You Can Not See
I found this interesting so I made an invisible GitHub comment on this PR request: https://github.com/BrowserBox/BrowserBox/pull/702#issuecomme...
-
Instantly Deploy BrowserBox on Azure Cloud – open-source isolated browser
to actually send an email with the login link once deployment completes. I've added BrowserBox to many other cloud platforms' (Vultr, AWS, Linode) 1-click-deploy methods, but Azure is the only one (that I know) that can send this email.
Basically we use a bash script on the VM extension to run the install, and then use the Metrics API to write a metric datapoint, which triggers the email for the alert defined elsewhere in the ARM template.
I love the convenience of this! Install can take a while (particularly with the secure document viewer for PDFs, DOCX, etc because of all the fonts that need to be installed), and getting an email with the link that you can click on is just so easy.
If anyone's wondering the license, it's completely free and unencumbered to just use for personal/noncommercial/research use in anyway even modified, and also available under AGPL-3.0 if you want to modify source and use commercially for free under AGPL-3.0. If you'd rather just modify into a proprietary code base and integrate into a commercial system without releasing your own code under AGPL-3.0-or-later then we do offer a range of commercial licenses with a simple per-seat pricing module that discounts at high volume significantly. We also offer support, maintenance, customization, training and consulting.
This links to the Azure ARM quickstart for the main open-source version of BrowserBox. Just click the "Deploy to Azure" or "Deploy to AzureGov" links to give it a spin on your own account. I've made the setup as easy as possible.
We currently don't collect any telemetry at all (not even installs, but it can be inferred from various sources like GitHub clones, Docker pulls, etc ~ it's around 60 per day currently). We don't guarantee what's collected or not by Chrome headless, any dependent packages (we try to be pretty lean but it does run use npm so there's always risk, we use socket.dev to monitor any risks and aim to fix any vulnerable deps as soon as we see them), or the cloud platform or ISP you run on tho. We support tor both as a hidden service and a way to connect to the net, but it's tor-slow especially the latter. To run any of the tor switches you'll need to manually install.
Overall the main OSS version should work fairly solidly across browsers and devices (let me know at [email protected] if it doesn't!), but the important thing to remember is that everything can be customized, from the look, and chrome UI, to how it's embedded (in an iframe widget on your app, for instance, to default full-page), all the way down to the minutae of how the viewport is streamed over WebRTC and the audio chunks are streamed over websocket. If you want to dig into a fairly high performance, secure and reliable real-time app with real-world use cases, that out of the box supports many OSes (macOS, Ubuntu, Fedora, RHEL, CentOS, Debian, Kali, etc etc...even Windows but we insist you use the PSGallery installer if you are running on Windows: https://www.powershellgallery.com/packages/BrowserBox-Instal...), then definitely dig into the code!
It's open source on GitHub currently: https://github.com/BrowserBox/BrowserBox
Oh, and one final thing -- pick a low ping Azure region for your deployment! Ping is very important to give a great experience. The lower your ping, the less dependent everything is on your link bandwidth.
Let me know how it goes! :)
-
Show HN: Quetta – A privacy-first web browser with enhanced ad blocker inside
It's a tricky balance to strike. Obviously, krono, you're right: ff we're being generous the app launch GA tracker they use, they probably consider it shares nothing of value or identifiable, but strictly speaking it's not true that no data shared.
I think the audit you do is actually valuable. In my company's product, BrowserBox^0 (also a browser, funnily enough! focused on remote isolation, privacy & security, and including Tor support), we don't collect anything but we want to add some kind of telemetry regarding usage so we can even basically know how many daily users we have (outside of licensed channels where it's tracked in the contract).
Even tho we don't collect anything, we don't advertise "Zero data collection" anywhere, because of how sensitive I think this topic is. I think we really need to be solid on it, if we're going to say that. And to cover us, in the privacy policy, we say "we may collect some data for operational purposes to ensure the continued running of the service" (paraphrasing), even tho we don't.
One niggle is that we use Chrome in headless mode (can also use Edge / Chromium), and while we appreciate the auto updating quality that Chrome has for security patches, we're cautious that maybe Chrome still collects telemetry and sends it to Google even with headless and correct flags (see for instance: https://github.com/puppeteer/puppeteer/blob/afb7d9eb5854e851...)
I know it's not your job...but what's your advice on how to proceed specifically?
-
GitHub Actions as a time-sharing supercomputer
This is really cool, Alex: the ability to run arbitrary jobs on GitHub actions that you've wrapped into a convenient API that (I guess) automatically runs on the 3000 free-minutes that every GH account gets on default Ubuntu-runner actions every month.
Super cool, I love this idea!
Less general than you, but I also had a notion to do kewl shit on GH actions, and I figured out how to turn it into a a "personal ephemeral VPN-like" using BrowserBox. Basically, you fork/generate the BrowserBox project into your own account, enable Actions, and open the "Make VPN" issue template from the /issues/new page and voila! In a few minutes you get an up and running remote browser/private VPN that runs for 8 minutes or so (conservation, but you can tweak the value in the actions yaml!), and even cooler, the action job will post the login link into the comments section of the issue you opened!
One hassle I have still not avoided is the necessity of using ngrok for this. Sure, you can get around it using a tor hidden service which we also support, but that requires the user connecting via a tor browser.
Ngrok is required to create the tunnel from the BrowserBox running inside the GH Actions Runner, to the outside world.
Technically, this is probably possible by using mkcert on the IP address of the runner, and posting the rootCA.pem as an attachment to an issue comment. You then need to add it to your trust store and you're good to go, but ngrok is the easier way: sign up to ngrok, get your API key, add it to the Repository Secrets in settings and hit the "Make VPN" issue.
Seems like a lot of steps, so I added a "conversational" set of instructions posted by the runner as issue comments to guide you through it.
Check it out la! :)
https://github.com/BrowserBox/BrowserBox?tab=readme-ov-file#...
-
A note from our sponsor - WorkOS
workos.com | 17 Apr 2024
Stats
BrowserBox/BrowserBox is an open source project licensed under GNU General Public License v3.0 or later which is an OSI approved license.
The primary programming language of BrowserBox is JavaScript.