One machine holds everything
Application and database share the same box. It is also the backup, the file server, and the machine nobody can reboot during business hours.
Legacy ERP · Free ebook
Your ERP only opens inside the office. We put it in the browser.
Today it is a monolith: application and database on the same machine, everyone on the same local network. We split it into four dedicated servers, publish the system for browser or remote connection, and put a dedicated IP and an edge firewall in front of it.
- The four-machine map: what moves to which server, and why the monolith stops being one
- How access gets published: browser or remote connection, with the same screens your team knows
- What sits in front of it: dedicated IP, edge firewall, and infrastructure that is yours alone
The ERP does not have to be rewritten to stop being stuck. It has to be split.
Get the ebook
The four-machine architecture, explained end to end. No spam.
What you run today
It worked for years. Then the company stopped fitting in it.
Nothing here is a mistake. It is what a growing company builds when the ERP arrives before the network does. The problem is what it costs to keep it that way.
The system only opens at the desk
Access is local. Home office, a second branch, a salesperson on the road: each one becomes a workaround, a VPN nobody maintains, or a phone call to someone who is in the office.
The perimeter is the office door
The server sits in a room, on a shared link, behind whatever the modem does. When a ransomware note shows up, the ERP and its backup are on the same disk.
What we build instead
One machine becomes four, each doing one job.
The same ERP, the same screens, the same vendor. What changes is where each piece runs and how your team reaches it.
Server 01
Database server
The database gets its own machine, sized for it: memory for the working set, disk for the growth curve, backup and restore tested instead of assumed.
Server 02
Application server
The ERP application runs alone, so a heavy report stops competing with the database for the same CPU. Vendor homologation, when it is required, happens here.
Server 03
Domain controller
Users, groups and policies get a server of their own. One identity per person, revoked in one place on the day the person leaves.
Server 04
Remote access and publishing
The system is published for the browser or for remote connection. Your team signs in from anywhere, and the data never leaves the data center.
Protection and operation
Out of the office, and better guarded than it was there.
Leaving the server room is not the risk. Staying is. Here the environment is dedicated, the perimeter is a firewall instead of a modem, and someone is on shift at 3am.
Dedicated IP
Your environment answers on an address that is yours, not on a pool shared with strangers.
Edge firewall
Rules at the perimeter, published ports controlled one by one, and access allowed by policy instead of by habit.
Dedicated infrastructure
Reserved capacity in Optidata-owned data centers in Brazil. No noisy neighbour deciding how your month-end close performs.
24/7 support, ERP people
A staffed NOC and SOC around the clock, and a team that has moved ERPs before. Average first response under 8 minutes.
Free, delivered as a PDF in Portuguese (Brazil). Prefer to talk first?Talk to a migration specialist.