Internet Explorer as a service.

Before

After

No more polyfills, shims or vendor prefixes.

Never worry about Internet Explorer support.

Save your time, money, and sanity + close more deals.

Get on the waiting list

* We will never sell your address or send you junk.

FAQ

How does it work?

Quik works by running a modern browser headlessly and drawing a "canvas" of your site back to your end users. Keystrokes, mouse movements and other user interactions are supported out-of-the-box. Users install no extra software, and all session information (cookies, local storage) are deleted afterwards. In practically all cases, Quik is much better and faster than trying to support IE yourself.

How do I use it?

We'll have both a hosted on self-hosted solution, with which you can purchase a license or time on the service for. In order to use the service, we'll have documentation on how to run it via a client-side JavaScript library, or in your back-end technologies (like nginx, node, and more). Our goal is to make it easier and faster than current solutions like polyfills and feature-checks embedded into your application.

What doesn't work?

When we launch, you can expect users to interact with your site like normal. Certain browser features like audio, geo-location and clipboard won't work right away. As we continue to build we'll add support for these when we can.

When will you launch?

When we're ready! We currently have a few users in a private alpha using the technology in production. Once we get more stability, and extensive documentation, we'll reach out to subscribers and add them on a first-come first-serve basis.

What about dropping support for IE?

Of course! While we recommend dropping support as the primary way to handle older browsers, the truth is that many agencies and organizations simply cannot. Instead, using Quik can actually be more secure since common attack vectors like XSS aren't possible anymore. Quik will also work in place of other browsers as well that aren't considered modern, expanding what you can do with it beyond IE.

Why would I use this?

You can expect to use this if your team has to support older browsers, and you care about their sanity and time. We're aiming to make this solution much more cost-effective than hiring and supporting a team to handle this, leaving your team time to innovate in better areas.

Who are you?

We're the same team behind browserless.io, the first of its kind headless-browser service. We run millions of headless browser sessions every day, supporting some of the biggest and smallest users in the world. We have hands-on experience both in running and innovating when it comes to running headless browsers in production.

Why would you do this?

After spending more than decade having to support and ensure our sites are running on IE, we decided that it was time someone stepped up to the challenge of addressing the problem in an easier way. We found that even though current tools can help, it doesn't address the problem head-on. If you spend your time starting up VirtualBox, researching ES3 plugins, and looking over StackOverflow for answers, this was built for you.

How can I contact you?

While we're everything up and running in our production system, you can send us an email here. Be sure to mention Quik in your message.