1. You own the whole thing
ZakERP installs onto a machine in your own building. The application runs on Apache Tomcat, the data lives in your own SQL Server, and the backups are files you can copy onto a disk and put in a drawer. Nobody outside your company can read them, throttle them, price them, or switch them off.
That sounds like a technical detail. It is really a power question. When your ERP lives on someone else's servers, three things stop being yours: the timing (they decide when the system updates and when it is down), the price (a renewal is a negotiation you enter from behind), and the exit (leaving means extracting your own history from a format they designed).
A practical consequence. Because the application sits on your local network, the people using it are not competing with your internet connection. A payroll run or a 1,000-row attendance report is a query across the office LAN, not a round trip to another country.
You also keep the right to inspect. The screens, reports, dashboards and approval routes are plain text files in your installation. Any competent person you hire — today or in five years — can open them and read exactly what the system does. There is no part of your own business logic that is hidden from you.
2. It changes at your speed
This is the reason most of our users stay, so it is worth being concrete rather than enthusiastic.
In a conventional ERP, "add a column to that report" travels a long road: you raise a request, a consultant estimates it, someone approves the cost, a developer writes code, the change is tested, and eventually a release window arrives. Weeks pass. The request was not difficult; the process around it was.
In ZakERP, a report is a short text file. Here is a complete, working one — not an extract, the whole thing:
// A complete report. This is the whole file. search lateArrivals table zAttendance select "zactive = '1'" order xdate desc rows 31 search paginate export columns xstaff, xdate, xintime, xouttime, xstatus headers "Staff","Date","In","Out","Status" daterange xdate caption "Period" default month end daterange filter xstatus caption "Status" pick "Late,Late & Early Leave" end filter end search
Save the file, refresh the browser, and the report exists — in the menu, with a period bar defaulting to this month, a status filter, sortable columns, paging and export to CSV, Excel and PDF. Add one more line and it is restricted to named roles, or gains an email button. No compilation. No restart. Nobody is logged out while it happens.
The same idea covers nine kinds of definition — screens, saved searches, charts, dashboards, approval workflows, calendars, dialogs, home pages and ID cards. And you do not have to type them: the built-in Customisation Studio is a point-and-click builder that writes these files for you, and exports a set of changes as a bundle you can carry from a test server to the live one.
Why this matters more than a feature list. Every company has perhaps twenty rules that are genuinely its own — how overtime is counted, which manager signs what, what a "complete" purchase looks like. No packaged ERP will contain those twenty rules. The only question is whether adding them takes an afternoon or a project.
3. It knows how you actually work
ZakERP was not translated for this market; it was built in it. Things that are normally expensive customisations are simply how the system already works:
- Your existing attendance device keeps working. ZakERP reads the device's own database directly, so punches arrive without anyone exporting a file. Mobile punches from phones — with face matching and geofencing — land in the same timeline, and field staff can be given an explicit remote-punch permission, one employee at a time.
- Late, early leave and overtime are judged against the employee's own shift, not a single company-wide number, because a general shift and a twelve-hour shift are not the same working day.
- Leave is a rulebook, not a register. Entitlement, accrual, carry-forward, encashment ceilings and whether a weekly holiday inside a leave range counts as leave — all decided by settings, so the balance is calculated rather than argued about.
- Daily allowance and subsidised meals are first-class. Rates are effective-dated, so changing this month's rate does not silently rewrite last year's history.
- Approval chains are data. Supervisor, then GM, then MD is a row in a table, not a line of code, so changing who signs what is an afternoon's admin work rather than a development request.
4. One database, not five tools that email each other
Most companies do not have an ERP problem; they have a reconciliation problem. Attendance lives in one place, leave in another, salary in a third, and the accounts somewhere else again. Every month, somebody spends days making the four agree — and the moment they agree, they start drifting apart.
In ZakERP an employee exists once. The punch that marks them present, the leave day that marks them absent, the allowance they earn for attending and the payroll line that pays them all point at the same record. Nothing is copied between systems, so nothing can disagree.
The same discipline runs through the money side: every financial posting enters the ledger through a single controlled route, and stock movements are written to one signed ledger with a reconciliation view that proves the stock value against the accounts. The system is designed so that "the report says one thing and the ledger says another" is not a state it can reach.
5. What it actually costs
We will not put invented prices on a web page. But the shape of the cost is something you should understand before any conversation, because it is where on-premise and subscription software differ most.
| Cost | Subscription cloud ERP | ZakERP |
|---|---|---|
| Software | Per user, per month, forever. Grows every time you hire. | A licence installed on your server. Does not grow with headcount. |
| Hardware | Included in the subscription. | One ordinary server you probably already own, plus backups. |
| Implementation | Usually the largest single line, and often a multiple of the first year's licence. | Real work, and quoted as such — but smaller, because less has to be built from nothing. |
| Changes after go-live | Billed per change, or absorbed by your own consultants. | Most are configuration your own trained staff do themselves. |
| Leaving | Data export, migration project, and a hard stop date. | You already hold the database and the definition files. |
The honest summary: subscription software has a low first payment and an unbounded total; on-premise software has a higher first payment and a total you can predict. If your headcount is going to grow, the second shape is usually kinder — and if it is going to shrink, you are not paying for the absence.
6. What people worry about
"What if something goes wrong at 9pm?"
Because the system is yours, the recovery is also yours: restore last night's database backup and the application is running again. There is no queue and no ticket priority. That is also the responsibility side of ownership — somebody in your company needs to make sure that backup actually runs, and we set that up during installation.
"Is it as feature-rich as the big global suites?"
No, and it never will be. Those products carry twenty years of features for hundreds of industries in dozens of countries. ZakERP carries the features one company actually uses, plus the ability to add the ones you find you need. Different bet, deliberately.
"What if we outgrow you, or you disappear?"
This is the fairest question anyone asks a smaller vendor, and the answer is structural rather than reassuring words: the database is standard SQL Server, your customisations are readable text files on your own disk, and the whole thing runs on ordinary open technology. If you ever had to continue without us, another team could pick it up — because nothing is hidden and nothing is locked.
"How do we stop the wrong people seeing salaries?"
Access is by role, and it is enforced where it matters — not just by hiding menu items, but at the address of every screen, report, chart and calendar, so a copied link does not become a back door. Each person has one live session at a time, and administrative actions are written to an audit log.
"Our data is messy. Will that break the project?"
Messy data does not break the project; pretending it is clean does. Employee records, leave history, suppliers and opening balances are imported and reconciled before go-live, and the import routines are part of the product rather than a one-off favour. Expect to spend real time here — it is the single best predictor of whether an ERP go-live goes calmly.
7. Who it is not for
A vendor who says their product suits everybody is telling you something about the vendor.
A good fit
- One company, or a small group, operating in one country
- Roughly 50 to 1,000 people on the payroll
- Strong opinions about your own processes, and rules that no packaged system contains
- A preference for keeping data inside the building
- Somebody in-house who enjoys learning the system and becoming its owner
Not our territory
- Multinationals consolidating many legal entities across currencies and tax regimes
- Companies that need a large third-party add-on marketplace
- Organisations with a firm policy that nothing may run on their own hardware
- Anyone who wants software nobody ever has to learn — an ERP repays training, and there is no version of it that does not
If you are in the right-hand column, we would rather tell you now than six months into an implementation. If you are in the left-hand one, the next useful step is to see the system working on a sample of your own data.