Run it anywhere

You run and use the software every day, on your laptop, phone, or in the cloud. Sometimes you run the same application in the cloud or on-prem infrastructure, possibly a virtual machine or Docker container. Some tools only run in the cloud or on a specific operating system. Maybe the tool is compiled to run on Linux or Windows operating systems, limiting your ability to run it anywhere.

Some software platforms contain many applications bundled together to big installation files, with web servers, databases, command-line tools, etc. Those packages do a lot of things, and they can get quite complex. That is normal because the software platform covers a lot of aspects it is trying to solve. On the other hand, why do you need to install everything just because you need one tool in the bundle?

What about the dependencies our tools need? For example, libraries, frameworks, or runtimes? We need to think about those when deploying to specific environments like Kubernetes or other cloud infrastructure.

We simplified Beekn to the degree that it can run almost anywhere, on all major operating systems, in cloud and on-prem. You do not need to install any dependencies, framework, or runtimes. You download a Beekn and run it. That's it. Just run it in your operating system of choice.

Operating system

Generally, we support three major operating systems, Windows, Linux, and macOS. You can target the operating system and runtime when configuring a Beekn.

Infrastructure

You can run Beekn on your laptop, on the on-prem test server, or in the cloud. We can also build a Docker image for you and push it to your favorite Docker registry, or you can build it yourself. That also means you can run it in Kubernetes.

CI/CD pipelines

Where ever you host your Beekn you can trigger it from your automation processes, CI/CD pipelines, test scripts, etc.

Beekn run modes

Beekn comes in 2 run modes, on-demand and continuously on-schedule. On-demand mode allows running Beekn as a process on-demand from your desktop, script, or CI/CD pipeline. On the other hand, you can run Beekn continuously with a manual or on-schedule trigger at a specific date and time.

To summarize, the Beekn allows you to be flexible and give you capabilities to plan how, where, and when you want to run your back-end tests. Your team will feel more confident and deliver maximum value to your customers.