Veltrix SecOps Documentation

Welcome to the Veltrix SecOps documentation. Veltrix is the Security-as-Code change control plane: every configuration change to your security tools flows through one governed pipeline — validated, human-approved, progressively deployed, health-checked, and watched for drift.

Platform Overview

Veltrix manages the configuration of your security tools — a catalog of 96 apps in the open app marketplace, from Splunk and Microsoft Sentinel to CrowdStrike Falcon and Microsoft Entra ID — the way modern teams manage application code: versioned, reviewed, and deployed with safety controls.

The Change Pipeline

  • Author — visual Configuration Canvas or REST API
  • Validate — app-defined checks reject bad configs early
  • Approve — named human reviewers sign off on field-level diffs
  • Deploy — direct, canary, blue-green, or rolling, with health checks
  • Drift-detect & Rollback — out-of-band changes flagged; failed deploys revert automatically

Platform Capabilities

  • Tag-based environments with per-environment approval and rollout policies
  • Role-based access control and single sign-on with scoped, revocable API keys
  • Nine zero-trust connectivity providers with encrypted credentials
  • Open-source app marketplace, SDK, and CLI for new integrations
  • Versioned history, audit trail, and compliance reporting

Quick Start Guide

Follow these steps to get from sign-up to your first governed deployment:

  1. Sign up for an account

    Visit app.veltrixsecops.com and create your tenant.

  2. Install an app from the marketplace

    Open the Apps page and install the integration for your tool — for example, Splunk Enterprise or Splunk Cloud.

  3. Register components and connectivity

    Add the components you manage (indexers, search heads, cloud stacks), store credentials, and assign a connectivity provider for self-managed hosts.

  4. Set environment policies

    Tag your environments (dev, staging, production) and define per-environment rules: required approvers, deployment strategy, canary steps, and auto-rollback thresholds.

  5. Author, approve, deploy

    Create your first Configuration Canvas, submit it for approval, and deploy it through the pipeline.

Building an integration?

Install the developer CLI with npm install -g @veltrixsecops/cli, then scaffold an app with veltrix init <app-id>. See Client & Developer Tooling.

Hosting & Deployment

Veltrix is delivered as hosted SaaS — there is nothing to install to get started. Enterprise customers on the Custom plan can discuss on-premises deployment options with our team.

Option Best for How to get it
Hosted SaaS (multi-tenant) Most teams — fastest start, managed upgrades and backups Sign up on Starter or Professional
On-premises / dedicated Enterprises with data-residency or isolation requirements Contact sales about the Custom plan

Note that your security tools stay where they are — Veltrix reaches self-managed components over your choice of nine zero-trust connectivity providers (Tailscale, SSH, WireGuard, Cloudflare Tunnel, ZeroTier, Nebula, OpenVPN, AWS SSM, HashiCorp Boundary), with credentials encrypted at rest.

Product Guide

Task-oriented guides to every area of the portal: what each feature does, where to find it, every setting, who can use it, and which plans include it.

Configuration Workflow

Apps & Integrations

Administration

Monitoring & MSSP

Build on Veltrix

Tool integrations are open-source apps. An app packages canvas templates and six pipeline handlers — validate, deploy, rollback, health-check, drift-detect, status — and inherits the platform's approval and safety machinery for free.

Automation & AI Agents

Everything in the UI is available through the REST API, authenticated with scoped, revocable API keys. That makes Veltrix the natural governance layer for AI-driven operations: agents propose changes through the API, and the pipeline's validation, human approval, progressive deployment, and drift detection apply automatically.

  • Issue each agent its own API key so every proposal is attributable
  • Keep production approval with named human reviewers via environment policies
  • Let canary steps, health checks, and auto-rollback contain anything that slips through
  • Use drift detection to catch any automation acting outside the pipeline