Skip to main content
Darpan is a reconciliation workspace. It connects source systems, describes source data with schemas, executes reconciliation runs, applies RuleSets, and preserves the output needed to explain each difference. Most of the work in Darpan is front-loaded: connections, schemas, and a saved run are set up once and reused. The docs follow that shape — set up your sources, build a run, then review output and handle the admin around it. If this is your first time, the quickstart walks the full path end to end.

Start with the quickstart

One complete path from environment selection to result review.

Tenant Admin quickstart

Manage one tenant’s settings, connections, saved runs, automations, and results.

​
Set up sources

SFTP servers

Store the SFTP file-access connection that runs reuse.

NetSuite

Save the NetSuite connection used to pull source records.

Shopify

Store the Shopify Admin API connection used by runs and automations.

HotWax

Store the HotWax connection used by runs and automations.

AI provider

Configure the AI provider — a Darpan admin task you do once per provider.

​
Build a run

Schemas

Define source data shapes before a run depends on the fields.

Reconciliation setup

Save the source, schema, and primary-ID setup for repeated runs.

Author rules

Build the field comparisons that decide when systems line up.

Run reconciliation

Execute a saved or newly configured comparison.

Review results

Interpret generated differences and choose the next action.

​
Admin & alerts

Tenant settings

Set the tenant timezone and register Google Chat spaces.

Users & access

Grant tenant access and assign roles.

Automation

Schedule a saved reconciliation run, or run it on demand.

Run-completion alerts

Get a Google Chat message when a run finishes flagging differences.

​
Find your way around

Core concepts

The handful of terms every Darpan screen assumes you know.

Ask Darpan navigation

Open pages, setup records, saved runs, and generated outputs from one search surface.

​
Run Darpan yourself

Independent setup

Clone repositories, install dependencies, start the local stack, and verify sign-in.

Environments

The contexts Darpan runs in, from local development to the hosted app.

Local dev troubleshooting

Recover from common JDK 21, Spark, and clone failures.

​
For builders

The engineering docs explain how the product surface maps to the backend engine: Moqui service contracts, tenant-scoped data access, Spark comparison, Drools RuleSets, and generated output.

Backend engine

Runtime architecture behind Darpan runs.

Engineering workflow

Repo boundaries and verification model used for Darpan development.

API reference

Call the JSON-RPC services behind setup, execution, and review.

Release updates

Shipped tags and their major changes.

Troubleshooting

Login, upload, connection, and run failure checks.