Operate

With Grid Data App Manager
Every application, registered,
configured, and maintained — from one place.

When any Grid Data application starts, it registers itself with a single API call. The App Manager tracks its lifecycle, stores its configuration, and schedules the database housekeeping that keeps the whole estate fast.

1 API call
to join the estate
Live
registry dashboard
Per-table
retention policies
Cron
partition maintenance

The estate's memory

An inventory that maintains itself

Application inventories rot the day they are written. The App Manager’s doesn’t, because it isn’t written — it’s declared by the applications themselves, at startup, through a published registration pattern every family member follows. What you see is what is actually running.

One console answers the questions operators actually ask: what is deployed, where it lives, whether it is healthy, and when its database was last cleaned up.

Self-registration

Applications announce themselves on startup; operators see every deployment, its status, and its metadata — no manual inventory.

Live dashboard

Registry statistics and application health at a glance, with detail pages for overview, database, and metadata.

Central configuration

A key-value configuration store serves per-application settings through a consistent API.

Data retention policies

Per-application, per-table rules — frequency, retain window, advance, vacuum — edited in a simple grid.

Partition maintenance scheduling

Cron-based schedules run each application’s partition maintenance automatically, with last-run status visible.

Secure service-to-service

Keycloak-protected UI and APIs, with dedicated confidential clients for registering applications.

How it works

See it, end to end

every application registers itself on startup — one API call App Manager registry lifecycle · configuration · health Retention Cron schedules GDMP Grid Data Simulator Integration Suite Enhanced Analytics Reporting Testing Platform One console for the whole estate — and its housekeeping, scheduled rather than remembered. The registry at the centre: every family application checks in on startup, and housekeeping is scheduled, not remembered.
Step 1

An app starts

On first boot it POSTs its registration; business endpoints stay gated until the manager confirms.

Step 2

The manager confirms

A callback lifts the gate — no restart — and the app appears on the dashboard.

Step 3

Policies attach

Retention rules and partition-maintenance schedules are configured against the registered app.

Step 4

Housekeeping runs

The scheduler executes partition maintenance per app, on its cron, and records every run.

Use cases

Where Grid Data App Manager earns its keep

Estate visibility

One screen answering: what is deployed, where, and is it healthy.

Database housekeeping

Retention and partition maintenance across every application — scheduled instead of remembered.

Standardised onboarding

Every new application registers the same way; the pattern is a published implementation guide.

Under the hood

Technology

Current, supported, boring-on-purpose technology — the kind that stays deployable for years.

Angular 17
FastAPI / Python 3.12
PostgreSQL 16
Keycloak 24
APScheduler
Flyway
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 the applications that then register here.

Registers its retention and partition schedules here.

A registered citizen like every other member.

See Grid Data App Manager live

A working demonstration takes thirty minutes — on our environment or yours, with realistic simulated data.

Products

Contact

8100 Penn Ave S, suite 150j, Bloomington, MN – 55431

 +1 (763) 353-4363

Copyright © 2026 All Right Reserved PeriNimble