Kodexa is a platform designed to allow you to deploy document processing use-cases easily, quickly, securely but also with controls.

In this guide we will walk through how we see the process of deploying a use-case to Kodexa, first we will define how we typically see a use-case deployed in Kodexa.

​
Use-Case Deployment

A use-case is usually deployed as a project or as a common project template, depending on the approach you with to take.

​
Resource Deployment

Resource deployment focuses on managing a project’s lifecycle across different environments - from development to UAT to production. This approach is ideal when you have a large number of documents that need to be processed at scale, requiring a robust deployment strategy.

This deployment pattern involves building out a comprehensive process that combines data definitions, storage, processing, and often data validation and quality control elements. The key benefit is maintaining control over resources in higher environments while leveraging standard developer tools such as git and pull requests for version control.

To implement this approach, we use the Kodexa CLI along with a manifest file - a YAML file that describes all the resources to be deployed as part of a project. For detailed step-by-step instructions on setting up resource deployment, refer to the Resource Deployments guide.

# This is a Manifest file
resources-paths:
  - "models/*.yml"
  - "resources/taxonomy.yml"
  - "resources/invoice-data-form.yml"