Platforms & modules

Platforms are modular capabilities configured per engagement. Modules share identity, audit logging, and export policy services. We do not list anonymous SKU codes on this website because configurations reflect your environment and assurance requirements.

Shared platform services

Single sign-on integrates with your identity provider. Audit logs capture authentication, administration, export attempts, and configuration changes.

Notification service routes email and webhook alerts with throttling to prevent storms during incidents.

Intelligence modules

Ingestion bus, schema registry, entity store, correlation engine, analyst workspace, briefing builder, export governance.

Security and risk modules

Risk register, control library, test scheduler, incident cases, playbook runner, heat maps, committee exports.

Investment modules

Pipeline stages, diligence rooms, data reconciliation, pack templates, limits monitor, archive search.

Governance modules

Policy library, authority engine, meeting manager, action tracker, entity register.

Integration layer

API gateway with rate limits, API keys rotated on schedule, OpenAPI specifications per release.

Deployment artefacts

Infrastructure-as-code templates, monitoring dashboards, backup procedures, and upgrade runbooks delivered each phase.

Licensing

Metrics may include named users, entities, data volume tiers, or modules enabled—defined in your statement of work.

Roadmap interaction

Enhancement requests pass through impact review; we do not promise public roadmap dates on this marketing site.

Upgrade path

Version upgrades ship with migration scripts and rollback plans tested in staging.

Sandbox

Partners and clients receive sandboxes with synthetic data for integration development.

API lifecycle

Deprecated endpoints remain for two releases with sunset notices in release notes.

Performance SLOs

Platform SLOs for API availability documented separately from client application SLOs.

Identity as platform spine

All modules consume the same directory groups and attribute sources. Attribute changes propagate within minutes, not overnight batch jobs.

Service accounts are catalogued with owners and rotation schedules.

Observability for administrators

Administrators receive dashboards for failed jobs, integration errors, and certificate expiry—not only end-user feature metrics.

Module composition

Clients license combinations: intelligence without investment, governance with security, etc. Shared services mean identity and logging are configured once; modules inherit policies.

Disabled modules leave no attack surface in UI but remain absent from navigation—not merely hidden by CSS.

Release compatibility

Semantic versioning applies to APIs. Deprecation notices span two releases with migration guides.

Database migrations run in transactions with rollback scripts tested in staging clones.

Next steps

Email connect@intelligenceholdco.com or use Request a proposal for a scoped discussion.

Include deployment constraints, user counts, integration inventory, and assurance timelines with your enquiry.