📣 BIG NEWS: Neptune is joining OpenAI! → Read the message from our CEO 📣

Self-hosted deployment

A self-hosted experiment tracker that scales with you and stays with you

At Neptune, we’re fully invested in self-hosted. You can use it on your own terms, without scale limitations, or a push toward SaaS. Give your researchers the tools to monitor, optimize, and debug foundation model training while your platform team retains full control over infrastructure, data, and security.

Logo image Logo image Logo image Logo image Logo image Logo image Logo image
Highly availabile and reliable

With multi-zone deployment, automated failover, and consistent backups, you stay resilient during hardware failures, traffic spikes, or infra upgrades. No lost data, no training interruptions, even at scale.

Built for large-scale training pipelines

Neptune components scale vertically and horizontally to support high-throughput ingestion and fast retrieval, even with massive data volumes. No bottlenecks, no black boxes.

Everything inside your network

Deploy in your private cloud or on-prem, including fully air-gapped environments. Enforce your own SSO and meet internal security standards. Ensure sensitive logs and metrics never leave your infrastructure.

icon The architecture

State-of-the-art architecture for high-scale experiment tracking

Neptune’s core architecture was built to handle the demands of monitoring the largest training workflows. From strict security requirements to scaling ingestion, every aspect is engineered to support your specific needs and run seamlessly in your environment.

Ingestion throughput
+1M datapoints/second
Rendering charts of
+1M datapoints in <1s
Robust API for querying
logged metadata
icon Deployment options

Flexible deployment to match your infra and compliance needs

On-Premises

Deploy Neptune on your own hardware, behind your firewall, with fully air-gapped deployment supported.

Private Cloud

Install Neptune within your virtual private cloud. Supported Clouds include AWS, GCP, and Azure.

Dedicated Instance

Fully managed by Neptune, single-tenant deployment on a dedicated cloud instance provisioned just for you.

icon Checklist

Everything you’d expect from a self-hosted solution

Infrastructure & deployment

  • Kubernetes-only deployment: Helm Charts provided. Runs as non-root containers. No special K8s privileges required.

  • Bring your own services: Decomposable deployment architecture that allows for integrating with your Kafka, MySQL, ClickHouse, or Redis. Optional use of managed services.

  • Fully managed option available: We can operate Neptune on your infrastructure with proactive monitoring and alerting, backups, and 24/7 support.

High availability & disaster recovery

  • Multi-zone deployments: Single-region HA with workloads distributed across availability zones.

  • Backup & DR: Daily consistent backups with minimal ingestion freeze (below 1 min); offsite backup within the same cloud provider supported.

Scalability & performance

  • Horizontal & vertical scaling: Available on demand; Neptune components can be scaled independently.

  • Tiered storage support: SSDs used for recent data to ensure fast access, and HDDs for storing historical data efficiently.

  • Storage scalability: Ability to scale storage (ClickHouse) independently.

Security & access control

  • SSO/LDAP integration (SAML 2.0): Supports Okta, OneLogin, and custom identity providers.

  • Designed around SOC 2 principles: The architecture and processes follow security best practices for handling sensitive data.

  • Private deployments with full network isolation: Support for air-gapped deployment.

Monitoring & observability

  • Built-in Prometheus, Grafana, OpenTelemetry or forward logs and metrics to your existing tools.

  • Dashboards and alerts: A configured set of Grafana dashboards and alerts provided (e.g., for ingestion and retrieval disruptions).

Upgrades & testing

  • Dedicated test environments: Separate license for staging environments and upgrade validation.

  • Seamless upgrades with minor ingestion pause: Retrievals stay online during upgrades; ingestion may pause briefly (up to 5 mins) with no impact on training jobs (data is queued).

icon Next steps

How to get started with self-hosted Neptune

1

Review prerequisites & docs

Ensure a smooth start by understanding what’s needed.

  • Check system prerequisites
  • Review architecture and installation documentation
  • Evaluate environment compatibility
2

Talk to us

Let’s align on your needs, ideal setup, and expectations.

  • Discuss your team’s specific requirements
  • Explore deployment options
  • Get tailored recommendations about instance size and configuration
3

Deploy a proof of concept

Test Neptune in your environment before full commitment.

  • Guided POC setup — with the right prerequisites, it’s typically done in 1 day
  • Live demos, Q&A sessions, and technical support
  • Validate performance and integration

Move from POC to full-scale use with confidence.

decor
Frequently asked questions

Yes, you can bring your own services and other answers

  • With the right prerequisites in place, you can have Neptune up and running in 1 day.

    Deployment involves installing our Helm chart and connecting to services like ClickHouse, Kafka, Redis, and MySQL. If your infrastructure is already provisioned and you’re using Terraform (or are open to reusing our Terraform modules), setup is fast and straightforward.

    In environments with custom automation, security constraints, or additional scaling needs (e.g., tuning ingest gateways), plan for some extra time, typically 2–3 days depending on complexity.

    We support deployments on GCP, Azure, and AWS, and provide templates and guidance to make the process smooth.

  • Depending on your setup, it may be possible to deploy and use Neptune without Kubernetes.

    We’ve seen a wide range of production environments. If you’re unsure whether Neptune fits your infra, reach out, we’re happy to talk through it.

     

  • Yes. You can bring your own Kafka, MySQL, ClickHouse, Redis, and storage layers. If not available, all of these can be part of the Neptune deployment.

  • Yes. Neptune supports tiered storage in ClickHouse. Frequently accessed data goes on SSD, and older data can move to cheaper/higher‐latency storage.

  • No. All services can be deployed in an air-gapped environment. No forced external connectivity is required.

Deploy a scalable, highly available, and secure experiment tracking in your infrastructure