ServiceNow
ITSMBi-directional change records, CMDB reconciliation and approval routing.
- CMDB sync
- Change requests
- Approval routing
- Incident linkage
Infrapilot orchestrates your existing tooling rather than replacing it. Change records stay in ServiceNow, secrets stay in your vault, pipelines stay in your CI — and every one of them gains dependency awareness and an audit trail.
Certified means tested against each vendor’s supported versions on every release, with a named owner and a documented deprecation policy.
Bi-directional change records, CMDB reconciliation and approval routing.
Existing playbooks execute as workflow steps with full audit capture.
Plan, review and apply within governed change windows.
Subscription governance, resource lifecycle and Entra ID integration.
Account-level automation with Organizations and IAM role assumption.
Workflows, policies and runbooks versioned as code with pull-request review.
Problem events trigger automation; topology enriches the dependency graph.
Monitors initiate remediation and receive execution events in return.
Credentials brokered per execution — nothing stored by the platform.
Dynamic secrets issued at step start and revoked at step completion.
Bi-directional change records, CMDB reconciliation and approval routing.
Existing playbooks execute as workflow steps with full audit capture.
Plan, review and apply within governed change windows.
Signed script execution with brokered credentials and captured output.
Subscription governance, resource lifecycle and Entra ID integration.
Account-level automation with Organizations and IAM role assumption.
Project and folder governance with workload identity federation.
Workflows, policies and runbooks versioned as code with pull-request review.
Pipeline triggers and merge-request gating on infrastructure change.
Existing jobs invoked as governed steps inside a larger workflow.
Problem events trigger automation; topology enriches the dependency graph.
Monitors initiate remediation and receive execution events in return.
Alertmanager routes to workflows; PromQL informs health gates.
Execution metrics exposed as a datasource for your existing dashboards.
Inventory, snapshot orchestration and guest operations across clusters.
Group-based authorisation mapped to platform roles and approval chains.
Credentials brokered per execution — nothing stored by the platform.
Dynamic secrets issued at step start and revoked at step completion.
Connectors integrate with the systems around your estate. These are the technologies Infrapilot operates directly.
Relational, document, key-value, graph, search and warehouse engines under one lifecycle.
Current Windows and Linux distributions alongside the legacy Unix estates most tools skip.
Web tiers, application servers, message brokers, containers and virtualisation.
Consistent governance and lifecycle across every hyperscaler you operate in.
Generates and consumes the definitions your platform team already maintains.
Runs alongside existing tooling rather than demanding a rewrite.
Signals pulled in for correlation; findings pushed back out as events.
Change records, approvals and pipelines stay where your organisation already works.
Connectors are plugins built against a public SDK — the certified set is written with exactly the same interfaces available to you. A custom connector inherits credential brokering, retry semantics, audit capture and policy evaluation without implementing any of them.
import { defineConnector, type SyncContext } from '@infrapilot/sdk';
export default defineConnector({
id: 'acme-cmdb',
version: '1.4.0',
capabilities: ['inventory.read', 'ci.write'],
// Credentials are injected per execution and revoked on completion.
// The connector never sees a long-lived secret.
async sync(ctx: SyncContext) {
const page = await ctx.http.get('/api/v2/configuration-items', {
query: { updatedSince: ctx.cursor },
});
for (const item of page.items) {
await ctx.upsertAsset({
externalId: item.sys_id,
kind: item.ci_class,
attributes: item.attributes,
evidence: ctx.evidence('acme-cmdb', item.sys_id),
});
}
return { cursor: page.nextCursor };
},
});Connector requests from customers on an active agreement are prioritised in the quarterly roadmap, and we will confirm a target release before you sign.