NetSuite environment management for the AI era

  • Automated environment snapshots and transaction versions
  • Deploy safely to NetSuite, with automated checkpoints, approvals and rollbacks
  • Audit-ready evidence for AI-updated systems

Changeport snapshots your NetSuite environments every day, shows exactly what changed, and deploys only the exact release plan your team previewed, whether a person or an AI agent wrote the change.

7 days free. No card required.

Arriving at Production

  1. Edited in NetSuite by an admin customsearch_cp_open_bills Saved search Drift detected
  2. SDF deploy by a developer custrecord_cp_vendor_tier Custom field Drift detected
  3. GitHub pull request #41 custtmpl_cp_invoice Advanced PDF template Held for review
  4. Claude Code via MCP customscript_cp_ap_approval SuiteScript Deployed

Release plan Change #36 · Production

0c91 5e22 a83d

  • Preview validation passed
  • Approved by Priya in Changeport · 17 Oct, 10:23 am
  • Deployed 17 Oct, 10:31 am · verified 10:32 am
An example. Names and values are illustrative.

NetSuite changes come from more places than they used to

Admins edit production directly. Developers deploy SDF projects. Consultants work across several customer accounts. Now AI agents write scripts and propose changes too. When something breaks, the questions stay the same: what changed, who changed it, and how do we put it back?

Routes in
  • NetSuite UI
  • SuiteCloud SDF
  • GitHub
  • AI agents over MCP
  • Consultants
Environments
  • Production
  • Sandbox
  • Release preview
  • Test drive

From snapshot to verified deployment

  1. Step 1

    Connect

    Sign in to production, sandbox, release preview or test drive. Changeport uses Oracle's SuiteCloud tooling and a read-only collector that denies anything not explicitly allowed.

  2. Step 2

    Capture and compare

    Changeport snapshots configuration and SuiteScript files every day and on demand. Compare any two snapshots or environments, and see changes made directly in NetSuite as drift.

  3. Step 3

    Propose and review

    Changes come from your team, from GitHub, or from AI agents over MCP. Review them like pull requests, with line comments, suggestions and optional protection rules.

  4. Step 4

    Deploy and verify

    Deploy the release plan after a fresh validation and drift recheck. Changeport verifies the result. To go back, create a recovery change from the before-images.

Deploy to NetSuite with a checkpoint at every step

Changeport builds a release plan, validates it against the target environment as it is now, and deploys exactly that plan. If the plan or the target changes in between, the preview and any approval no longer apply.

  1. Preview

    The plan is validated against a fresh read of the target, including Oracle's validation and a dry run.

  2. Approval

    An approval is bound to the plan's fingerprint. Change the plan and the approval is cleared. Protection rules decide when approval is required, and every rule starts off.

  3. Recheck drift

    Before writing, Changeport checks that the target has not changed since the preview.

  4. Record, then write

    The deployment attempt is recorded before anything is written.

  5. Verify

    Changeport reads the target again to confirm the result.

  6. Reconcile

    If an outcome is unclear, Changeport checks with read-only calls. It never retries the write blindly.

Rollback is a change you can review too

Changeport keeps the before-image of everything it deploys. To undo a deployment, create a recovery change from those before-images. It is previewed, approved and verified like any other change, and it is blocked if someone has edited the component since, so it never overwrites newer work.

A recovery change restores configuration and files. It does not undo business transactions processed in the meantime, and some NetSuite objects cannot be deleted through SuiteCloud.

Know what is in every environment, every day

Changeport captures each connected environment's configuration and SuiteScript files every day, and on demand before a release or a sandbox refresh. Compare any two snapshots or environments with a semantic diff of custom objects, scripts and files. Each snapshot records what it covered and anything it could not read.

Production: changes since yesterday

Snapshot of 17 Oct, 6:00 am compared with 16 Oct, 6:00 am

  • customscript_cp_ap_approval Script · modified Deployed in change #36
  • custrecord_cp_vendor_tier Custom field · added Changed directly in NetSuite
  • customsearch_cp_open_bills Saved search · modified Changed directly in NetSuite
An example of drift in one environment. Names are illustrative.

Transaction versions Early access

Choose the transaction types to track. Changeport records each saved version, so you can compare a transaction with its earlier versions and restore changed header fields through a reviewed preview.

Estimates, sales orders, purchase orders, invoices, vendor bills and journal entries. Restores follow the same review and approval rules as other changes.

Tell us which transaction types you need: hello@changeport.ai

AI agents propose. People decide.

Changeport has an MCP server, so agents such as Claude Code and Codex can read snapshots and propose changes. Every proposal goes through the same diff, review and release plan as a person's change. Agents get only the permissions you grant.

  • Agents sign in with OAuth. You choose environments and permissions on a consent screen. No environment is selected by default, and review and deploy permissions start unticked.
  • Protection rules can require the approval to be made by a person in the browser.
  • The audit log records who proposed, reviewed, approved and deployed each change.
An example consent screen. Names are illustrative.

Built for in-house teams and consultancies

An account is your company or your consultancy. It holds workspaces, for example one for each NetSuite company you manage, and each workspace holds its environments.

  • Add people to the whole account or to a single workspace, and limit them to particular environments, much like GitHub organisations and repositories
  • Unlimited users and workspaces
  • Roles for owners, admins, contributors, reviewers, deployers and viewers
  • Scoped API tokens for scripts and CI
  • Northwind ConsultingaccountPriya, admin of the whole account
    • AcmeworkspaceSam, reviewer in this workspace
      • Production
      • Sandbox 1
      • Release preview
    • Globexworkspace
      • Production
      • SandboxLee, contributor in this sandbox only
An example account. Names are illustrative.

Audit-ready evidence for AI-updated systems

Every change carries its own history: who proposed it, who reviewed and approved it, which exact plan they approved, when it was deployed and whether verification passed. You do not assemble it after the fact.

Our security page explains how data is stored and processed, and what we do not claim yet.

Audit log
Who proposed, reviewed, approved and deployed each change.
Release receipts
The approved fingerprint and the verification result.
Snapshot history
What each environment contained on a given day.
GitHub
Pull requests and merges become changes with a fresh preview. A merge never approves or deploys by itself, and sync pull requests bring changes made in NetSuite back to the repository.
Collector
Read-only, and denies anything not explicitly allowed. Changeport writes to NetSuite only when someone deploys a change or restores a transaction.
Encryption
AES-256-GCM for captured source files and stored NetSuite credentials. HTTPS for every connection.
Consent
Apps and agents connect with OAuth and get only the environments and permissions you choose.

One plan. Unlimited users.

US$399 a month per account

Includes 2 connected NetSuite environments. Each additional environment is US$199 a month. Every feature is included, and you can try it free for 7 days with no card.

See pricing

See your NetSuite environments side by side

Connect a sandbox, take your first snapshot and compare it with production.

7 days free. No card required.