Product / deployment
Choose the operational boundary you want to own.
Run a local Docker node for evaluation, self-host where your team controls the environment, or request managed infrastructure. The options are related, but their performance and security characteristics are not interchangeable.
Self-hosted
Docker on your infrastructure
Good for local development, controlled environments, and teams that want to own the runtime boundary.
bashCode can be copied to the clipboard.
docker run -d --name liorandb -p 27018:27018 -p 27019:27019 -p 27201:27201 -v ldb-data:/var/lib/liorandb/data liorandb/liorandb:pre-alphaManaged
Provision through the dashboard
Use app.liorandb.com to request Starter or Dedicated infrastructure. Provisioning and support terms are described on pricing.
Open dashboardStudio
Inspect and operate
Launch the official Studio destination when your deployment exposes the supported access path.
Launch StudioOperational checklist
Before you call it production.
Own the basics
- • Pin the engine and driver versions.
- • Persist the data directory outside the container lifecycle.
- • Establish network boundaries and secret rotation.
- • Test restore and recovery behavior on your exact deployment.
Verify the differences
- • Local benchmark settings do not define managed instance throughput.
- • Feature availability can differ by deployment and release track.
- • Confirm backups, retention, support, and limits from current terms.
- • Treat gRPC/REST availability as deployment-specific until confirmed.