Apiro Release Versions
Apiro Community Version.
Full-featured and free to use - without the enterpise features such as SSO and HA.
Everything you can do on the commercial versions you can do on the community version. Handy for software developers to use locally while formulating new schemas, orchestration and pipeline scriptables.
In addition we release the community version more often so commercial users may test upcoming enhancements prior to the enterprise release, and we potentially use newer versions of the JDK as well (though you may override this).
Running Apiro locally.
As mentioned in another section Apiro is not a consumer software application and is designed to be run on server class hardware.
There may be instances where it is desirable to run Apiro standalone locally. The main reasons being evaluation and development (either low level where you are creating new plugin classes to add to Apiro or doing detailed in-depth pipeline development with a lot of scripting where it is advantageous having direct access to filtering and tailing the application console log).
In addition, doing this sort of work it is very advantageous to do it independently on your own standalone instance so your own activities do not mix with side effects from other users.
So having decided to deploy Apiro locally - you have two options:
Software Artifact Level
Deploying components at the software Artifact level - namely Maven repository artifacts
If you are a software developer and will be developing new Java based components or complex groovy components, you will benefit from developing inside an Integrated Development Environment (IDE). Apiro provides maven based starter apps on GitHub to get you up an running instantly - along with some sample custom components you can integrate immediately.
Container Virtualisation level (Docker Compose option)
Deploying components at the container virtualisation level - namely Docker repository artifacts
If you are not developing new components at the java software level, and do not require full low level single step debugging functionality you would be comfortable as a software developer, and you are just developing pipelines from existing componeents, whether out of the box or supplied by another group within your company, deploying Apiro at a higher level via docker may be more convenient.
Caveat - Docker is a Unix (specifically Linux) oriented virtualisation technology, and Windows loads Docker containers by running a linux VM, wither through the Windows Subsystem For Linux on new releases or on a heavyweight VM in older releases. Although WSL2 is better both involve some loss of performance.
Therefore, if you are running Windows on an older box with more constrained resources, provided you have the necessary knowledge to do so you may benefit from running the lower level deployment via Maven and Java directly. In that case Apiro is run using the native Java Windows Runtime which is optimised specifically for windows and thus bypasses the OS virtualisation layer. On higher specification modern hardware you should not notice that much difference.
Apiro Commercial
Standard commercial offering of Apiro, with enterprise features provided as Kubernetes components and a sample helm chart. Organisations may deploy it as they with in their own private, public or hybrid infrastructure.
Apiro Cloud
Hosted and managed pay-as-you-go cloud instances of Apiro Commercial
Apiro Enterprise
For large corporate deployments. Please contact us for licensing details as this is determined per client.