# Quickstart (/docs/enterprise/helm/installation/quickstart)



<Callout type="info">
  Installation Journey
  [Prerequisites](/enterprise/helm/installation/prerequisites/) → **Quickstart** (you are here) → [Configure](/enterprise/helm/configuration/helm-values/)
</Callout>

Get a minimal NetBox Enterprise instance running with default settings. This guide uses internal PostgreSQL and Redis managed by the operator, and installs into the `default` namespace. For a dedicated namespace, see [Standard Installation](/enterprise/helm/installation/standard-install/).

## 1. Log In to the Helm Registry [#1-log-in-to-the-helm-registry]

Authenticate with the registry using your email and license ID:

```bash
read -rsp "License ID: " NBE_LICENSE_ID && echo
helm registry login registry.enterprise.netboxlabs.com \
  --username your-email@example.com \
  --password-stdin <<< "$NBE_LICENSE_ID"
unset NBE_LICENSE_ID
```

## 2. Install CRDs [#2-install-crds]

Install the three Custom Resource Definition charts before the operator:

```bash
helm install netbox-enterprise-crds \
  oci://registry.enterprise.netboxlabs.com/netbox-enterprise/stable-v2/netbox-enterprise-crds \
  --version 2.2.1

helm install netbox-enterprise-crds-pgo \
  oci://registry.enterprise.netboxlabs.com/netbox-enterprise/stable-v2/netbox-enterprise-crds-pgo \
  --version 2.2.1

helm install netbox-enterprise-crds-redis \
  oci://registry.enterprise.netboxlabs.com/netbox-enterprise/stable-v2/netbox-enterprise-crds-redis \
  --version 2.2.1
```

<Callout type="info" title="Using the bundled gateway?">
  These three CRD charts cover a default installation, which routes through your existing ingress controller. If you plan to enable the bundled Traefik gateway (`gateway.enabled: true`), install the Gateway API CRD charts as well. See [Gateway API CRDs](/enterprise/helm/installation/prerequisites/#gateway-api-crds-gateway-routing-only).
</Callout>

## 3. Install the Chart [#3-install-the-chart]

```bash
helm install netbox-enterprise \
  oci://registry.enterprise.netboxlabs.com/netbox-enterprise/stable-v2/netbox-enterprise \
  --version 2.2.1
```

## 4. Apply Configuration [#4-apply-configuration]

Apply a `NetBoxEnterprise` resource to configure the instance. Download the standard example manifest:

```bash
kubectl apply -f https://netboxlabs.com/docs/files/helm/examples/netbox-managed.yaml
```

This manifest deploys NetBox with one replica, internal PostgreSQL and Redis, and Diode enabled. See the [full examples index](/enterprise/helm/installation/examples/) for manifests covering external databases, SSO, object storage, custom plugins, and more.

## 5. Wait for Readiness [#5-wait-for-readiness]

Watch the operator deploy all components:

```bash
kubectl get pods
```

All pods should reach `Running` (or `Completed` for jobs) within a few minutes.

## 6. Access NetBox [#6-access-netbox]

Port-forward to the NetBox service:

```bash
kubectl port-forward svc/netbox-managed-netbox 8080:80
```

Open [http://localhost:8080](http://localhost:8080) in your browser.

## 7. Log In [#7-log-in]

The operator auto-generates a superuser account with the username `admin`. Retrieve the password from the generated secret:

```bash
kubectl get secret netbox-managed-netbox-superuser \
  -o jsonpath='{.data.password}' | base64 -d
```

Log in with `admin` and the password retrieved above.

## Next Steps [#next-steps]

* [Standard Installation](/enterprise/helm/installation/standard-install/) - Production-ready install with custom values, TLS, and resource tuning
* [Configuration](/enterprise/helm/configuration/helm-values) - Full Helm values reference
* [Architecture](/enterprise/helm/guides/architecture) - Understand the component topology