PERMISSIONS
Hydra can only see and change what the person using it is allowed to. It has no access of its own.
CO-PILOT FOR ERPNEXT
Ship your ERPNext projects like a pro.
A Better Way to Ship Frappe. Low-code is now No-Code. Own it like a pro.
Frappe & ERPNext v15 and v16 · Free plan available
Read our back-story →WHY
Changing ERPNext is easy. Keeping every site in step is not.
What your team sets up in the app, the extra fields, the approval steps, the reports, is saved inside that one site. Another site does not get any of it unless somebody sets it all up again by hand. There is no record of who changed what, and nothing to go back to when it breaks. Espresso moves those changes into your app’s code, where they are reviewed, deployed to every site you run, and kept.
01
HydraAI
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.
02
Custom Migrator
Built in the app. Saved into your code.
Custom Migrator lists the settings your team changed on this site that are not yet in your app’s code on GitHub. Tick what should go live and it writes them into your app and pushes them to a branch of their own.
- Change detection: Anything already merged into your main branch is hidden, along with everything ERPNext and your other apps ship themselves. What is left is your team’s work.
- Export preview: Each item is marked new or changed, so you know exactly what the push will contain.
- Config as code: The changes are written into your app as files your repository already understands, so the next deployment applies them to any site you run.
- Pull request workflow: Each export goes up on a fresh branch of its own, and one click opens the pull request with the message and description already drafted. Tag a release too if you want one. Nobody else’s half-finished work comes along with it.
03
Espresso Cloud
Merge it. It’s live.
Espresso watches the branch you choose. When a change lands there it builds your app, puts it on your server and applies the update to the site, keeping the previous version in case you want it back.
- CI/CD: Merge the pull request and the rest happens on its own. Push several times in a row and only the newest is deployed. Nobody logs into a server, runs commands, or copies settings across by hand.
- One-click rollback: If a deployment causes trouble, pick the last good one and Espresso puts it back. It won’t roll back to a release that’s missing an app you now use. That returns your app to how it was, not your data, so restore a backup as well if you need that.
- Build and deploy logs: Each release keeps its own build and deployment log, so a failure tells you where it stopped instead of leaving you guessing.
- Self-hosted or managed: Connect a Linux server with Docker that you already have, and your site, database and backups stay on it. Or run on our servers, where each site gets its own containers and database.
TRUST
Nothing reaches the live site without approval.
LIVE SITE
Hydra runs on the sites you connect it to, and it is meant for a development or sandbox site, not your live one. From there, changes reach the live site as a pull request your team merges.
AUDIT
Every change has a name on it. Hydra logs each action under the person who asked, and each Custom Migrator commit carries their name.
SECRETS
Passwords are typed into Frappe’s own forms, not the chat. Your GitHub token never appears in git config or URLs.
INFRASTRUCTURE
Run on your own servers. Espresso connects over SSH.
RECOVERY
Scheduled backups, upload-and-restore, and going back to any earlier release.
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.
Do I need all three?
No. Custom Migrator works just as well with changes you made by hand, and Espresso deploys any Frappe app from GitHub. Together they cover the whole path from idea to live site.
Which versions are supported?
Frappe and ERPNext v15 and v16.
What is a Hydra credit?
Credits pay for the AI work Hydra does. Simple questions use very little, and building something uses more. Your plan’s credits refresh every 30 days, and you can add a pack on paid plans.
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.
What does “your own server” mean?
Any Linux server you already have. Espresso connects to it and builds, deploys and backs up the site there, so your data never leaves it.