Six weeks ago I opened Cutova up. I said then that I would rather show you than argue about it, so here is what I have been showing.
Since launch I have shipped something almost every day. Some of it you asked for. Some of it came from watching real people use Cutova against real Epicor systems and seeing exactly where it needed to be better. All of it is live today.
Here are the parts I am most excited about.
Your automations can work in Epicor now
This is the one I have wanted since the beginning.
Until now, Cutova needed a person: someone signs in, authorizes, and asks. That is great for a conversation. It does not help the workflow that should run at 2 AM without anyone watching it.
Agent tokens fix that. An administrator creates one for an Epicor user on the instance’s Users tab, and an automation uses it to call Cutova directly. An n8n workflow, Claude Code running unattended, an app you build on the Agent SDK, or your own script. Every call runs with that Epicor user’s permissions, exactly like a person would. I strongly suggest a dedicated integration user with only the access the workflow needs.
You stay in control. A token is shown once, and Cutova does not keep a copy. It expires on the date you choose, and you can revoke it at any time. Revoke it and the next call is refused.
Agent tokens come with Team and above: two on Team, five on Company, twenty-five on Company Plus, and as many as you need on Enterprise. The pricing page has the details.
Every tool call, on the record
The first question every IT team asks me is “can we see what it did?” Now the answer is yes, in as much detail as you want.
Audit logging gives each instance an Audit logging tab: who called which tool, when, how it went and how long it took. Search it, export it to CSV, and keep it for up to thirty days. If your controls require it, turn on strict audit and Cutova will refuse any call it cannot record.
Then the part your security team will like most: every tool call can stream straight to your SIEM, over syslog with TLS, a couple of seconds after it happens. SolarWinds and Papertrail, Sumo Logic, Better Stack, Datadog, New Relic, or any syslog receiver. Start with metadata only. Move to Advanced to include what the assistant asked for, or Full to include what Epicor sent back. At those levels the data goes to your SIEM as is, so pick the level your policies allow. If your receiver goes down, Cutova retries, shows it in the console and emails your administrators.
Audit logging is part of Enterprise and is off until you ask for it. The security page explains exactly what is recorded at each level.
You decide who can use what
Not every tool belongs in every hand. Per-user tool access lets you allow or deny each tool for each person or group, with a sensible default for everyone else. You can bring your Epicor users in before they ever sign in, set their access, and have it waiting for them on day one.
More Epicor, more versions
Epicor shops do not all run the latest release, and Cutova should not care. Since launch:
- Kinetic 2021 works, and its older API descriptions are converted so your tools get proper inputs and outputs.
- 11.1.100, 11.3.100 and 12.0.100 join 12.1.100, each with its own registration package.
- The register wizard now picks the right package for your Epicor version, and packs install the right build for it.
If you are on a version that is not on that list, tell me. It is probably next.
Speaking the newest MCP revision
The Model Context Protocol keeps moving, and Cutova moves with it. Cutova now serves the July 2026 revision of MCP alongside the 2025 revisions, so newer assistants get the newer protocol and the clients you already use keep working exactly as they did. Nobody has to upgrade in lockstep with anybody.
Easier to start, easier to run
- Try any paid plan free for 14 days, no credit card. Starter, Team, Company or Company Plus. If you do nothing, you simply return to Free.
- Simpler pricing. One flat monthly price per tier, sized by how many people actually use Cutova, not by your Epicor license count. Annual takes two months off.
- A guided setup. A Start here panel and a step-by-step setup in the console, and a redesigned register wizard.
- A setup guide for each assistant: Claude, ChatGPT, Microsoft Copilot Studio, VS Code and LibreChat.
- The Epicor Functions pack is now available. Your assistant can create and edit Epicor Functions, and you choose which ones to expose as tools. The Risk and Outliers pack is coming soon.
The gateway, rebuilt to take a punch
Here is the honest one.
The on-premise gateway is how Cutova reaches an Epicor that lives behind your firewall. Last week a customer’s gateway kept dropping in the middle of normal work. I dug in, and found that when two large Epicor responses came back at the same moment, they could trip over each other on the way out and take the connection down. It only shows up when a lot of data moves at once, which means people are really using it. That is a good problem to have, and it is fixed.
Gateway 1.3.1 sends every response cleanly, one after another, however big and however many. I tested it hard, on purpose, on slow links with huge payloads, and it holds. Along the way it got a lot smarter:
- If a gateway is offline, you now get a clear message telling you to start it, not a mysterious server error.
- Revoking a gateway now means it is done. The agent backs off politely instead of knocking on the door all day, and re-registering from the Monitor takes one click and one approval.
- The Gateways page now shows who set each gateway up and where it connects from, and every create, register, revoke and delete is now recorded.
- Upgrading is just running the new installer. It keeps your gateway’s identity and starts the service again, so there is nothing to re-register.
If you run a gateway, grab the new installer from the Gateway Installer card in the console.
And a pile of fixes
I will not list every one. A few you might have noticed: file uploads that came through empty, BAQ tools that broke after a rename, invitations you could not renew once they expired, and a tab that reloaded itself in a loop. All gone. I also tightened how Cutova handles errors from Epicor, so connection details stay out of the error messages you see.
What is next
A few things I am working on now:
- Epicor-side detail in your audit trail, so each tool call in your SIEM links to the exact Epicor requests it made.
- Gateway update notices, then automatic updates, so the next fix reaches every site without anyone visiting it.
- Sign in with your own identity provider for Enterprise, on the roadmap.
- The Risk and Outliers pack, coming soon.
- Older Epicor releases, starting with 10.2.500.
Keep telling me what you need
Most of this list started as an email or a conversation. Keep them coming. If you run Epicor and want to see any of this against your own data, write to hello@cutova.ai. I still answer my own email.