Deploy and operate
Choose a runtime mode and verify service health, access, and recovery before directing clients to the deployment.
On this page
Choose a deployment mode
- Standalone service
- Install one graphlake-admin process for the browser, HTTP, and optional Bolt and Gremlin endpoints.
- Distributed service
- Use a Coordinator with private Workers for supported distributed operations. Run the same build on all nodes and provide access to the mapped data.
- Coordinator failover
- Use etcd for leadership, S3-compatible shared control state, and TLS ingress that probes the elected Coordinator.
See the cluster installation guide for configuration, startup, HA, and acceptance checks.
Secure the client entry point
For shared browser access, use an HTTPS reverse proxy and set --public-url to the exact browser origin. Create model-level roles for query, export, modeling, publishing, and audit. Use role-based service accounts for application drivers and scoped personal tokens for AI clients.
Keep database credentials in server-side environment settings. See the service and client reference for proxy headers and protocol configuration.
Check health and data access
Check the build at /healthz and readiness at /readyz. Use runtime health to probe published sources and Workers, then run a known-result query through the same ingress clients use. Collect Prometheus metrics, audit events, and OpenTelemetry signals as needed.
See the monitoring guide for probe and telemetry setup.
Upgrade, roll back, and recover
Back up the catalog and credential configuration, and keep the previous binary release. Stop the standalone service, unpack the new archive into a separate directory, switch current and the unit as needed, then restart. Confirm the running build, model revision, and known-result query. Rollback restores the old release and its matching catalog when needed.
For off-site recovery, keep a checkpoint that binds control state, PostgreSQL and Parquet snapshots, and expected business-query results. In the target /recovery page, import the checkpoint and pass acceptance checks before reopening traffic. Include local table artifacts referenced by the control export and keep a separate catalog backup for standalone deployments.
See the upgrade guide and backup and recovery guide.