SchemaPulse
PricingContact

Platform · Architecture

How it is built, and where each piece runs.

SchemaPulse is self-hosted software, not a service you send telemetry to. This page describes the actual deployment shape, including every path that crosses your network boundary.

View SecuritySecurity
SchemaPulse deployment architectureGo agents on each database host report to the SchemaPulse control plane, which stores metadata in PostgreSQL and time series in InfluxDB. All of that sits inside the customer's own network boundary. Two paths cross that boundary: mandatory licence verification, and any integrations or notification channels the customer enables.YOUR INFRASTRUCTUREDATABASE HOSTSMySQL · Galerago-agentMongoDB · RSgo-agentPostgreSQLgo-agentmetricsControl planeLaravel + ReactcontainerPostgreSQLInfluxDBmetadata + time seriesstay inside the boundaryLicence servermandatoryJira · PagerDutyonly if enabled
Fig. 1Agents, control plane and both datastores sit inside your infrastructure. Two paths cross the boundary: mandatory licence verification, and any integrations or notification channels you enable.

Outbound paths are described precisely on the Security page, including what each carries.

Components

Six pieces

Agent
A Go agent on each database host with a signed, verified identity and its own configuration. Install and cleanup scripts are served by the control plane.
Control plane
A Laravel API and a React console, shipped together as a single container image. This is the only component that needs to be reachable by operators.
Metadata
PostgreSQL holds configuration, policies, incidents, inventory, backup catalogue and audit history.
Time series
InfluxDB holds metrics at collection resolution, with retention you configure.
Provisioning
Terraform for infrastructure and Ansible for configuration, driven from the control plane with state held alongside it.
Tenancy
Organisation and project scoping throughout, with roles of Admin, Editor, Viewer and Read-only.

Deployment

What running it actually involves

One container for the control plane

The API, console and scheduling run from a single image. Upgrades are an image change, and rollback is the previous tag.

One agent per database host

Installed during provisioning, or added to existing hosts with a single command served by the control plane.

Licensed per node

Node-locked licence keys with activation, rebind and release, so replacing hardware does not mean replacing a licence.

Where to look next