Automate your ERP without opening it to the internet.
Your ERP sits on the internal network for a reason. Trelium installs next to it, reads the POs, invoices, and order emails your team keys in today, and writes the results into the ERP, with a person approving anything that doesn't match.
ERP
Mail server
File shares
Identity
TreliumTrusted by teams that move fast
Why ERP automation ends up on-prem.
Most teams start looking at self-hosting for one of these three reasons. Usually it's all three.
- 1
The ERP isn't on the internet
Many ERPs, especially on-prem installs, only accept connections from inside the network. A cloud tool needs a tunnel or a firewall exception to reach them. Trelium doesn't, because it runs on the same network.
- 2
The documents are sensitive
Customer POs, contract pricing, and supplier invoices are exactly the data your security team doesn't want copied to another vendor's servers.
- 3
ERP changes go through change control
Nothing touches the ERP without review. On-prem upgrades follow your change calendar, so the agents don't change unless your team signs off.
Agents sit next to your ERP.
Trelium runs on the same network as the ERP. Connectors talk to it directly, and every write is recorded in an audit store you own.
- 1Connectors
- Talk to your ERP, databases, mail server, and file shares over the internal network. None of them gets exposed to the internet.
- 2Agent runtime
- Does the actual work, from reading a PO attachment to posting the sales order, on servers you operate.
- 3Data and audit store
- Run history, source documents, and audit logs are written to your storage and kept as long as your retention policy says.
- 4Admin and identity
- People sign in through your identity provider. Roles and approvals work the same way they do in Trelium Cloud.
Your systems
- ERP
- Order inbox
- File shares
- Identity provider
TreliumSelf-hosted on your servers- 1Connectors
- 2Agent runtime
- 3Data and audit store
- 4Admin console
ERP work agents take on first.
Each one turns a document or a request into an ERP entry, and sends anything unusual to a person first.
ERP order and PO entry
Customer POs arrive by email. The agent keys them into your ERP and sends anything that doesn't match to a person.
See the agentOrder changes
Customers and reps ask for changes in plain language. The agent validates each change and updates the existing order in your ERP.
See the agentPurchase orders to suppliers
Someone on your team asks for a purchase order in plain language. The agent builds a supplier-ready PO in your ERP.
See the agentInvoice matching and AP
Supplier invoices arrive by email. The agent matches each one to its sales order, creates the bill, and flags anything that doesn't line up.
See the agent
What your ERP owner and auditors will ask about.
Agents write to the system of record, so the controls are built around who can change what, and proving it afterwards. Read the security overview.
Approvals
Nothing posts without sign-off
Require a person to approve an order, a change, or a bill before the agent writes it to the ERP.
Identity
Segregation of duties
Roles are separate, so the person who builds an agent doesn't have to be the person who approves what it posts.
Audit
Every ERP write traced to its source
Each entry is logged with the document that started it, the decision the agent made, and who approved it.
Data location
Data stays in your perimeter
Orders, pricing, and supplier records stay on infrastructure you control, next to the ERP.
Model training
Never used to train AI
Nothing processed through Trelium, including orders and pricing, is used to train, fine-tune, or improve any model.
For procurement and legal
- SOC 2 Type II
- Audit in progress
- Vendor risk packet
- Ready to share on request
- DPA and MSA
- Available for legal review
- Trust Center
- trust.trelium.com ↗
Three places to run it.
It usually comes down to one question: can this data leave your network? If not, self-host. If it can, Trelium Cloud means there is nothing to install.
Self-hosted
Your data center
Hardware you own
- Best for
- ERPs and file shares that live on your own hardware
- Data location
- Inside your network
- Operated by
- Your IT team, with our engineers
- Upgrades
- Scheduled with your change windows
- Platform
- Full platform, next to your ERP and file shares
Self-hosted
Your private cloud
Your cloud account
- Best for
- Teams that already run their workloads in a cloud account
- Data location
- Inside your network
- Operated by
- Your IT team, with our engineers
- Upgrades
- Scheduled with your change windows
- Platform
- Full platform, under your cloud security policies and logging
Managed
Trelium Cloud
Operated by Trelium
- Best for
- Data that is allowed to sit in a US or EU region
- Data location
- US or EU region
- Operated by
- Trelium
- Upgrades
- Rolled out automatically
- Platform
- Full platform. Move on-prem later without rebuilding agents
What your IT team will need.
This is the checklist our engineers go through with you during scoping, before anything gets installed.
- Infrastructure
- Servers in your data center or private cloud. How many depends on how many agents you plan to run, so we size it together.
- Storage
- Persistent storage for run history, source documents, and audit logs.
- Network access
- Internal routes from Trelium to each system an agent works in: your ERP, mail server, file shares, and anything else in scope.
- Model access
- A model endpoint your security team has approved. If you don't have one yet, we'll go through the options against your data policies.
- Identity
- A SAML identity provider, such as Okta, Google Workspace, or Microsoft Entra.
- Your team
- Someone from IT to own the install and upgrades, and one person who owns each workflow you automate.
Bring the network diagram to the call.
Thirty minutes with our engineers. We'll go through where Trelium sits in your network, what it connects to, and how model access works. Bring your IT and security leads.
Questions about on-prem ERP automation.
Trelium works with ERPs like SAP, Oracle, NetSuite, and Microsoft Dynamics. Where an ERP has an API, Trelium connects to it directly. Where it doesn't, a browser agent can work through the approved web interface instead.
Yes, that is how agents enter orders, update them, and create POs and bills. You decide whether a person has to approve each write before it happens.
The agent stops and sends it to a person instead of posting it. Nothing unusual runs through silently.
Yes. Building agents, running them, and approving their work are separate roles, so the same person doesn't have to do all three.
Yes. Every input, decision, and action is logged, so any entry can be traced back to the document that started it and the person who approved it.
No. Trelium runs inside the same network as the ERP, so agents reach it over internal routes and the ERP stays closed to the internet.
Not without your sign-off. On-prem upgrades are scheduled with your team on your change calendar, never pushed automatically.
No. Nothing processed through Trelium, including orders, pricing, and customer records, is used to train, fine-tune, or improve any AI model, by Trelium or any third party.