rung1 Enterprise
Design partners · Phase 1Change ERPNext by asking. Nothing lands unchecked.

Your agent can change your books, and nothing it changes happens without a rule check, a person who can say no, and a record you can read.
Tested on a copy of your books. Checked against your own ledger, stock, GST and audit trail. Undo for 30 days.
Illustration. A request to block purchase orders above ₹2,00,000 unless approved is built on a copy, passes the ledger, stock, access, GST and audit-trail checks, is approved by the finance head R. Iyer at 11:42 IST, and is written to proof record a41f with undo available for 30 days.
You won’t see customer logos here yet. We are in our design-partner phase, and we’d rather show you how it works than who uses it.
A discount field added in March. GSTR-1 won’t file in April. Eleven days and a penalty later, nobody can say who changed what. Permissions only tell you a role may write. They don’t tell you your trial balance still balances.
An ERPNext partner quotes ₹75,000–1.5 lakh and 4–16 weeks for changes like this. With rung1, you describe the change, and it reaches your books only after it’s been checked and approved.
Arithmetic, not a measurement: if each step of an agent’s task is right 98% of the time, the chance that every step is right is 0.98n. At 50 steps it is about 36%. Per-step accuracy here is an assumption for illustration. source to confirm Use ← → to scrub.
Not in scope: rung1 never pays, never files a return, never posts into a closed period. What rung1 will never do
In plain language, on the web or WhatsApp.
The agent builds the change on a throwaway copy of your site, never on live.
Ledger, stock, access, GST and the MCA audit trail, computed from your data.
What changes, what’s removed, whether it can be undone, what it costs in rupees.
A person you name says yes. Rejections need a written reason, which the agent learns from.
Who asked, what the checks said, who approved, how to undo.
One button, and the undo is checked too.
The agent has drafted a change and the checks have run on a copy. The gate waits for the named approver. Nothing reaches your books.
Refused · Ledger check
This change was not allowed.
Your books would have gone out of balance by ₹4,250.00. We tested this on a copy of your site. Your live books have not been touched.
GATE_LEDGER_UNBALANCED · cost of this refusal ₹0.00
Others sell the edit. We sell the gate.
You never pay for a change that didn’t reach your books.
Not by you, not by us, not by the agent.
A named person says yes.
Never written by AI.
| # | Change | Outcome | By | Undo / cost | Chain |
|---|
Checked and recorded by the elan1 layer. How a proof record works
Change ERPNext by asking. Nothing lands unchecked.

A trial balance that ties to the rupee, signed by your CA.
Keep your own ERPNext. Bring the checks to it.
Checked changes to your own CRM. Never contacts a customer.
Approve a waiting change by phone, with a read-back.
Price, stock and refund changes that reconcile to your books.
Design previews of the rung1 app with realistic Indian data. Screens will change as design partners use them.





Owners and CFOs
“Can I change my ERP without another partner project?”
Finance teams
“What exactly changes, and can I undo it?”
Chartered accountants
“Will this move my client’s trial balance without me knowing?”
Already on ERPNext
“Can I keep my site and still get the checks?”
Moving off Tally
“Will my opening balances tie?”
Returns still generate, HSN and place of supply intact.
The statutory edit log can’t be switched off, and we check it on every change.
Mumbai region, including backups and logs.
Free seat, read and approve.
“A model may produce a write intent. It may never produce an allow.”
Where we stand
Dates are plans, not promises. Full roadmap
Three things you can check today
rung1 is software from elan1 that lets Indian businesses change their ERPNext system by asking in plain language. Every change is built on a copy of the books, checked against the ledger, stock, access, GST and the MCA audit trail, approved by a named person, recorded in a proof record, and can be undone for 30 days.
It is expected to, sometimes. Every change runs on a copy of your books first, the checks run against it, a person you name approves it, and undo is available for 30 days. A wrong change can’t reach your live books without a named approval, and it can’t stay there.
No. Changes are built and tested on a throwaway copy of your site. One service publishes, after taking a snapshot, and it restores automatically if a check fails on live.
Never. It prepares; it never pays. It never submits anything unattended, never posts into a closed period and never amends a filed return.
In Mumbai, India, including backups and logs. You own it, it’s never used to train AI models, and you can export it any time with no exit fee.
A free seat on every client site, the approval queue and an audit-pack export.
10 design-partner slots for Phase 1. 90 days free, onboarding done for you, a named founder on WhatsApp.
Not for service firms under ₹1 crore, firms above ₹250 crore, or anyone whose CA won’t take a call.