Quick Start

Get the Dev SDK running on Kubernetes in about 10 minutes.

Generate your API key, then install VaultKey with the interactive installer or with Helm. Port-forward and health check are the same either way.

Step 1: Get your API key

Sign in to the Securelytix portal with your company email, generate your API key after email verification, then copy it immediately. The full key is shown only once.

Step 2: Install VaultKey

After you have your API key, choose one install path below.

Option A — Interactive installer (recommended)

Guides you through credentials, database config, and namespace setup interactively. Have your API key ready; the script will prompt for it.

bash · terminal
curl -fsSL https://charts.securelytix.tech/install.sh | bash

Or install manually with Helm if you want full control over each step (CI/CD, custom values, or existing pull secrets).

Option B — Manual Helm

Add the Helm repo

bash · terminal
1helm repo add securelytix https://charts.securelytix.tech
2helm repo update

Create the DockerHub pull secret

bash · terminal
1kubectl create secret docker-registry securelytix-dockerhub \
2 --docker-server=https://index.docker.io/v1/ \
3 --docker-username=securelytix2026 \
4 --docker-password=<YOUR_PAT_TOKEN>

macOS users

The imagePullSecrets argument must always be wrapped in double quotes. Unquoted square brackets cause a glob error in zsh.

Install with Helm

bash · terminal
1helm install vault-key securelytix/vault-key \
2 --set secrets.apiKey="<your-api-key>" \
3 --set postgresql.enabled=true \
4 --set machineId.hostPath="/etc/machine-id" \
5 --set "imagePullSecrets[0].name=securelytix-dockerhub"

Step 3: Port forwarding

After either install path finishes, forward the service locally:

bash · terminal
kubectl port-forward svc/vault-key-service 8080:8080 -n securelytix

Step 4: Verify

bash · terminal
1curl http://localhost:8080/health
2# Expected:
3{
4 "status": "ok",
5 "timestamp": "...",
6 "postgres": "ok"
7}

That's it

Your SDK is running. Jump to SDK Usage for code examples, API Reference for endpoints, or Health & Troubleshooting if anything went wrong.

Was this page helpful?