Deploy on premises
In case you need larger capacity than supplied by business plan, we also supply on-premises deployment option that has no daily query limit.
In order to use our NER model locally you should:
- register as user (if not yet registered)
- upgrade to enterprise plan in User area -> Upgrade
- execute a payment with invoice number as a purpose of payment
- once a license key is available at User area -> Credentials page you can start installing
- deployment status is available at User area -> Deployments
It is recommended to use Docker images for on-premises deployment. Deployment works fine with either Docker, Docker Compose, Docker Swarm, or Microk8s. Example setup package includes Dockerfile, and bash start script using microk8s.
Hardware requirements for on-premises deployment:
| Space on disk required by built Docker image: | < 660MB |
| Space on disk required by NER model: | < 30MB |
| Peak memory usage by Docker container: | < 450MB |
Example package contents:
You can download example setup package here: download (~2KB). Contents of ZIP file:
| Dockerfile | Builds docker image for NER model service. |
| Microk8s deployment configuration | Sets up single container, single pod deployment running locally on 8005 port. |
| Microk8s service configuration | Sets up http service available on private cluster IP on 8005 port. |
| Bash start script |
Builds and deploys docker image using Microk8s configuration on local machine. This file requires modifications, such as setting License Key or Internal API Key. |
Upstream communication:
API server deployed on premises does very little communication with upstream server. Currently following requests are being sent:
- Instance up status (on server start)
- Instance ping status (once an hour)
- Latest model download request (once an hour)
- Instance down status (on server shutdown)