Frequently asked questions

When will Licorice be available for general release?

We expect the first release of Licorice to be ready by mid-2021. Right now, we’re working with Pilot clients to get Licorice to an absolute maximum of usefulness. If you want to request early access, you can do so here.

How can I provide feedback?

Right now, there are two ways to provide feedback about what you want to see in Licorice—you may either contact us directly or become a Pilot client. We’re listening!

How much will Licorice cost?

Licorice is freemium—you are free to use and try it without limitation from 1 to 3 people. For 4+ people, Licorice is US$30/mo per user (for all people). This price is subject to change.

What are Licorice’s system requirements?

Licorice runs in a browser. We support up-to-date Chrome, Firefox, Safari, and Edge Chromium. The minimum supported screen resolution is 1920×1080.

Does Licorice work on mobile devices?

Full mobile support will be implemented in a future release. We know this is a “mobile-first” world. However, IT professionals spend a lot of time on computers and tablets/2-in-1 laptops, so we need to get the workflows right there first, and then we’ll focus on getting mobile right.

Licorice should also work on Chromebooks and thin clients (as long as their browsers are reasonably modern).

Does Licorice work on tablets?

As long as they have a minimum resolution of 1920×1080 and a reasonably modern browser, then yes. There are no special requirements.

Can Licorice be self-hosted?

At present, we have no plans for self-hosted installations. Instead, we’re focusing on proper in-browser performance and regional isolation—meaning Licorice can be hosted in the country or region you select, and your data will never leave that country/region. If you have specific requirements, please let us know.

What’s wrong with ‘tickets’?

They’re not ‘bad’ per se. However, IT support services have two main types of work:

  1. Emergent tasks that need to happen immediately; and
  2. Known tasks that need to happen in the future.

We believe that for type 2, tickets are not the appropriate tool. We will be talking at length on this topic in our blog as time goes on.