Your ERPNext implementation agent
Describe it. Hydra builds it.
Ask for a change in plain English, right inside ERPNext. Hydra builds it on your dev site, checks that it works, and shows you everything it touched.
Describe the change. Hydra builds it, then checks it.
Approval steps, extra fields, reports, reminder emails, rules that run when a record is saved. Say what you need in plain English and Hydra sets it up on your development (sandbox) site, then lists everything it touched.
- Role-based access: Hydra works through your own login, so it sees and changes exactly what your account is allowed to. There is no hidden admin account behind it.
- Page context: Switch on the page toggle in the chat box, named after the page you’re on, and Hydra sees what’s on screen, so you don’t have to describe it. It starts off on every page, so nothing is shared unless you choose.
- Sandboxed testing: Anything Hydra writes as code runs first in a safe copy that cannot touch your data, and the field names it uses are checked against your real site. Code that would fail never gets saved.
- Audit trail: Every action is logged against the person who asked for it, and passwords are typed into the app’s own forms, never into the chat.
WHO IT’S FOR
No Frappe skills needed. Hydra knows how ERPNext is put together.
Describe the approval step, form or report you need in plain English. Hydra sets it up, with no scripting and no waiting on a developer.
Set up naming series, tax rules, approval chains and financial reports yourself. You bring the accounting knowledge; Hydra handles the ERPNext side.
Go from a client conversation to a working setup in the same session, and spend your time on requirements instead of writing scripts.
WHAT IT DOES
What people ask Hydra for. Real requests, built on a dev site.
The stages a document moves through, who can approve each one, and stopping people approving their own.
“Quotations need a Sales Manager’s approval before they go out.”Reports with the filters you ask for, built against the fields your site actually has.
“Submitted POs from the last 3 months, filterable by supplier.”New fields on an existing form, and whole new record types, linked both ways so each one shows up on the other.
“Add Nursing Notes to the Inpatient Record’s connections.”Checks and automatic updates when a record is saved. The code runs first in a safe copy that cannot touch your data.
“Classify arm measurements as SAM, MAM or Normal on save.”Emails on a schedule, or when something happens, to the right people.
“Email everyone a weekly list of who’s on leave.”Invoice, quotation and delivery note layouts, built from a description or a sample PDF you attach.
FEATURES
Built into every request. So what it makes holds up.
Bring records in from a spreadsheet. Hydra uses ERPNext’s own Data Import, matches your columns to the right fields and re-runs only the rows that failed, without emailing everyone along the way.
Before anything changes you get a written plan you can edit, download and approve. If a build stops partway, it picks up where it left off.
Hydra knows which ERPNext version and apps your site runs, and checks the documentation for that version before it builds.
After every change, Hydra checks your site to confirm it actually took effect, and tells you plainly if it didn’t.
COMPARED
Not a chatbot that pastes code. An agent that works in your site.
| General AI chat | HydraAI | |
|---|---|---|
| Knows how your site is set up | Only what you paste in | Reads your site before it builds |
| What it can change | Nothing. You copy its output by hand | Exactly what your user is allowed to |
| Checks its own work | No | Runs the code in a safe copy, then re-reads your site |
| How it reaches the live site | You redo it there by hand | A pull request, through Custom Migrator |
| Record of what changed | None | A list of changes, and a log of every action under your name |
Questions
Can Hydra change my live site?
Only if you connect it to your live site, and we recommend you don’t. Hydra is meant for a development or sandbox site, so its changes reach the live site as a pull request your team reviews and merges. Running it on production is an Enterprise option.
What can’t it do?
Anything your own account cannot. For setups that need a password, like connecting an email account, Hydra leaves the password for you to type into the app’s own form.
Does my data leave my site?
What Hydra reads to answer you goes through Espresso’s Hydra service to the AI model. Chats are saved on that service by default. An admin can choose to save them on your own site instead, and incognito chats aren’t saved.
How is it priced?
In credits. Every plan includes some, refreshed every 30 days, and you can add packs on paid plans. Hydra pauses at your limit instead of billing more.
Which versions does it support?
Frappe and ERPNext v15 and v16.