29 modules on one inventory
Each module solves a specific problem and each has its own page. They share one model of your estate, which is what makes adding the second one cheap.
What modules does DevOpsArk provide?
DevOpsArk provides 29 modules across Build, Deploy, Operate, Secure, Infrastructure and AI, all sharing one inventory of your estate.
ArkBuilder
AI-powered build and containerization
Containerization
Automated containerization for any application
Pipelines
CI/CD pipelines with policy and provenance
ArkApps
Application inventory and lifecycle
ArkCD
Continuous delivery and progressive rollout
Kubernetes
Multi-cluster Kubernetes management
Agentless Kubernetes
Manage clusters without installing anything
DMK8S
DevOpsArk managed Kubernetes
Release Management
Coordinated releases across services
Monitoring
Infrastructure and application monitoring
Alerting
Alerts that are worth waking up for
Observability
Metrics, logs and traces in one plane
Log Management
Centralised logs with structure and retention
Backups
Backups with restores that are actually tested
Cost Management
Cloud and Kubernetes cost attribution
Security
Posture, policy and continuous verification
Scanners
Image, code, IaC and secret scanning
Vulnerability Management
From finding to fix, with ownership
Secrets
Centralised secrets with rotation
IAM
Access, roles and approvals
SSL Management
Certificates that renew before they expire
Servers
Fleet inventory, patching and access
DNS Management
Records, zones and change safety
CaaS
Containers as a service
FaaS
Functions as a service
ArkChat
Ask Ark about your own infrastructure
AI Log Analysis
Find the line that matters
Anomaly Detection
Detection without hand-written thresholds
360 DITE
Delivery, infrastructure, testing and experience in one score
Come at it from the outcome instead
Questions about modules
DevOpsArk provides 29 modules across Build, Deploy, Operate, Secure, Infrastructure and AI, all sharing one inventory of your estate.
No. Modules are adopted individually and most teams start with cluster inventory, monitoring and security posture, all of which work with read-only access. Adding a module later is configuration rather than integration, because the inventory already exists.
Pricing is based on the scale of the estate under management rather than on a per-module licence, so adding a module does not add a line item. See the pricing page for detail.
A module is a DevOpsArk capability, such as vulnerability management or continuous delivery. An integration is a connection to a third-party system, such as AWS or GitHub, that modules read from and write to.
Usually Kubernetes and monitoring, because they deliver an inventory and a health picture within minutes of connecting a cluster read-only, without requiring any decision about write access.
Which modules do you actually need?
Tell us what is currently painful and we will say which modules address it, including when the answer is none of them.