---
Source: https://docs.microblink.com/verify/quick-start-on-prem
Title: Quick start (on-prem)
Description: Quick start guide to using the BlinkID Verify on-prem API
---

# Quick start (on-prem)

Verify runs as a single container image that bundles the API, the processing workers, and the machine learning models.
You can deploy it in your own cloud, or on your own hardware, using any OCI-compliant container runtime.

## Prerequisites

### License

You need a license key and an application ID.
Contact [sales](mailto:sales@microblink.com) to get a license; the credentials are then available in the [developer hub](https://developer.microblink.com/).

### Only x86-64 ISA

Verify does not support ARM processors, only x86-64 (AMD64) processors.

### Resources

Per container:

- Minimum: 2 CPU cores, 4 GB of memory
- Recommended: 4 CPU cores, 8 GB of memory

### Docker

This article uses Docker for image and container management, but you can use any other OCI-compliant tool.

Minimum Docker version: >= 20.10.5.

## Get the image

```bash
docker pull us-docker.pkg.dev/document-verification-public/on-prem/core:4000.0.0
```

## Run the container

```bash
docker run -p 8080:8080  \
  -e LICENSE_KEY={your_license_key} \
  -e LICENSE_APPLICATION_ID={your_application_id} \
  us-docker.pkg.dev/document-verification-public/on-prem/core:4000.0.0
```

## Make a request

You can now make your first request:

<ApiSample
  method="POST"
  url="http://localhost:8080/api/v3/verify"
  formData={[
    { name: "imageFirstSide", fileName: "front_id.jpg" },
    { name: "imageSecondSide", fileName: "back_id.png" },
  ]}
/>

See how to [configure](./configuration.md) your requests, and learn how to [interpret the response](./response.md).

## Going to production

The single `docker run` above is enough to get started, but for production, more configuration is needed:

- Always set a memory limit. 
  Overload protection is a percentage of the cgroup memory limit, and it's disabled when there is no limit, so the container can't reject requests before it runs out of memory.
- Run the container under a restart policy. 
  It runs the API, the workers, and the model server as separate processes, and nothing restarts inside the container: if any of them exits, the whole container exits and needs to be brought back as one unit.

Read more:

- [Docker Compose](./docker-compose.md) for a single host
- [Helm](./helm.md) for Kubernetes


Last updated on Aug 4, 2026