ServiceNow App Engine licensing, explained. Tiers, user types and the custom table allowance.

App Engine licenses the custom apps you build on the Now Platform. It is quoted per user per year in two tiers and limited by a custom table allowance, and most overspend comes from the tier, the user mix and unmonitored tables.

What does ServiceNow App Engine license, and what does it leave out?

App Engine is the subscription for custom build on the Now Platform: the workflow apps, forms, tables and automations your own teams create. It does not cover ITSM, HRSD or CSM work, and it cannot stand in for those products.

The boundary matters because the platform makes it easy to cross. A custom app that assigns incidents or reads HR cases falls under process product licensing, whatever the app is called.

What the order form fixes

App Engine is sold under the Master Subscription Agreement. The order form names three things, and each is open to negotiation:

Term defaults follow the platform contract. Now Assist for App Engine, the generative build assistant, is included in eligible packaging in the current AI tiers, with no separate purchase. ServiceNow's price page now lists these features under the ServiceNow Otto name: Otto for Creator in Foundation and Otto for App Engine in Prime.

An order form signed before the 2026 repackaging carries older SKU names. Map each one to Foundation or Prime before you compare a renewal quote with what you own, using our Foundation, Advanced and Prime comparison.

How do App Engine Foundation and Prime differ, and is Prime worth the premium?

For most portfolios Prime does not earn its premium, because Foundation carries the low code build tools departmental apps need. Prime adds Otto for App Engine, Management Center and Process Mining, and lifts the caps on tables and scoped apps.

In the quotes we reviewed, Prime cost 30 to 50 percent more than the lower tier for the same user counts.

In practice the lower tier runs the workflow builder, forms, catalogs, approvals and integrations through standard connectors. Prime adds richer automation constructs, broader process scope and room for complex cross functional applications.

The tier should follow an inventory of what runs in production, and it rarely does. In 6 of every 10 renewals we reviewed, the upper tier had been sold against approval routers, request trackers and departmental forms that never touch an upper tier feature. The premium was paid every year and compounded under the uplift.

Why we advise against buying Prime to cover the roadmap

Account teams, and some implementation partners, recommend buying the top tier now so future apps are covered. We disagree. Moving up mid term is easy, and ServiceNow will sell you the upgrade the day a real Prime workload ships. Moving back down at renewal is a fight, so only one of the two mistakes is recoverable.

Buy the tier for the portfolio you have, not the portfolio the roadmap promises.

When Prime is the right answer

• Table or app count. After clean up, your App Engine tables or scoped apps still exceed the Foundation caps and keep growing.
• A funded feature need. A live or funded workload depends on Mobile Publishing, Process Mining or Management Center governance for a large citizen developer program.

If neither applies, sign Foundation with a written price for a mid term upgrade.

How should you split App Engine users between Creator, Builder and User?

Put almost everyone on User, a smaller group on Builder, and only working developers on Creator. The three types are priced very differently, and the mix is where quotes carry most of their padding.

• Creator. The full development tier, for professional developers building scoped applications. Above roughly 5 percent of the licensed population, the mix points to over licensing.
• Builder. The citizen developer tier, for people configuring flows and forms inside guardrails.
• User. The consumption tier, for everyone who opens, submits and works within finished apps.

In our reviews, loose user typing cost 20 to 35 percent against a mix based on behavior. Usually the first quote placed large groups in a higher type by default, and no one revisited the split at renewal.

Worked example: what a loose user mix costs

Say you license 2,000 people on App Engine, at illustrative prices of $900 per Creator, $360 per Builder and $120 per User per year. These are not ServiceNow prices, which are quoted per deal. The ratio between the types drives the result.

The loose mix puts 9 percent of users on Creator and costs $116,400 a year more, 31 percent above the corrected mix.

Put the loose mix on Prime at a 40 percent premium with a 7 percent annual uplift, and three years cost $2,230,626. The corrected mix on Foundation with a 3 percent uplift costs $1,172,069 over the same three years, roughly half as much.

How to retype users on evidence

Use the same method as the fulfiller versus requester line on the process side, based on the past 12 months of activity:

1. Creators: people who created or updated application records (sys_app) or table definitions (sys_db_object).
2. Builders: people who built or edited flows in Flow Designer (sys_hub_flow) without shipping an app.
3. Users: everyone else. Compare the totals with the counts on the quote.

Our note on ServiceNow creator licensing covers the developer roles in more detail.

How does the App Engine custom table allowance work?

Every custom table your apps create draws down an allowance on the order form. Exceed it and the next conversation is a tier upgrade or a separate charge, priced by ServiceNow.

Order forms we reviewed usually sized the allowance at roughly twenty tables per app. The current Foundation package publishes 15 custom tables and 3 scoped apps, and Prime has no cap. ServiceNow's Custom Table Guide counts any table it did not provide, created or installed by you or for you, unless the table is specifically exempt.

Which tables do not count?

• Exempt types. Many to many tables (up to 3 custom fields), remote tables, archive tables starting ar_, rotated table shards and document tables.
• Listed extensions. The guide allows you to extend named tables such as cmdb_ci, kb_knowledge and sys_dictionary up to 1,000 times without an App Engine subscription.
• Recent removals. The October 2025 guide narrowed the CMDB exemption to tables extended from cmdb_ci and dropped seven tables from the exempt list, among them sys_choice, sys_filter and sys_user_preference. Tables your team treated as free under the older guide may now count.

Why table counts outrun the allowance

Across single terms we watched table counts rise 15 to 40 percent, driven by unmanaged citizen apps, cloned tables in abandoned projects and extensions no one mapped to the contract. None of it was malicious, and all of it counted against the allowance.

Scope causes most of the surprises. Subscription Management maps tables inside a scoped application at the app level, but global tables must be mapped one by one, and unmapped tables count as App Engine. This is the usual route by which tables built outside properly scoped applications bring separate charges, even inside the allowance.

A table count, worked through

At that point you have a real choice: a larger Foundation allowance or the step up to Prime. Get both prices in writing and compare them with the forecast.

How to check your own table count

A quarterly inventory recording owner, app, purpose and contract mapping is the whole defense, and the first thing a ServiceNow license review asks for. Subscription Management holds the data in three places: Custom Table Inventory (ua_custom_table_inventory), Exempted Table Inventory (ua_exempted_table_inventory), and the Subscription Overview dashboard, which shows the tables each subscription includes.

When does a custom app need ITSM, HRSD or CSM licensing as well?

A custom app needs process licensing as soon as its tables read or write ITSM, HRSD or CSM data. That licensing applies on top of App Engine, the same reclassification that catches ITAM scope and fulfiller roles elsewhere on the platform.

• An app that assigns or updates incidents. The people working those records need ITSM fulfiller licenses.
• An onboarding tracker reading HR cases. The app falls under HRSD licensing.
• A portal reading customer cases. Case and account data brings in CSM licensing.
• A facilities request app on its own tables. App Engine alone covers it.

Process subscriptions include a few App Engine Starter tables for light extensions, each capped at 50 custom fields. Since the October 2025 Custom Table Guide, a custom table that extends Task directly falls outside those rights and needs a full App Engine subscription.

Add a licensing question to your app intake form (which tables, which data, which users) so these cases are settled at design time.

What have we seen in App Engine renewals from 2024 to 2026?

Across the roughly 25 to 35 ServiceNow renewals I reviewed between 2024 and 2026, App Engine was the line item buyers understood least and overbought most. That is predictable when every deal is quoted against a price list the buyer never sees. Three patterns recurred:

• Tier. Upper tier packaging sold against portfolios of approval routers and request forms, usually because the first quote led with it and no one tested it against production apps.
• User typing. Large groups licensed as Creators or Builders where User licensing matched what they did.
• Renewal compression. Tier, user mix, table count and uplift landed in one negotiation, and buyers without their own inventory settled all four on ServiceNow's numbers.

The buyers who came with evidence signed the right tier, the right mix and a 3 to 4 percent uplift cap instead of the default 7. The discount benchmarks show what prepared buyers achieve across the platform.

What will the ServiceNow account team say, and how should you answer?

• "Foundation will hold your developers back." Show production apps against the Prime inclusions and ask for a fixed mid term upgrade price.
• "Your citizen developers need Creator." Builder exists for low code work. License as Creators only the people who created scoped applications in the past year.
• "You are over your table allowance." Ask for the table list behind the claim, then remove exempt tables, mapped tables and retired clones.
• "This app needs ITSM licensing." Ask which tables and users the claim covers, and check whether those people already hold fulfiller licenses.

What should the order form say before you sign?

• A priced upgrade path. The per user price to move from Foundation to Prime during the term.
• Written user type definitions. What makes someone a Creator or a Builder, so the categories do not drift upward.
• Reduction rights. The right to move users to a lower type, or step down a tier, at renewal.
• The table allowance and its price. The number included, exemptions as defined in the Custom Table Guide version in force at signature, and a fixed price for more.
• An uplift cap and named AI features. A written cap covering the term and first renewal, and the Otto or Now Assist features your tier includes.

What to do next

1. 12 months before renewal. Inventory the app portfolio against the Prime inclusions. If nothing in production uses them, your renewal position is Foundation, and the burden of proof belongs to the vendor.
2. 9 months before. Retype users on behavior: who shipped an app, who configured a flow, who only uses the apps. Question every Creator seat that has no app or table change behind it.
3. 6 months before. Count your custom tables before ServiceNow does. Map each to an app, an owner and the allowance, and retire clones and dead projects first.
4. 6 months before. Check the process boundary. Any custom app touching ITSM, HRSD or CSM data needs its licensing settled deliberately before an auditor finds it.
5. 3 months before. Put the uplift cap in writing and bring the whole platform into one negotiation, where App Engine concessions come easiest next to the fulfiller licenses. The CIO guide to negotiating with ServiceNow and our note on the annual uplift cover the wording.
6. Any time. The ServiceNow practice can run the review and the negotiation with you, working only for you.

Frequently asked questions