Frequently asked questions

How SNcode compares to what ServiceNow ships, and what connecting it actually does to your client's instance.

How is this different from ServiceNow Build Agent?

+

Build Agent is a strong tool, and if you work in one instance that’s on a current release with an Otto for Creator (formerly Now Assist for Creator) entitlement, it’s a sensible choice — it’s from the vendor and governed by default.

The difference shows up when you work across clients. Build Agent is installed and entitled per instance: a store app, plugin activation, admin rights on that instance, a recent release family, and a prompt budget on each one. Five client instances means five installs, five entitlements, five approvals — and on any client running an older release, it isn’t available at all.

SNcode installs nothing on any client instance. It connects from your desktop over the REST API, keeps each client in its own workspace with its own credentials and history, and works with whichever release your client is actually running. It also covers work that isn’t app-building: instance forensics, data profiling and loads, cross-system reconciliation.

Does SNcode need to be installed on my client’s instance?

+

No. There’s no store app, no plugin, no update set, no change request. SNcode runs on your machine and connects over the ServiceNow REST API with the credentials you already have. Nothing is deployed to the client’s platform, and nothing about their instance changes by connecting.

Still have a question? Email support@sncode.dev, read the docs, or review the security model.