You can expose the container to your network directly or put it in front of a reverse proxy if you need SSL/authentication/other features provided by servers like nginx or Caddy.If you purchase more than 1 instance, you may not load balance across them (per our license and per the container’s implementation). Each instance must stand alone, but you may run them in different contexts/environments (e.g. dev, staging, prod).If you need concurrency across > 1 GPU, reach out to support@datalab.to about a custom contract.
License activation and usage heartbeats do not send private data to Datalab.Our intent is to ensure compliance with our license and to easily support customers when they run into problems.The container sends the following to our servers:
On container startup we activate your license. In that request, we send information about your hardware and OS available in /proc and /sys (in the container, not on your host).
At regular intervals we send usage heartbeats that contain:
The # of successful/failed inference requests completed since the last heartbeat
The # of inference requests submitted to the container over a recent time window
We support fully-airgapped deployments, higher volume & concurrency, and white glove support with custom enterprise contractsPlease reach out to us at support@datalab.to if you have questions.