Guardivia

Platform architecture

Four planes, one design language

Every Guardivia product separates protocol termination, processing, application gateways and management so each layer scales and fails over independently.

Signaling plane

Terminates SS7/MAP over SIGTRAN, SIP toward IMS, Diameter toward 4G/5G peers. Redundant associations per node.

Processing plane

Message stores, routing engines, rule and policy engines, classifiers, validation engines, profiling and detection models.

Gateway plane

SMPP and SMPPS servers, HTTP/REST APIs, webhooks, device telemetry channels and partner APIs.

Management plane

Web consoles, REST provisioning, monitoring exports (SNMP, syslog, SIEM), reports, audit and configuration-change logs.

Interconnection

How the products connect

Guardivia components in colour; external systems in grey. Each product page carries its own detailed diagram.

Guardivia platform overview: signaling, messaging, security and route assuranceA labelled architecture diagram showing systems, product boundaries and directional data flows. A detailed text description follows the figure.Partner networksSS7 · DiameterAggregatorsSMPPEnterprisesHTTP · SMPPVoice CDRsSIP · CDRSMS Signaling & ESME Gateway FirewallHawk · Dolphin · Sharkinspect · classify · monetizeOperator SMSCMAP · SMPP · IMSCore Network SuiteHLR/HSS · STP · CAMELEnterprise SMPP Gatewaymulti-tenant routingFlashCall & Voice Frauddetection · scoringHoneypot SMS Testing: real devices verify every routeSubscribersverified deliveryBSS · NOC · SIEMCDR · alarms · reportsQoS Engineering Teamin-house · SLA-backed
Text description

Partner networks (SS7, Diameter), aggregators (SMPP) and enterprises (HTTP, SMPP) enter through the SMS Signaling and ESME Gateway Firewall, which sits in front of the Operator SMSC and the Core Network Suite. The Enterprise SMPP Gateway fronts application customers. Voice CDRs feed the FlashCall and Voice Fraud Solution. Honeypot SMS Testing verifies delivery at real devices. Outputs reach subscribers, BSS/NOC/SIEM systems and the QoS Engineering Team that operates and supports the platforms.

Inline security

The Firewall’s Hawk engine sits between the STP and the SMSC; Dolphin and Shark sit in front of ESME binds. Allowed traffic proceeds to the Operator SMSC or a third-party SMSC.

Evidence loop

Honeypot findings become firewall indicators only after human confirmation; firewall decisions and gateway CDRs are imported back into route verdicts.

Design principles

Applied across the portfolio

  • Software-only stacks on Linux; no proprietary signaling hardware
  • Independent scaling of signaling, processing and gateway layers
  • Explicit integration tiers and documented interfaces
  • Monitoring mode before enforcement for every security product
  • Per-message CDRs and audit logs as first-class outputs
  • Human confirmation for AI-proposed enforcement
  • Product boundaries preserved: SMSC, Core Suite, Firewall, Gateway, FlashCall, Honeypot
  • One engineering team, one release process

Detailed diagrams: Operator SMSC, Core Network Suite, SMS Firewall, Enterprise SMPP Gateway, FlashCall, Honeypot Testing.

See it running on your traffic profile.

Talk to the engineers who build the platform. Demos use your protocols, your integration points and your policy questions.