Security & governance

Controls on your MarkLogic estate

Pulse is built for teams who need day-2 insight without sending operational data to a SaaS APM. Role-based access, Audit Log, and Indexes Explorer give governance alongside the shared product experience.

Data stays on your estate

Pulse runs on your MarkLogic Server. Logs, metrics, saved views, and audit events live in Pulse databases you control. Observability is airgapped at runtime—no required cloud collector to see MarkLogic pressure.

Role-based access that maps to MarkLogic users

Pulse Roles grants Viewer, Operator, and Pulse Admin tiers—plus per-module roles—on existing MarkLogic users. Non-Pulse MarkLogic roles are preserved. Grant and revoke actions are auditable.

Viewer — developers and read-only support across ops modules
Operator — on-call engineers (filesystem logs, saved views, metrics admin)
Pulse Admin — platform owners (Setup, roles, audit, index scan, ingest diagnostics)

Audit Log for Pulse activity

Audit Log records page views, API calls, exports, Setup actions, Query Lens and Optic activity, and purges—with plain-language summaries, export (CSV / JSON / XML), and retention purge with dry-run preview.

Governance capabilities

Indexes Explorer for cleanup evidence
RBAC (tiers + per-module roles)
Audit Log with export and retention controls
Security pack and commercial support options

Explore the modules that implement these controls on theproduct page, or book a demo to walk them against your estate.

Next step

Talk through governance for your estate.

We can walk RBAC, audit retention, and airgapped observability against how you run MarkLogic today.

Book a demo Technical fit