Platform

One platform for understanding, changing and governing NetSuite.

ConfigLedger keeps a live model of your account — every field, workflow, script, search, role and integration, and the relationships between them.

That model is what lets a plain-English business request become a change plan you can actually trust.

The ConfigLedger lifecycle

Understand → Change → Validate → Control

Configuration intelligence is the foundation. Governed change is the product. Each phase feeds the next, and every step stays visible to the people accountable for the system.

01
Understand

Map every object and dependency in the account into a persistent configuration graph.

02
Change

Turn a natural-language business request into a costed, dependency-aware change plan.

03
Validate

Build in Sandbox, then test the result against the original requirement before anyone approves.

04
Control

Governed approvals, rollback readiness, audit history and post-deployment monitoring.

The platform

One configuration intelligence layer for the whole account.

Nine connected capabilities built on a single persistent graph of your NetSuite configuration.

Configuration Explorer

Search and explore NetSuite configuration from one place.

Dependency Intelligence

Understand what uses what.

Ask ConfigLedger

Ask questions about your environment in plain English.

Change Impact

Assess potential consequences before configuration changes.

Configuration Health

Identify possible duplicates, unused objects and inconsistencies.

Workflow Intelligence

Translate complex workflow logic into business language.

Roles & Controls

Understand access and potential permission conflicts.

Change Monitor

Track how your configuration evolves over time.

Account Handbook

Automatically create living NetSuite documentation.

Overview
Production — Global Holdings Ltd
Last scan 03 Sep 2026 · 04:12
Config Health
82%
Objects Scanned
1,274
Dependencies
5,908
Changes / Month
12
Potential Issues
47
Configuration inventory
Saved Searches426
Custom Fields318
Workflows47
Custom Roles28
Custom Segments12
Scripts76
Custom Records39
Architecture

Two engines. One governed system.

The configuration graph is what makes automated change safe. The change engine is what turns understanding into implemented, tested and approved configuration.

Intelligence Engine
The foundation

A continuously maintained model of what exists inside your account and how every object connects.

What exists
  • Custom fields
  • Workflows
  • Scripts
  • Saved searches
  • Roles
  • Forms
  • Segments
  • Integrations
How it connects
USESDEPENDS ONTRIGGERSREFERENCED BYVISIBLE TOOUTPUTS TO

The result is a working digital twin of your NetSuite configuration.

Change Engine
The new layer

A business requirement written in plain English becomes a governed change set — planned against your real dependencies, built and tested in Sandbox, and deployed only with human approval.

  1. 01Requirement
  2. 02Current-state analysis
  3. 03Impact assessment
  4. 04Change plan
  5. 05Configuration / code generation
  6. 06Sandbox deployment
  7. 07Automated QA
  8. 08Human approval
  9. 09Production deployment
  10. 10Post-deployment monitoring
How it works

From NetSuite metadata to configuration intelligence.

01

Connect

Securely connect your NetSuite environment.

02

Scan

ConfigLedger inventories accessible configuration metadata.

03

Map

Objects and deterministic dependencies become a configuration graph.

04

Understand

AI translates technical configuration into clear business explanations.

05

Monitor

Future scans identify changes and preserve historical configuration memory.

AI explains the configuration. It does not invent the dependencies.

Your configuration graph is built from actual NetSuite metadata and detected relationships.

Architecture

A deterministic foundation with intelligence on top.

NETSUITE
Accounts, subsidiaries, customisation
CONFIGLEDGER CONNECTOR
Controlled, permissioned access
CONFIGURATION INVENTORY
Objects and metadata
CONFIGURATION GRAPH
Deterministic relationships
INTELLIGENCE LAYER
Explanation, analysis, documentation
Configuration Explorer
Dependency Analysis
Ask ConfigLedger
Change Monitor
Account Handbook
Impact Analysis
Positioning

Oracle helps a developer build a customisation. ConfigLedger helps the business manage the whole change.

Oracle's SuiteCloud Developer Assistant is a capable tool for developers writing SuiteScript and custom objects inside their IDE. ConfigLedger is not competing on code generation — the value is the lifecycle around it.

01Understand the customer environment
02Understand the business request
03Trace existing dependencies
04Design the change
05Build the change
06Deploy to Sandbox
07Test against the requirement
08Explain before and after
09Collect business approval
10Deploy to Production
11Monitor afterwards
12Preserve institutional history

The model underneath is replaceable infrastructure. The configuration graph, the NetSuite actions, the change orchestration, the testing framework and the governance are the product.

Your NetSuite contains years of business logic.

Understand it. Then change it safely.

Map your configuration, trace every dependency, and turn business requests into governed changes that are tested in Sandbox and deployed only when you approve.

Understand → Change → Validate → Control