---
Source: https://docs.microblink.com/verify/deployment
Title: Deployment options
Description: Cloud and self-hosted deployment options for BlinkID Verify
---

# Deployment options

BlinkID Verify is available in two deployment models: a cloud API hosted by Microblink, and a self-hosted container you run in your own infrastructure.

## Cloud

The cloud API is the default and recommended option.
Microblink operates the infrastructure, handles scaling, and keeps the API up to date.

No setup is required beyond obtaining an API key.

### Dashboards

The cloud deployment includes access to production dashboards at [developer.microblink.com/dashboard/cloud](https://developer.microblink.com/dashboard/cloud).
They are tied to your developer account and license keys, and show real-world performance, usage, and trends for your integration.

## Self-hosted

The self-hosted deployment is an OCI container image you can run using Docker, Podman, or any other container runtime.
This gives you full control over the deployment environment and allows you to keep document images within your own infrastructure.

It can be deployed in a Kubernetes cluster for high availability and scaling.

For deployment instructions, see the reference pages for [Docker Compose](./docker-compose.md) and [Helm](./helm.md).

### API compatibility

The API surface for the self-hosted deployment is identical to the cloud version.
Requests have the same structure, except for the domain, port, and authentication, which are under your control.

See the [API reference](/verify/api/ref/v1) for details.


Last updated on Jun 18, 2026