{"id":77100,"date":"2026-10-14T17:15:03","date_gmt":"2026-10-14T15:15:03","guid":{"rendered":"https:\/\/www.arcadsoftware.com\/arcad\/?p=77100"},"modified":"2026-10-14T17:15:03","modified_gmt":"2026-10-14T15:15:03","slug":"integrating-ai-into-ibm-i-devops-pipeline-without-losing-control","status":"publish","type":"post","link":"https:\/\/www.arcadsoftware.com\/arcad\/news-events\/blog\/integrating-ai-into-ibm-i-devops-pipeline-without-losing-control\/","title":{"rendered":"Integrating AI into your IBM i DevOps pipeline without losing control"},"content":{"rendered":"

Article written by Michel Mouchon on October 14, 2026<\/p>\n<\/div>

On IBM i, the real limit has never been computing power. It’s the ability to push change through safely, on a shared platform where a poorly controlled modification can be costly. Here is how to bring AI agents into the DevOps pipeline without giving up the guardrails that protect production.<\/p>\n<\/div><\/div><\/div><\/div><\/div>

The constraint isn’t compute capacity. It’s change capacity.<\/em><\/p>\n<\/div><\/div><\/div>

The real bottleneck<\/h2><\/div>

When people talk about applying AI to DevOps, the image that comes to mind is a developer who codes faster. That isn’t the story that really matters on IBM i.<\/p>\n

The real story begins when you move from the developer to the team, and then to the enterprise platform: that is where delivery holds or breaks. On an IBM i estate running hundreds of interconnected applications, across several countries and\/or teams, the constraint has never been compute capacity. It is change capacity: how many changes can you push into production without breaking anything?<\/p>\n

Many organizations have already taken a first step with coding assistants. It’s a good starting point: they cut the time to a first draft, explain existing code and speed up documentation. But while they optimize an individual developer’s productivity, what really slows down a production delivery stays the same: impact analysis, testing, building evidence for audit. In other words, everything that, in a regulated or high-availability environment, happens after the first draft of code.<\/p>\n<\/div>

What \u201closing control\u201d really means<\/h2><\/div>

IBM i is not a playground for black-box automation. It is a shared, highly context-dependent environment where RPG, COBOL and CL programs and DB2 components are linked by dependencies that only a handful of experts still fully master. And that handful shrinks with every generation.<\/p>\n

In this context, \u201closing control\u201d has a very concrete meaning: an agent that modifies code with no traceable justification; a change that lands in a test environment without anyone being able to say why; overly broad access granted for convenience; a segregation of duties that disappears because the same agent both proposes and executes.<\/p>\n

None of this is inevitable with AI itself. It is a direct consequence of the way AI is brought into the pipeline.<\/p>\n<\/div>

An agent that builds the case, not one that decides<\/h2><\/div>

The good news is that this problem isn’t new: it’s the problem of any high-privilege automation. The answer isn’t to remove controls to go faster, but to make them repeatable, visible and quick to run. In practice, for an IBM i change request, the flow looks like this:<\/p>\n<\/div>

<\/span><\/div>

The agent builds the case (analysis, proposal, evidence) but never goes through the gate alone. Human review remains the mandatory checkpoint before any promotion to a higher environment.<\/p>\n

The key point is not to remove controls, but to make them systematic: every step the agent produces is logged, every pull request carries its rationale and its risks, and promotion remains a human decision, backed by evidence that has already been gathered rather than reconstructed in a rush.<\/p>\n<\/div>

A maturity path, not a leap of faith<\/h2><\/div>

Because the IBM i environment is shared, adoption can’t be a gamble. It moves forward in stages, each one validated before moving on to the next.<\/p>\n<\/div><\/div><\/div>

\"Maturity<\/span><\/div>

Read<\/p>\n<\/div>

Dependency mapping, documentation, test recommendations. Almost no risk, immediate value: it’s the training ground for trust.<\/p>\n<\/div><\/div><\/div>

Recommend<\/p>\n<\/div>

The agent drafts a pull request but never merges it. The decision to merge stays human, every time.<\/p>\n<\/div><\/div><\/div>

Write with guardrails<\/p>\n<\/div>

Once trust is established, the agent can write in development or test, always behind pull requests and mandatory approvals.<\/p>\n<\/div><\/div><\/div><\/div><\/div><\/div>

Scope expansion always comes with stricter release gates, never the other way around. This progression delivers value early, without betting on the operational discipline that protects production.<\/p>\n<\/div>

Five non-negotiable guardrails<\/h2><\/div>

Once the path is set, governance itself must be designed like that of any high-privilege automation, not as a box to tick after the fact.<\/p>\n

    \n
  1. Identities and least privilege.<\/strong> Each agent, whether it acts on behalf of a human or autonomously, has its own identity and only the rights its task requires.<\/li>\n
  2. Human in the loop.<\/strong> Approvals and reviews remain mandatory, and this requirement is technically enforced in the pipeline: branch protections, control gates that cannot be bypassed.<\/li>\n
  3. Whitelist of MCP servers and tools.<\/strong> The Model Context Protocol connects agents to tools: it must be governed like any interface, by defining precisely what an agent can access, nothing more.<\/li>\n
  4. Systematic logging.<\/strong> Every tool or agent invocation is recorded, for audit as well as incident response.<\/li>\n
  5. A formalized AI governance model.<\/strong> Beyond technical controls, the organization must have settled who decides, who approves, and how far the authorized scope extends.<\/li>\n<\/ol>\n<\/div><\/div><\/div>

    In an agentic SDLC, governance isn’t a tax on speed. It’s what makes speed possible.<\/p>\n<\/div><\/div><\/div>

    How ARCAD builds this control into its architecture<\/h2><\/div>

    This is the principle that structures the ARCAD agentic platform: the agent reasons and plans, but a workflow engine, deterministic and logged, does the executing. No model improvisation on a sensitive action.<\/p>\n

    The architecture rests on three pillars. Knowledge (RAG)<\/strong> grounds the agent’s answers in more than thirty years of ARCAD methodology rather than in the model’s probabilities alone. Tools (MCP)<\/strong> expose the ARCAD DevOps stack (DROPS, the Metadata Repository, Builder) in a standardized form: around 80 DROPS REST endpoints are exposed as MCP tools, available to any MCP client, whether it’s the ARCAD agent, Copilot or Claude. Action (the workflow engine)<\/strong> runs ARCAD’s standard processes in a repeatable, auditable way, with sensitive steps still subject to human validation, exactly as today.<\/p>\n

    This choice has a deliberate corollary: AI is the assistant, not the engine. Results remain deterministic, not a probabilistic estimate. The source of truth remains the ARCAD repository rather than a model’s answer, and there is no runaway correction loop where the AI would endlessly try to fix its own output. Each organization chooses the steps where AI steps in; the product keeps working without it, and the cost, in tokens as well as in risk, remains predictable.<\/p>\n<\/div><\/div><\/div>

    Industrialize and secure your IBM i deliveries with a governed DevOps toolchain<\/p>\n<\/div><\/div><\/div>

    Discover ARCAD for DevOps<\/span>Discover ARCAD for DevOps<\/span><\/div><\/a><\/div><\/div><\/div><\/div><\/div><\/div>

    What this looks like in practice<\/h2><\/div>

    This kind of discipline holds up at scale. At Leumit Health Services, ARCAD Transformer Field<\/a> automated a field expansion project across the entire IBM i application estate, as part of an end-to-end DevOps process.<\/p>\n<\/div><\/div><\/div>

    14,000<\/p>\n<\/div>

    program sources scoped<\/p>\n<\/div><\/div><\/div>

    2,500<\/p>\n<\/div>

    sources automatically modified<\/p>\n<\/div><\/div><\/div>

    1 night<\/p>\n<\/div>

    overnight cutover, zero rollback<\/p>\n<\/div><\/div><\/div><\/div><\/div><\/div>

    \u201cThe item code expansion project here at Leumit was beyond critical. We could not afford to go wrong.\u201d<\/p>\n<\/div>

    Aviv Rosenwasser<\/strong>, Head of IBM i Development, Leumit Health Services<\/p>\n<\/div><\/div><\/div>

    Automate your field expansions across your entire IBM i estate<\/p>\n<\/div><\/div><\/div>

    Discover Transformer Field<\/span>Discover Transformer Field<\/span><\/div><\/a><\/div><\/div><\/div><\/div><\/div><\/div>

    Where to start: a 90-day plan<\/h2><\/div>

    The adoption that works follows a simple principle: start small, govern from day one, scale what works.<\/p>\n<\/div>

    Weeks 1\u20134<\/h3><\/div>

    One or two strictly read-only pilots, chosen for the pain points they remove right away: impact analysis, documentation, evidence gathering.<\/p>\n<\/div>

    Weeks 4\u20138<\/h3><\/div>

    Guardrails go in place in parallel: identities, control gates, evidence archiving, a tool whitelist with detailed logging.<\/p>\n<\/div>

    Weeks 8\u201312<\/h3><\/div>

    Forming mixed squads of IBM i and non-IBM i engineers, to widen the scope without concentrating risk on a handful of experts.<\/p>\n<\/div>

    Ongoing<\/h3><\/div>

    Blameless post-mortems and shared playbooks, so that every incident avoided benefits the next team.<\/p>\n<\/div><\/div><\/div>

    The goal isn’t to put AI everywhere. It’s to change faster, without ever changing blind.<\/p>\n<\/div><\/div><\/div>

    ARCAD Software – Content based on real-world experience and technical sessions from the ARCAD Summit.<\/em><\/p>\n<\/div><\/div><\/div>

    Bring AI into your IBM i DevOps pipeline!<\/p>\n<\/div><\/div><\/div>

    Contact us<\/span>Contact us<\/span><\/div><\/a><\/div><\/div><\/div><\/div><\/div><\/div><\/div><\/div>

    About the author<\/h2><\/div>
    <\/span><\/div><\/div><\/div>

    Michel Mouchon<\/h3><\/div>

    CTO & DevOps Business Line Manager<\/h4><\/div><\/div><\/div>

    CTO of ARCAD Software since 2000 and now Business Line Manager of the DevOps for Legacy brand, Michel Mouchon is responsible for defining ARCAD\u2019s overall technology strategy. A pioneer in areas such as DevSecOps and digital transformation, he drives innovation to support the company\u2019s growth. In this role, he plays a key part in coordinating the R&D, Engineering, and Pre-Sales departments.<\/p>\n

    Michel has developed broad, cross-disciplinary expertise in IT, beginning his career with a dual degree in Electronics and Software Engineering. His constant curiosity for emerging technologies \u2014 and how to apply them within the ARCAD and DevOps ecosystem \u2014 combined with his strong communication skills, has helped strengthen the ARCAD user community. He has also played a decisive role in highlighting new technologies, including today\u2019s advancements that leverage AI to transform access to products and application knowledge, while maximizing the added value of ARCAD solutions.<\/p>\n<\/div><\/div><\/div><\/div><\/div><\/div><\/div><\/div><\/p>\n","protected":false},"excerpt":{"rendered":"

    AI and DevOps on IBM i: how to integrate AI agents into your pipeline. Maturity path, guardrails and a 90-day plan.<\/p>\n","protected":false},"author":3,"featured_media":77096,"comment_status":"closed","ping_status":"closed","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[219],"tags":[616,371],"class_list":["post-77100","post","type-post","status-publish","format-standard","has-post-thumbnail","hentry","category-blog","tag-blog-en","tag-ibm-i-devops"],"yoast_head":"\nIntegrating AI into your IBM i DevOps pipeline without losing control<\/title>\n<meta name=\"description\" content=\"AI and DevOps on IBM i: how to integrate AI agents into your pipeline. Maturity path, guardrails and a 90-day plan.\" \/>\n<meta name=\"robots\" content=\"index, follow, max-snippet:-1, max-image-preview:large, max-video-preview:-1\" \/>\n<link rel=\"canonical\" href=\"https:\/\/www.arcadsoftware.com\/arcad\/news-events\/blog\/integrating-ai-into-ibm-i-devops-pipeline-without-losing-control\/\" \/>\n<meta property=\"og:locale\" content=\"en_US\" \/>\n<meta property=\"og:type\" content=\"article\" \/>\n<meta property=\"og:title\" content=\"Integrating AI into your IBM i DevOps pipeline without losing control\" \/>\n<meta property=\"og:description\" content=\"AI and DevOps on IBM i: how to integrate AI agents into your pipeline. Maturity path, guardrails and a 90-day plan.\" \/>\n<meta property=\"og:url\" content=\"https:\/\/www.arcadsoftware.com\/arcad\/news-events\/blog\/integrating-ai-into-ibm-i-devops-pipeline-without-losing-control\/\" \/>\n<meta property=\"og:site_name\" content=\"ARCAD\" \/>\n<meta property=\"article:publisher\" content=\"https:\/\/www.facebook.com\/pages\/Arcad-Software\/116086138469235\" \/>\n<meta property=\"article:published_time\" content=\"2026-10-14T15:15:03+00:00\" \/>\n<meta property=\"og:image\" content=\"https:\/\/www.arcadsoftware.com\/arcad\/wp-content\/uploads\/2026\/10\/integrating-ai-into-your-ibm-i-devops-pipeline-without-losing-control.png\" \/>\n\t<meta property=\"og:image:width\" content=\"800\" \/>\n\t<meta property=\"og:image:height\" content=\"298\" \/>\n\t<meta property=\"og:image:type\" content=\"image\/png\" \/>\n<meta name=\"author\" content=\"administrator\" \/>\n<meta name=\"twitter:label1\" content=\"Written by\" \/>\n\t<meta name=\"twitter:data1\" content=\"administrator\" \/>\n\t<meta name=\"twitter:label2\" content=\"Est. reading time\" \/>\n\t<meta name=\"twitter:data2\" content=\"7 minutes\" \/>\n<script type=\"application\/ld+json\" class=\"yoast-schema-graph\">{\"@context\":\"https:\\\/\\\/schema.org\",\"@graph\":[{\"@type\":\"Article\",\"@id\":\"https:\\\/\\\/www.arcadsoftware.com\\\/arcad\\\/news-events\\\/blog\\\/integrating-ai-into-ibm-i-devops-pipeline-without-losing-control\\\/#article\",\"isPartOf\":{\"@id\":\"https:\\\/\\\/www.arcadsoftware.com\\\/arcad\\\/news-events\\\/blog\\\/integrating-ai-into-ibm-i-devops-pipeline-without-losing-control\\\/\"},\"author\":{\"name\":\"administrator\",\"@id\":\"https:\\\/\\\/www.arcadsoftware.com\\\/arcad\\\/#\\\/schema\\\/person\\\/ac3c33678907c9c414148df7a202dfbf\"},\"headline\":\"Integrating AI into your IBM i DevOps pipeline without losing control\",\"datePublished\":\"2026-10-14T15:15:03+00:00\",\"mainEntityOfPage\":{\"@id\":\"https:\\\/\\\/www.arcadsoftware.com\\\/arcad\\\/news-events\\\/blog\\\/integrating-ai-into-ibm-i-devops-pipeline-without-losing-control\\\/\"},\"wordCount\":11018,\"publisher\":{\"@id\":\"https:\\\/\\\/www.arcadsoftware.com\\\/arcad\\\/#organization\"},\"image\":{\"@id\":\"https:\\\/\\\/www.arcadsoftware.com\\\/arcad\\\/news-events\\\/blog\\\/integrating-ai-into-ibm-i-devops-pipeline-without-losing-control\\\/#primaryimage\"},\"thumbnailUrl\":\"https:\\\/\\\/www.arcadsoftware.com\\\/arcad\\\/wp-content\\\/uploads\\\/2026\\\/10\\\/integrating-ai-into-your-ibm-i-devops-pipeline-without-losing-control.png\",\"keywords\":[\"blog\",\"DevOps for IBM i\"],\"articleSection\":[\"Blog\"],\"inLanguage\":\"en-US\"},{\"@type\":\"WebPage\",\"@id\":\"https:\\\/\\\/www.arcadsoftware.com\\\/arcad\\\/news-events\\\/blog\\\/integrating-ai-into-ibm-i-devops-pipeline-without-losing-control\\\/\",\"url\":\"https:\\\/\\\/www.arcadsoftware.com\\\/arcad\\\/news-events\\\/blog\\\/integrating-ai-into-ibm-i-devops-pipeline-without-losing-control\\\/\",\"name\":\"Integrating AI into your IBM i DevOps pipeline without losing control\",\"isPartOf\":{\"@id\":\"https:\\\/\\\/www.arcadsoftware.com\\\/arcad\\\/#website\"},\"primaryImageOfPage\":{\"@id\":\"https:\\\/\\\/www.arcadsoftware.com\\\/arcad\\\/news-events\\\/blog\\\/integrating-ai-into-ibm-i-devops-pipeline-without-losing-control\\\/#primaryimage\"},\"image\":{\"@id\":\"https:\\\/\\\/www.arcadsoftware.com\\\/arcad\\\/news-events\\\/blog\\\/integrating-ai-into-ibm-i-devops-pipeline-without-losing-control\\\/#primaryimage\"},\"thumbnailUrl\":\"https:\\\/\\\/www.arcadsoftware.com\\\/arcad\\\/wp-content\\\/uploads\\\/2026\\\/10\\\/integrating-ai-into-your-ibm-i-devops-pipeline-without-losing-control.png\",\"datePublished\":\"2026-10-14T15:15:03+00:00\",\"description\":\"AI and DevOps on IBM i: how to integrate AI agents into your pipeline. Maturity path, guardrails and a 90-day plan.\",\"breadcrumb\":{\"@id\":\"https:\\\/\\\/www.arcadsoftware.com\\\/arcad\\\/news-events\\\/blog\\\/integrating-ai-into-ibm-i-devops-pipeline-without-losing-control\\\/#breadcrumb\"},\"inLanguage\":\"en-US\",\"potentialAction\":[{\"@type\":\"ReadAction\",\"target\":[\"https:\\\/\\\/www.arcadsoftware.com\\\/arcad\\\/news-events\\\/blog\\\/integrating-ai-into-ibm-i-devops-pipeline-without-losing-control\\\/\"]}]},{\"@type\":\"ImageObject\",\"inLanguage\":\"en-US\",\"@id\":\"https:\\\/\\\/www.arcadsoftware.com\\\/arcad\\\/news-events\\\/blog\\\/integrating-ai-into-ibm-i-devops-pipeline-without-losing-control\\\/#primaryimage\",\"url\":\"https:\\\/\\\/www.arcadsoftware.com\\\/arcad\\\/wp-content\\\/uploads\\\/2026\\\/10\\\/integrating-ai-into-your-ibm-i-devops-pipeline-without-losing-control.png\",\"contentUrl\":\"https:\\\/\\\/www.arcadsoftware.com\\\/arcad\\\/wp-content\\\/uploads\\\/2026\\\/10\\\/integrating-ai-into-your-ibm-i-devops-pipeline-without-losing-control.png\",\"width\":800,\"height\":298,\"caption\":\"Integrating AI into Your IBM i DevOps Pipeline Without Losing Control\"},{\"@type\":\"BreadcrumbList\",\"@id\":\"https:\\\/\\\/www.arcadsoftware.com\\\/arcad\\\/news-events\\\/blog\\\/integrating-ai-into-ibm-i-devops-pipeline-without-losing-control\\\/#breadcrumb\",\"itemListElement\":[{\"@type\":\"ListItem\",\"position\":1,\"name\":\"ARCAD\",\"item\":\"https:\\\/\\\/www.arcadsoftware.com\\\/arcad\\\/\"},{\"@type\":\"ListItem\",\"position\":2,\"name\":\"Integrating AI into your IBM i DevOps pipeline without losing control\"}]},{\"@type\":\"WebSite\",\"@id\":\"https:\\\/\\\/www.arcadsoftware.com\\\/arcad\\\/#website\",\"url\":\"https:\\\/\\\/www.arcadsoftware.com\\\/arcad\\\/\",\"name\":\"ARCAD\",\"description\":\"Experts DevOps & Modernisation sur IBM i (alias AS\\\/400 ou AS400)\",\"publisher\":{\"@id\":\"https:\\\/\\\/www.arcadsoftware.com\\\/arcad\\\/#organization\"},\"potentialAction\":[{\"@type\":\"SearchAction\",\"target\":{\"@type\":\"EntryPoint\",\"urlTemplate\":\"https:\\\/\\\/www.arcadsoftware.com\\\/arcad\\\/?s={search_term_string}\"},\"query-input\":{\"@type\":\"PropertyValueSpecification\",\"valueRequired\":true,\"valueName\":\"search_term_string\"}}],\"inLanguage\":\"en-US\"},{\"@type\":\"Organization\",\"@id\":\"https:\\\/\\\/www.arcadsoftware.com\\\/arcad\\\/#organization\",\"name\":\"ARCAD Software\",\"url\":\"https:\\\/\\\/www.arcadsoftware.com\\\/arcad\\\/\",\"logo\":{\"@type\":\"ImageObject\",\"inLanguage\":\"en-US\",\"@id\":\"https:\\\/\\\/www.arcadsoftware.com\\\/arcad\\\/#\\\/schema\\\/logo\\\/image\\\/\",\"url\":\"https:\\\/\\\/www.arcadsoftware.com\\\/arcad\\\/wp-content\\\/uploads\\\/2017\\\/09\\\/arcad-group-logo-text-144.png\",\"contentUrl\":\"https:\\\/\\\/www.arcadsoftware.com\\\/arcad\\\/wp-content\\\/uploads\\\/2017\\\/09\\\/arcad-group-logo-text-144.png\",\"width\":144,\"height\":200,\"caption\":\"ARCAD Software\"},\"image\":{\"@id\":\"https:\\\/\\\/www.arcadsoftware.com\\\/arcad\\\/#\\\/schema\\\/logo\\\/image\\\/\"},\"sameAs\":[\"https:\\\/\\\/www.facebook.com\\\/pages\\\/Arcad-Software\\\/116086138469235\",\"https:\\\/\\\/x.com\\\/arcad_software\",\"https:\\\/\\\/www.linkedin.com\\\/company\\\/arcad-software\",\"https:\\\/\\\/www.youtube.com\\\/user\\\/ARCADSoftwareInc\"]},{\"@type\":\"Person\",\"@id\":\"https:\\\/\\\/www.arcadsoftware.com\\\/arcad\\\/#\\\/schema\\\/person\\\/ac3c33678907c9c414148df7a202dfbf\",\"name\":\"administrator\",\"url\":\"https:\\\/\\\/www.arcadsoftware.com\\\/arcad\\\/author\\\/administrator\\\/\"}]}<\/script>\n<!-- \/ Yoast SEO plugin. -->","yoast_head_json":{"title":"Integrating AI into your IBM i DevOps pipeline without losing control","description":"AI and DevOps on IBM i: how to integrate AI agents into your pipeline. Maturity path, guardrails and a 90-day plan.","robots":{"index":"index","follow":"follow","max-snippet":"max-snippet:-1","max-image-preview":"max-image-preview:large","max-video-preview":"max-video-preview:-1"},"canonical":"https:\/\/www.arcadsoftware.com\/arcad\/news-events\/blog\/integrating-ai-into-ibm-i-devops-pipeline-without-losing-control\/","og_locale":"en_US","og_type":"article","og_title":"Integrating AI into your IBM i DevOps pipeline without losing control","og_description":"AI and DevOps on IBM i: how to integrate AI agents into your pipeline. Maturity path, guardrails and a 90-day plan.","og_url":"https:\/\/www.arcadsoftware.com\/arcad\/news-events\/blog\/integrating-ai-into-ibm-i-devops-pipeline-without-losing-control\/","og_site_name":"ARCAD","article_publisher":"https:\/\/www.facebook.com\/pages\/Arcad-Software\/116086138469235","article_published_time":"2026-10-14T15:15:03+00:00","og_image":[{"width":800,"height":298,"url":"https:\/\/www.arcadsoftware.com\/arcad\/wp-content\/uploads\/2026\/10\/integrating-ai-into-your-ibm-i-devops-pipeline-without-losing-control.png","type":"image\/png"}],"author":"administrator","twitter_misc":{"Written by":"administrator","Est. reading time":"7 minutes"},"schema":{"@context":"https:\/\/schema.org","@graph":[{"@type":"Article","@id":"https:\/\/www.arcadsoftware.com\/arcad\/news-events\/blog\/integrating-ai-into-ibm-i-devops-pipeline-without-losing-control\/#article","isPartOf":{"@id":"https:\/\/www.arcadsoftware.com\/arcad\/news-events\/blog\/integrating-ai-into-ibm-i-devops-pipeline-without-losing-control\/"},"author":{"name":"administrator","@id":"https:\/\/www.arcadsoftware.com\/arcad\/#\/schema\/person\/ac3c33678907c9c414148df7a202dfbf"},"headline":"Integrating AI into your IBM i DevOps pipeline without losing control","datePublished":"2026-10-14T15:15:03+00:00","mainEntityOfPage":{"@id":"https:\/\/www.arcadsoftware.com\/arcad\/news-events\/blog\/integrating-ai-into-ibm-i-devops-pipeline-without-losing-control\/"},"wordCount":11018,"publisher":{"@id":"https:\/\/www.arcadsoftware.com\/arcad\/#organization"},"image":{"@id":"https:\/\/www.arcadsoftware.com\/arcad\/news-events\/blog\/integrating-ai-into-ibm-i-devops-pipeline-without-losing-control\/#primaryimage"},"thumbnailUrl":"https:\/\/www.arcadsoftware.com\/arcad\/wp-content\/uploads\/2026\/10\/integrating-ai-into-your-ibm-i-devops-pipeline-without-losing-control.png","keywords":["blog","DevOps for IBM i"],"articleSection":["Blog"],"inLanguage":"en-US"},{"@type":"WebPage","@id":"https:\/\/www.arcadsoftware.com\/arcad\/news-events\/blog\/integrating-ai-into-ibm-i-devops-pipeline-without-losing-control\/","url":"https:\/\/www.arcadsoftware.com\/arcad\/news-events\/blog\/integrating-ai-into-ibm-i-devops-pipeline-without-losing-control\/","name":"Integrating AI into your IBM i DevOps pipeline without losing control","isPartOf":{"@id":"https:\/\/www.arcadsoftware.com\/arcad\/#website"},"primaryImageOfPage":{"@id":"https:\/\/www.arcadsoftware.com\/arcad\/news-events\/blog\/integrating-ai-into-ibm-i-devops-pipeline-without-losing-control\/#primaryimage"},"image":{"@id":"https:\/\/www.arcadsoftware.com\/arcad\/news-events\/blog\/integrating-ai-into-ibm-i-devops-pipeline-without-losing-control\/#primaryimage"},"thumbnailUrl":"https:\/\/www.arcadsoftware.com\/arcad\/wp-content\/uploads\/2026\/10\/integrating-ai-into-your-ibm-i-devops-pipeline-without-losing-control.png","datePublished":"2026-10-14T15:15:03+00:00","description":"AI and DevOps on IBM i: how to integrate AI agents into your pipeline. Maturity path, guardrails and a 90-day plan.","breadcrumb":{"@id":"https:\/\/www.arcadsoftware.com\/arcad\/news-events\/blog\/integrating-ai-into-ibm-i-devops-pipeline-without-losing-control\/#breadcrumb"},"inLanguage":"en-US","potentialAction":[{"@type":"ReadAction","target":["https:\/\/www.arcadsoftware.com\/arcad\/news-events\/blog\/integrating-ai-into-ibm-i-devops-pipeline-without-losing-control\/"]}]},{"@type":"ImageObject","inLanguage":"en-US","@id":"https:\/\/www.arcadsoftware.com\/arcad\/news-events\/blog\/integrating-ai-into-ibm-i-devops-pipeline-without-losing-control\/#primaryimage","url":"https:\/\/www.arcadsoftware.com\/arcad\/wp-content\/uploads\/2026\/10\/integrating-ai-into-your-ibm-i-devops-pipeline-without-losing-control.png","contentUrl":"https:\/\/www.arcadsoftware.com\/arcad\/wp-content\/uploads\/2026\/10\/integrating-ai-into-your-ibm-i-devops-pipeline-without-losing-control.png","width":800,"height":298,"caption":"Integrating AI into Your IBM i DevOps Pipeline Without Losing Control"},{"@type":"BreadcrumbList","@id":"https:\/\/www.arcadsoftware.com\/arcad\/news-events\/blog\/integrating-ai-into-ibm-i-devops-pipeline-without-losing-control\/#breadcrumb","itemListElement":[{"@type":"ListItem","position":1,"name":"ARCAD","item":"https:\/\/www.arcadsoftware.com\/arcad\/"},{"@type":"ListItem","position":2,"name":"Integrating AI into your IBM i DevOps pipeline without losing control"}]},{"@type":"WebSite","@id":"https:\/\/www.arcadsoftware.com\/arcad\/#website","url":"https:\/\/www.arcadsoftware.com\/arcad\/","name":"ARCAD","description":"Experts DevOps & Modernisation sur IBM i (alias AS\/400 ou AS400)","publisher":{"@id":"https:\/\/www.arcadsoftware.com\/arcad\/#organization"},"potentialAction":[{"@type":"SearchAction","target":{"@type":"EntryPoint","urlTemplate":"https:\/\/www.arcadsoftware.com\/arcad\/?s={search_term_string}"},"query-input":{"@type":"PropertyValueSpecification","valueRequired":true,"valueName":"search_term_string"}}],"inLanguage":"en-US"},{"@type":"Organization","@id":"https:\/\/www.arcadsoftware.com\/arcad\/#organization","name":"ARCAD Software","url":"https:\/\/www.arcadsoftware.com\/arcad\/","logo":{"@type":"ImageObject","inLanguage":"en-US","@id":"https:\/\/www.arcadsoftware.com\/arcad\/#\/schema\/logo\/image\/","url":"https:\/\/www.arcadsoftware.com\/arcad\/wp-content\/uploads\/2017\/09\/arcad-group-logo-text-144.png","contentUrl":"https:\/\/www.arcadsoftware.com\/arcad\/wp-content\/uploads\/2017\/09\/arcad-group-logo-text-144.png","width":144,"height":200,"caption":"ARCAD Software"},"image":{"@id":"https:\/\/www.arcadsoftware.com\/arcad\/#\/schema\/logo\/image\/"},"sameAs":["https:\/\/www.facebook.com\/pages\/Arcad-Software\/116086138469235","https:\/\/x.com\/arcad_software","https:\/\/www.linkedin.com\/company\/arcad-software","https:\/\/www.youtube.com\/user\/ARCADSoftwareInc"]},{"@type":"Person","@id":"https:\/\/www.arcadsoftware.com\/arcad\/#\/schema\/person\/ac3c33678907c9c414148df7a202dfbf","name":"administrator","url":"https:\/\/www.arcadsoftware.com\/arcad\/author\/administrator\/"}]}},"_links":{"self":[{"href":"https:\/\/www.arcadsoftware.com\/arcad\/wp-json\/wp\/v2\/posts\/77100","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/www.arcadsoftware.com\/arcad\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/www.arcadsoftware.com\/arcad\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/www.arcadsoftware.com\/arcad\/wp-json\/wp\/v2\/users\/3"}],"replies":[{"embeddable":true,"href":"https:\/\/www.arcadsoftware.com\/arcad\/wp-json\/wp\/v2\/comments?post=77100"}],"version-history":[{"count":3,"href":"https:\/\/www.arcadsoftware.com\/arcad\/wp-json\/wp\/v2\/posts\/77100\/revisions"}],"predecessor-version":[{"id":77110,"href":"https:\/\/www.arcadsoftware.com\/arcad\/wp-json\/wp\/v2\/posts\/77100\/revisions\/77110"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/www.arcadsoftware.com\/arcad\/wp-json\/wp\/v2\/media\/77096"}],"wp:attachment":[{"href":"https:\/\/www.arcadsoftware.com\/arcad\/wp-json\/wp\/v2\/media?parent=77100"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/www.arcadsoftware.com\/arcad\/wp-json\/wp\/v2\/categories?post=77100"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/www.arcadsoftware.com\/arcad\/wp-json\/wp\/v2\/tags?post=77100"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}