Documentation

Zalanx Documentation

Set up Zalanx, connect your security stack, understand plan capabilities, and operate your workspace safely.

Current production documentation

Getting Started

Start with one security source and prove one useful workflow before expanding coverage.

  1. 1Create your workspace
  2. 2Choose one high-signal provider
  3. 3Connect and verify the provider
  4. 4Send supported telemetry
  5. 5Review monitoring activity
  6. 6Configure alerts and response policy where available

Available capabilities depend on plan, connected provider, permissions, and workspace policy.

Integrations

Connect the systems where your SaaS security signals already live.

Identity

  • ClerkFREE ELIGIBLE
  • Auth0FREE ELIGIBLE
  • OktaFREE ELIGIBLE
  • SupabaseFREE ELIGIBLE

Application

  • VercelSTARTER + PRO
  • SentryFREE ELIGIBLE

Observability

  • DatadogFREE ELIGIBLE

Payments

  • StripeFREE ELIGIBLE

Edge

  • CloudflareSTARTER + PRO

Cloud

  • AWS CloudTrailPRO
  • GCP Audit LogsPRO
  • Azure Monitor + Entra IDPRO

Custom

  • Custom WebhookPRO

Detailed provider setup instructions are being moved into the Zalanx documentation center.

Plans & Capabilities

FREE

Monitor

Autonomous monitoring with deterministic detection for one eligible security source.

  • Included: 1 workspace
  • Included: 1 user
  • Included: 1 eligible integration
  • Included: 10 email alerts/month
  • Included: No card required

Unavailable

  • Not included: model investigations
  • Not included: reports
  • Not included: suggestions
  • Not included: Slack
  • Not included: Safe Auto-Defense
  • Not included: Safe Autopilot
  • Not included: provider execution

STARTER

Investigate

Autonomous monitoring with incident analysis, suggested actions, reports, and Slack alerts.

  • Included: $19/month
  • Included: 7-day card-required trial
  • Included: 1 workspace
  • Included: 3 users
  • Included: 2 integrations
  • Included: incident analysis
  • Included: suggested actions
  • Included: reports
  • Included: email + Slack

Unavailable

  • Not included: Safe Autopilot
  • Not included: provider-side execution

PRO

Respond

Autonomous monitoring with Safe Auto-Defense, Safe Autopilot, advanced policy controls, and provider-supported response workflows.

  • Included: $199/month
  • Included: 7-day card-required trial
  • Included: 1 workspace
  • Included: 10 users
  • Included: 13 integrations
  • Included: Safe Auto-Defense
  • Included: Safe Autopilot
  • Included: advanced policy controls
  • Included: reports
  • Included: email + Slack
  • Included: Provider-side execution where supported.
See full pricing →

Security & Credential Safety

  • Use least-privilege provider credentials.
  • Never share API keys, tokens, signing secrets, service-account files, client secrets, or access keys in support messages, email, chat, or screenshots.
  • Use provider signing or shared-secret verification where supported.
  • Rotate credentials immediately if they may have been exposed.
  • Sensitive response actions remain subject to plan, provider capability, permissions, and workspace policy.
  • Rollback is available only where supported.
Security & Trust →

Troubleshooting

1. Integration not connected

Possible cause
Credentials, provider configuration, or endpoint mismatch.
Check
Reopen Integrations, verify the provider configuration, and run Test Connection where available.

2. No recent activity

Possible cause
No supported telemetry has arrived.
Check
Review provider event routing and the latest provider activity, then send a safe provider test event.

3. Invalid webhook or signature

Possible cause
The signing or shared secret is incorrect.
Check
Copy the secret from the exact provider endpoint configured for Zalanx. Never paste a secret into a support request.

4. Action skipped

Possible cause
Plan, policy, risk or confidence, target, provider capability, or Emergency Stop state.
Check
Review the Defense Actions reason and status alongside workspace policy. A skipped action does not always mean policy should be changed.

5. Wrong workspace

Possible cause
Endpoint, API-key, or workspace mismatch.
Check
Copy configuration from the intended Zalanx workspace.

Never send credentials or private keys when requesting support.

Need Help?

Need help choosing a starting provider or validating your first workflow?