Getting Started
Quick StartArchitecture
AI Agents
MSP HunterThreat ResearcherTech SupportCompliance AgentAccount ManagerOnboarding Agent
Compliance
HIPAASOC 2PCI-DSSNIST
Guides
First 30 DaysScalingClient OnboardingROI Calculation
API
OverviewAuthEndpointsWebhooks

Architecture Overview

🔧 Technical8 min readUpdated May 2026

System Overview

Gridlock is built as a multi-agent AI system where specialized agents work together to protect MSP client networks. Each agent is an independent unit with its own expertise, but they share intelligence and coordinate responses.

🌐 Network

Client endpoints

🔌 Connector

Lightweight agent

🧠 AI Engine

Z.AI GLM-5

🤖 Agents

6 specialists

📊 Dashboard

Real-time UI

Agent Pipeline

When data flows in from the network, it goes through a processing pipeline:

  1. Data Collection — The connector captures network traffic, system logs, endpoint data, and configuration snapshots
  2. Normalization — Raw data is parsed into a standardized format the agents can understand
  3. Routing — Data is routed to the appropriate agent based on type (network data → MSP Hunter, threat intel → Threat Researcher, etc.)
  4. AI Processing — Each agent uses Z.AI GLM-5 to analyze data, identify patterns, and make decisions
  5. Action — Agents take automated actions: block threats, generate tickets, update compliance scores, alert technicians

AI Provider

Gridlock uses Z.AI GLM-5 as its AI backbone. This gives us:

Data Flow & Security

🔒 Security First

All data is encrypted in transit (TLS 1.3) and at rest (AES-256). The connector never stores credentials. API keys are scoped to minimum required permissions.

Data flows through a secure pipeline:

  1. Encrypted collection from endpoints via the connector
  2. TLS-encrypted transmission to the Gridlock cloud
  3. Processing in isolated agent environments
  4. Results stored in encrypted databases
  5. Dashboard access via authenticated sessions

Multi-Tenant Architecture

Each MSP gets a fully isolated environment. Your clients' data never touches another MSP's data. This is achieved through: