Disclaimer

Open Source Software

Ark is open-source software under active development. The agentic AI space is evolving rapidly, and Ark evolves with it — expect frequent updates, new features, and breaking changes between releases. The software is provided “as is” without warranties of any kind.

API Stability and Migration

Ark does not yet provide a stable API, and breaking changes may occur between releases. Follow the upgrading guide for migration steps. Since Ark functions primarily as an operational layer, the recommended approach is to define your resources declaratively in YAML files or store configuration data in your application layer database, decoupled from Ark itself. This enables you to recreate resources in Ark as needed, allowing the system to reconcile them without data migration concerns.

Security

Ark is architected to support enterprise-grade security through layered controls that can be implemented above and below the core runtime. The out-of-the-box configuration prioritizes developer experience and ease of evaluation, with security layers intentionally left unconfigured to allow organizations to implement their specific security requirements.


┌─────────────────────────────────────┐
│     Enterprise Security Layer       │  ← Authentication, Authorization,
├─────────────────────────────────────┤    Network Policies, Secrets Mgmt, etc
│         Ark Runtime Core            │  ← Agent orchestration, Model mgmt
├─────────────────────────────────────┤    Query execution, Memory storage
│    Infrastructure Security Layer    │  ← Cluster hardening, Node security,
└─────────────────────────────────────┘    Compliance controls, Monitoring, etc

The default configuration includes:

Open cluster access for rapid prototyping and demonstration
Simplified service-to-service communication for development workflows
Standard Kubernetes RBAC that can be restricted as needed
Extensible authentication and authorization integration points
Configurable network policies and service mesh integration
Pluggable secrets management and encryption capabilities

Ark’s design philosophy enables organizations to implement their required security posture through standard Kubernetes security primitives, enterprise identity providers, network security controls, and compliance frameworks. Ark provides the necessary extension points and configuration options to support defense-in-depth strategies without prescribing specific security implementations that may conflict with existing organizational standards.

Security-Conscious Design

Ark’s architecture and design decisions prioritize compatibility with Kubernetes enterprise security practices. Rather than implementing proprietary security mechanisms, all components are designed to work seamlessly with existing Kubernetes security primitives, enterprise identity systems, and network security controls. This approach ensures that organizations can apply their established security policies and tooling without architectural conflicts or security gaps introduced by Ark itself.

Third Party Vendors, Services and Products

Any reference to third-party vendors, services, or products is provided for informational purposes only and does not constitute an endorsement, recommendation, or approval by McKinsey & Company. Inclusion of such references does not imply any affiliation or partnership, and McKinsey & Company makes no representations or warranties regarding the quality, reliability, or suitability of any third-party offerings mentioned.