powered by ASAP


Unveiling the Core SDK

Understanding the Mechanics of Our Automation Framework

Born from our framework, the Core SDK is our automation heart, securely executing workflows with traceability. It provides a wealth of base components for building applications and offers customization for specific automation needs.

Leverage an Exceptionally Rich API

Java 11-Based Core SDK


Old / deprecated components can be replaced without rewriting whole applications.


Use the given SPI to extend the functionality of the core.


Write your own base components for your specific automation needs.


Reuse our / your base components inside new applications.

Core SDK

Essential Components


Is the base component which executes a Model.


Is the “workflow” which will be executed by the engine. It describes the automation as a “sequence” of Commands.

Model Interpreter

The Model Interpreter is responsible for mapping specific models (like BPMN) to our generic Model. It also determines how the Model should behave and be executed at runtime.


Is the smallest unit of a Model. They execute some specific Task like “write x to file y”. Once written they can be reused over & over again.

Command Interpreter

Parameterizes and executes specific Commands. It is possible to create Commands in different languages (Java, Kotlin) or standards like Open API.

Command Pool & Collectors

Provides the needed Commands to the Engine at runtime while executing the Model. For example there are Command Pools which can fetch all your Commands from a Maven Repository or from a local directory.

Credential Manager

Manages and provides all credentials which are needed by a Command to connect to a specific tool. The Manager does not connect to any tool itself, this is still done by the specific Command(Service).

Persistence Service

Stores and provides all data which are created or needed by the Commands at runtime.

FuSe (Functional Security)

Is a component which can trace specific data of the Model execution. This allows to do specific monitoring of the executions done by the Engine.

  1. First a Workflow in a specific format like BPMN (or any other), will be passed to the Engine.
  2. The registered Model Interpreter will parse this Workflow to a generic Model.
  3. The Model consists of Commands which will be loaded by the Command Pool.
  4. If all Commands of the Model are available, the execution of the Model begins or resumes until all Commands are finished.
    1. Dependent on the Model and the last execution state, the Engine adds one or multiple Commands to the operation queue or finishes the execution.
    2. If the Engine is not finished, each queued Command will be parameterized and executed by its specific Command Interpreter.
    3. The Command then will do its task until its finished or failed.
    4. At the end of this loop, all results of the last Command execution are written back to the Persistence Service.

Create your own Applications based on the Core SDK components

You have specific automation needs? No Problem!

Once written, each base component and Command can be reused in any application. This means that specific requirements on the part of the user or the target platform can be implemented with ease.

Create your own base components by implementing our APIs

Some Examples

  • You want to execute a different Model specification than BPMN? Write your own Model Interpreter.
  • You want to save all created data inside a specific database? Write your own Persistence Service.
  • Your credentials are hosted by a central tool and you want use it? Write your own Credential Manager.
  • You want to fetch your Commands from another artifact repository? Write your own Command Pool & Collector.
  • You want to support Commands written in a different language or standard? Write your own Command Interpreter.
  • The Engine should work in a different or extended way? Write your own Engine or register Observers & Callbacks to extend it.

In order to provide you with the best possible service, please don't hesitate to get in touch. Whether you're keen on discovering more about PAK, considering a partnership, looking to become part of our team, or wishing to share your successful experiences with PAK, your input is highly valued. Fill out the contact form below and we'll get back to you promptly.

Need a tailored solution or have questions about PAK?

We are here to help. 

For all inquiries, please feel free to reach out at

You are looking for a job?
We have the perfect solution!

Join us and find an exciting task in the environment of PAK.

You are looking for a job?
We have the perfect solution!

Join us and find an exciting task in the environment of PAK.

© ASAP 2024

Sonatype Nexus

PAK features connectors and commands for Sonatype Nexus. This means the software can directly interact with Nexus repositories for storing and managing artifacts. Through these connectors, PAK can automate tasks like uploading binaries or retrieving dependencies, ensuring efficient artifact management within Nexus.


PAK has connectors and commands for Jenkins. This allows the software to directly communicate with Jenkins servers, enabling the automation of CI/CD (Continuous Integration/Continuous Deployment) tasks. Through these connectors, PAK can trigger builds, fetch build statuses, or manage job configurations, streamlining the CI/CD processes within Jenkins.

Git Hub

PAK possesses connectors and commands for GitHub. This means the software can interface directly with GitHub repositories, facilitating actions like code pushes, pull requests, or issue tracking. Through these connectors, PAK can automate various GitHub operations, enhancing code collaboration and repository management.

Atlassian Confluence

PAK is equipped with connectors and commands for Atlassian Confluence. This enables the software to directly interact with Confluence spaces and pages. Through these connectors, PAK can automate actions such as creating, updating, or retrieving documentation, ensuring efficient content management and collaboration within Confluence.


PAK features connectors and commands for Codebeamer. This allows the software to seamlessly integrate with Codebeamer’s ALM (Application Lifecycle Management) platform. Through these connectors, PAK can automate tasks like issue tracking, test management, or requirements tracing, enhancing the coordination and management of software development processes.

JFrog Artifactory

PAK has connectors and commands for JFrog Artifactory. This means the software can directly interface with Artifactory repositories, enabling actions like artifact storage, retrieval, and management. Through these connectors, PAK can automate tasks such as deploying artifacts or managing repository configurations, streamlining the integration and management of binary artifacts within Artifactory.

Amazon Web Services (AWS)

PAK has connectors and commands for Amazon Web Services (AWS). This means the software possesses specialized interfaces to directly interact with AWS services and execute actions on the AWS platform. Through these connectors, PAK can automate AWS-specific commands, such as launching EC2 instances, managing S3 buckets, or configuring Lambda functions. This allows for efficient integration, management, and automation of AWS resources and services directly from PAK.

Atlassian Jira

PAK features integration tools and capabilities for Atlassian Jira. These tools allow for a direct connection to Jira and the execution of specific actions. Using these integration tools, PAK can automate Jira actions such as adding comments or changing ticket priorities, ensuring seamless handling and coordination of Jira processes.


PAK has connectors and commands for Git. This means it has interfaces to directly communicate with Git and execute actions. Through these connectors, the software can automate Git commands such as retrieving changes or creating branches, enabling efficient integration and management of Git tasks.

Generic Human Tasks

PAK offers you a standard set of commands which require creative input from the user. Enables you to start with automating your workflows, that still need abit of human input.

Generic Commands

PAK offers a standard set of commands giving you the first steps to automate your workflows.

Nexus Maven Command Pool

Nexus is an artifact repository manager for storing binaries, libraries, and artifacts, supporting formats like Maven. Maven, a software project management tool, is based on the Project Object Model (POM) and allows developers to consistently define projects and dependencies. Our Command Pool offers commands for interactions between Maven and Nexus, such as artifact uploads or dependency retrieval.

Artifactory Maven Command Pool

Artifactory allows developers to store, retrieve, and manage binary files and artifacts, providing a
central source for all binaries used in a development process. Apache Maven is a software project
management and comprehension tool that enables developers to consistently describe a project and
its dependencies. Our Command Pool offers a collection of commands used to facilitate interactions
between Maven and Artifactory, such as uploading artifacts or retrieving dependencies.

Open API Command Interpreter

The OpenApi Command Interpreter allows you the automatic parsing of commands from an OpenApi defintion. No additional code needs to be written anymore, just add the address to the definition and our framework does the rest!

Kotlin Command Interpreter

The Kotlin Command Interpreter allows you the parsing and execution of commands within a Kotlin environment to automate various tasks or processes.

Bpmn Interpreter

Workflows come in many shapes and forms. The BPMN (Business Process Model and Notation) Interpreter enables the parsing of worklows defined in the BPMN format into the PAK intern model.

Human Task Interpreter

The Human Task Interpreter allows you the parsing and running of commands within a HTML and Javascript environment. Use this to build commands which need the creative input of a workflow user!

Java Command Interpreter

The Java Command Interpreter allows you the parsing and execution of commands within a Java
environment to automate various tasks or processes.


The heart of the PAK-Framework. Contains the means to run workflows with the PAK engine, but also the possibility to enrich the frameworks interfaces with your own implementations and solutions.

RocksDB Persistence

Data that is generated by a workflow run needs to be saved for short or longer terms. Our solution to the Persistence Interface of the PAK-Framework is to use the high-performance, key-value based RocksDB developed by Facebook.

PAK online

PAK Online is a web based application and provides an Open API based REST API. It enables you to upload workflows and run them periodically or on REST demand.

Command Line App

Run tasks and workflows on the console or as part of a CI/CD Pipeline with our Command Line Interface.

Workflow Editor

With our specially developed editor, a wide variety of workflows can be easily modeled in the wide known BPMN process format.

Workflow Executor

The Workflow Executor is the application to run your workflows. It features a multilingual UI and easy managment of your favorite workflows.


We offer a community website where you can exchange ideas and support each other. For our Pro packages we also offer full support via email.