On February 2, 2025, Andrej Karpathy, the OpenAI co-founder and former Tesla AI director, posted a tweet describing how he'd been building software lately: "I just see stuff, say stuff, run stuff, and copy-paste stuff, and it mostly works." He called it vibe coding. Nine months later, Collins Dictionary named it the word of the year, beating out "aura farming" and a handful of other terms that had no business existing before 2025 either.

Karpathy was describing a personal, almost hobbyist way of building things: full trust in the model, minimal review of what it produced. That's a fine way to prototype an app for yourself over a weekend. It's a considerably worse way to build something a bank, a hospital, or a government agency is going to run production workflows on. Every enterprise software vendor watching the term take off had the same problem to solve: how do you keep the speed everyone suddenly wanted, without inheriting the technical debt, security gaps, and shadow IT sprawl that come with code nobody on a platform team ever looked at.

ServiceNow's answer was to build governance into the generation step itself, so an app inherits the platform's rules the moment it's created instead of picking them up later during a review. Whether that actually holds up, and what the rest of ServiceNow's app development stack looks like around it, is worth walking through in detail.

A gap between demand and developers that predates any of this

The pressure behind all of this predates AI, and it comes from something more structural: IDC has estimated that businesses would need to create 750 million new apps by 2025, against a projected shortage of roughly 4 million developers in that same window. Long before anyone was talking about vibe coding, organizations were already trying to close that gap with low-code and no-code platforms, tools that let people assemble applications visually instead of writing every line by hand.

What's changed is how fast that gap is now closing, at least on paper. GitHub's own developer survey found that 92% of U.S. app developers were already using AI coding tools, and Gartner has projected that 75% of enterprise software engineers will use AI coding assistants by 2028, up from less than 10% in early 2023. Gartner has also estimated that generative design AI could automate up to 60% of the design effort for new websites and mobile apps. These numbers describe how software gets built now, not some fringe practice at the edges of the industry, for better or worse depending on what happens to the output afterward.

What's in ServiceNow's app development stack today

The app development stack isn't a single product, it's a set of connected capabilities built for different kinds of builders and different stages of the same lifecycle, all sitting on top of App Engine, the platform where custom workflow applications actually run.

App Engine is the foundation. It's where apps get built, deployed, and governed, and it includes the full development, testing, and deployment infrastructure needed to take something from an idea to a production application. Everything else described here plugs into it.

Build Agent is the AI capability that generates the app itself. Describe what you need in natural language, and Build Agent produces the flows, UI, data model, and any AI agents the app needs, grounded in what already exists in your instance rather than starting from a blank slate. It ships as part of Now Assist for Creator and is available inside both the ServiceNow IDE and ServiceNow Studio.

ServiceNow Studio is the unified environment where professional developers and business technologists work, with Build Agent's assistance built in, cross-scope editing so people aren't context-switching between tools, and update set management for tracking and deploying changes safely.

Creator Studio serves a different builder entirely: someone with no coding background who needs a simple, request-based application and doesn't need the full IDE. It's a guided, no-code environment built around drag-and-drop forms, automations, and submission workflows, meant to take app creation from days down to minutes for straightforward use cases.

App Engine Management Center is the governance layer sitting above all of it. It gives platform teams one place to review app ideas before development starts, manage deployment pipelines, track who's building what, and enforce standards across every custom app in the portfolio, regardless of which tool built it.

Workflow Data Fabric feeds the whole stack with data. It connects information across systems without duplicating it, adds business context through a unified catalog, and applies governance so that whatever Build Agent generates, or whatever an agent inside a finished app decides to do, is grounded in data the platform trusts.

How Build Agent went from a lab feature to a governed enterprise capability

Build Agent has been through a few iterations before landing where it is now. ServiceNow introduced it as part of the Zurich platform release in September 2025, initially available inside the ServiceNow IDE and described plainly as an agentic developer available through chat, for building an app, writing documentation, or debugging code. At that point, it was still mostly a tool for people already working inside ServiceNow's own development environment.

Eight months later, at Knowledge 2026 in May, ServiceNow announced that Build Agent now works inside external AI coding tools directly, including Cursor, Windsurf, Claude Code, and GitHub Copilot, through something called the Build Agent SDK. It also works as an MCP client, pulling design specs and project context from tools like Figma, GitHub, and Miro straight into a build session. It's a distinction ServiceNow's own leadership has been explicit about.

"Vibe coding is transforming how fast people can build. But speed without governance and an enterprise runtime produce apps that too often look ready but aren't."

Jithin Bhasker, Group Vice President and General Manager of Creator Workflows and App Engine, ServiceNow

What backs that claim up is fairly concrete: anything built through the Build Agent SDK, regardless of which external tool initiated it, inherits ServiceNow's roles, access control lists, software development lifecycle policies, and audit trails automatically. A developer working in Cursor doesn't have to step outside platform standards to move fast, since that governance travels with the output. ServiceNow also made App Engine Management Center free to access alongside this release, specifically so every app gets reviewed against standards before deployment rather than after something breaks.

The shadow AI problem this is actually built to prevent

It's worth being specific about what "ungoverned" looks like in practice, because it's not hypothetical. Frost & Sullivan has found that roughly 70% of companies lack a cohesive strategy and roadmap for implementing AI at all, and a KPMG survey found that 45% of executives believe generative AI can actively harm trust in their organization if the right risk management tools aren't in place. Put an AI coding assistant in front of a workforce without a governed path for what it produces, and the likely outcome is a faster-growing pile of applications nobody in IT can see, each one a potential compliance gap or attack surface, not necessarily better software.

That's the real argument for wiring governance into the generation step rather than reviewing output after the fact. A quarterly access review or a security audit that discovers three years of shadow-built spreadsheet replacements is a very different starting position than one where every app, no matter who built it or in what tool, already carries the platform's access controls and change history because that's how it was generated.

Three ways to build, one governed outcome

ServiceNow's app development stack is deliberately built around more than one kind of builder, and the specific capabilities inside Now Assist for Creator show what that actually looks like day to day. Flow generation gives flow authors a starting skeleton from a plain-language description. Code generation turns natural-language comments into working code or flow suggestions, with intelligent completion as someone starts typing. Playbook generation produces a full workflow playbook outline from a description or an uploaded image of a process, instead of hours of manual configuration. Service catalog item generation writes the professional descriptions and questions for a new catalog item from a short description of what it should do. Conversational app generation lets someone build a foundational custom application by describing their process in a chat interface, no prior ServiceNow experience required.

Layered on top, Build Agent extends this into full application generation, including the AI agents that run inside the finished app, and can generate Automated Test Framework coverage in the same session, with plain-language explanations when something fails instead of a stack trace. It also generates release notes and update set descriptions from the metadata of what actually changed, closing the loop between building something and documenting it.

That range matters because the person best positioned to build a given app changes depending on the problem. A business analyst automating a request form belongs in Creator Studio. A developer extending ITSM or CSM with new logic belongs in Studio with Build Agent. A platform team member connecting an external tool to pull in a Figma spec belongs on the Build Agent SDK. None of them should have to leave ServiceNow's governance behind to get their work done quickly.

What this looks like in customer deployments

The platform's underlying architecture is what ServiceNow leadership points to as the reason these results hold up across such different use cases.

"Everything we do at ServiceNow is derived from this single platform, single data model, and single architecture. It's our differentiator, and it's incredibly powerful for our customers and their productivity."

Jon Sigler, Executive Vice President and General Manager, AI Platform, ServiceNow

Syslabo cut onboarding time in half using citizen development with AI agents. Danone automated processes and saved 14,000 hours in the process. Hitachi Vantara reported a 20% boost in development output; Ajay Vuppala, who manages the ServiceNow AI Platform there, said the platform "makes it easy to integrate with other systems, ensuring data security and seamless processes." Mindsprint cut process time by 22%, with Sriram Gopalakrishnan, President and Head of Technology Services and Delivery, noting that "processes that once took days now take minutes." Siemens GBS automated more than a million hours of work through the platform.

Independent case studies from ServiceNow's own low-code research point in the same direction. A global manufacturing company using App Engine Studio and App Engine Management Center tripled its development capacity, saved more than 4,600 hours through workflow automation, and added over 30 citizen developers, with 90% of code reviews passing on the first attempt. A U.S. healthcare provider automating manual processes like flu vaccination tracking increased development capacity by 40% and had citizen developers build 84 new workflows. A commerce company converted more than 140 apps off legacy technology while keeping collaboration safe from sprawl. An aerospace manufacturer replaced a spreadsheet-and-email process for managing more than 3,000 apps, cutting cycle time by 70% and saving an estimated $8.4 million a year.

TRIMEDX, a healthcare technology company, used Now Assist for Creator to speed up work order summarization and knowledge article generation for its technicians. The math behind that use case is straightforward once you see it laid out.

"If we can shave two to five minutes off each of our 2.5 million annual work orders, you're talking hundreds of thousands of hours saved."

Brad Jobe, CIO, TRIMEDX

TRIMEDX reported a 22% increase in developer productivity, and half its developers were actively using Now Assist within three months of rollout.

Where the analysts land on this

ServiceNow has been named a Leader in Gartner's Magic Quadrant for Enterprise Low-Code Application Platforms for six consecutive years, most recently in the July 2025 report, alongside Microsoft, Salesforce, Appian, Mendix, and OutSystems as the only other vendors in the Leaders quadrant. More specific to what's covered here, ServiceNow ranked first in the companion 2025 Gartner Critical Capabilities for Enterprise Low-Code Application Platforms report for the "Building and Managing AI Agents" use case specifically, which is a narrower and arguably more relevant distinction given how much of the current roadmap is agent generation rather than plain workflow automation.

FAQs

What is vibe coding, in ServiceNow's version of it? It's building an application by describing what you want in plain language and letting AI handle the implementation, the code, configuration, workflows, and UI. ServiceNow's version through Build Agent keeps the platform's governance, security policies, and instance context applied automatically, rather than leaving that to a manual review after the fact.

How is vibe coding different from low code? Low code replaces hand-coding with visual assembly, drag-and-drop components, and configuration screens. Vibe coding goes a step further: instead of assembling the pieces yourself, you describe the outcome and AI handles the assembly. The low-code foundation, and the governance built into it, is still there underneath either way.

Can I use Cursor or Claude Code to build ServiceNow apps? Yes. Both connect to Build Agent through the Build Agent SDK and inherit ServiceNow's governance policies, access controls, and audit trails automatically. Build Agent also works as an MCP client, so it can pull context from tools like Figma, GitHub, and Miro directly into a build session.

What's the difference between Creator Studio, ServiceNow Studio, and App Engine? App Engine is the overall platform where custom applications are built, deployed, and governed. ServiceNow Studio is the unified development environment for pro developers and business technologists, with Build Agent built in. Creator Studio is a simpler, no-code environment for citizen developers building request-based apps without needing the full IDE.

Do citizen developer apps built in Creator Studio bypass IT governance? No. Apps built through Creator Studio are still subject to the same review and deployment controls available through App Engine Management Center. The point of a governed no-code environment is to expand who can build safely, not to create an ungoverned side channel.

Is App Engine Management Center a separate purchase? It's available as part of App Engine, and ServiceNow made access to it free alongside the May 2026 Build Agent expansion specifically to reduce friction around governing apps before deployment. Licensing details are still worth confirming directly with ServiceNow or a partner during procurement, since packaging changes over time.