Shared infrastructure
Postgres, Keycloak, and Kafka per environment, provisioned for each application by its own install hooks — one credential surface instead of one per product.
Foundation
Grid Data Platform Manager The platform the family runs on.
Grid Data Platform Manager (GDPM) hosts the shared infrastructure every family application stands on — PostgreSQL, Keycloak, and Kafka — so a sign-in to one application is honored by the rest. Every application registers with it and serves nothing until approved; GDPM then tracks it, holds its configuration, delivers its notifications, and keeps its database fast.
One sign-on
across the family
Gated
registration and approval
Email · SMS · webhook
notification delivery
Scheduled
retention and partitions
The foundation
Shared infrastructure, one credential surface
Instead of every product bringing its own database, identity server, and message broker, the Platform Manager hosts them once per environment: one PostgreSQL with a database per application, one Keycloak realm with a client per application, and the Kafka backbone. Each application is provisioned by its own install hooks — one credential surface instead of one per product.
On that foundation sit the registry, the registration gate, the Notification Hub, and the housekeeping that keeps every database fast.
Single sign-on
One realm with a client per application: sign in once and move across the family without signing in again.
Registration gate
Applications register on startup and refuse requests until approved; approval opens them at once, rejection closes them again.
Notification Hub
Applications publish events to one Kafka topic or over HTTP; GDPM delivers them by email, SMS, or webhook — Slack and Teams included — with severity thresholds, templates, and an audit of every attempt.
Registry & dashboard
Every deployed application with its status, health, database, metadata, and configuration at a glance.
Retention & partitions
Per-table retention rules and cron-scheduled partition maintenance for every application, with last-run status — protected by point-in-time backups.
How it works
See it, end to end
Step 1
Provisioned
An application's install hooks create its database in the shared PostgreSQL and its client in the shared Keycloak realm.
Step 2
Registered
On startup it registers with the Platform Manager and refuses requests until an operator approves it.
Step 3
Approved
Approval opens it at once — no restart — and it joins the registry and dashboard; rejection closes it again.
Step 4
Looked after
Its events become notifications on the right channel, and retention and partition maintenance run on schedule.
Use cases
Where Grid Data Platform Manager earns its keep
Estate visibility
One screen: what is deployed, where, and whether it is healthy.
Alerting without plumbing
A product raises an event; the right people hear about it on the right channel.
Single sign-on across products
Users sign in once and move between Grid Data applications without signing in again.
Database housekeeping
Retention and partitions, scheduled instead of remembered.
Under the hood
Technology
Current, supported, boring-on-purpose technology — the kind that stays deployable for years.
Angular
FastAPI / Python
PostgreSQL
Keycloak
Apache Kafka
APScheduler
Jinja templates
Flyway
pgBackRest
Helm / Docker Compose
Better together
Part of the Grid Data Family
Every family application shares one identity platform, one design system, one registration pattern, and one deployment path.
Deploys applications onto the infrastructure the Platform Manager hosts, and protects their databases.
Registers here and shares its sign-on, database server, and Kafka backbone.
Runs as a managed application on the shared Postgres, Keycloak, Kafka, and Redis.
See Grid Data Platform Manager live
A working demonstration takes thirty minutes — on our environment or yours, with realistic simulated data.
Connect With Us