Feature
Local-first deployment — your data on your servers
The cloud demo at aion-erp.vercel.app shows what AION can do. For factories that need on-premise — data residency, network reliability, governance preference — the same product runs on your hardware. Your servers, your network, your data residency.
Why MENA factories often prefer on-premise
Cloud-first is the default for most modern software, and AION is happily available as cloud. But there's a specific set of factories — family-owned, regional, conservative in their data practices — for whom cloud isn't the right answer. For those factories, on-premise isn't a compromise; it's a requirement.
Three reasons we see most often:
- Data sovereignty. The factory's financial books, customer records, supplier records, employee records all stay within Saudi (or Egypt, or wherever) jurisdiction. No data crosses borders to a vendor's cloud region. For some businesses this is a legal requirement (certain government suppliers); for others it's a board-level governance preference.
- Network reliability. Egyptian factories outside Cairo, Saudi factories in industrial cities outside Riyadh — internet connectivity isn't always 99.99%. A cloud-only ERP becomes the bottleneck the day the link goes down. On-premise runs on your LAN; an internet outage means external e-invoicing pauses but day-to-day operations continue.
- Governance preference. Family-owned MENA businesses often prefer their financial data to be physically present on hardware they own. It's not always a technical argument; it's a values argument. AION respects that without trying to convert anyone.
For factories where these don't apply — cloud is genuinely the better deployment model. For factories where they do — on-premise should be a first-class option, not a compromised fallback.
What stays the same between cloud and on-premise
The on-premise product is the cloud product. Same codebase. Same modules. Same UI. Same updates. The deployment differs; everything else is identical.
- All 19 modules — GL, AP, AR, inventory, manufacturing, costing, sales, procurement, payroll, fixed assets, cash management, leasing, HR, and the rest.
- SLA engine for zero manual journal entries.
- Multi-country, multi-BG architecture — even an on-premise tenant supports the three live demo BGs and any country additions.
- Bilingual Arabic + English at the same parity.
- Costing engine — multi-level BOM rollup, variance analysis, WIP valuation, period close with crash recovery.
- E-invoicing — ZATCA Phase 2 and ETA both work on-premise, with external clearance submitted through your network's internet egress.
- Reports and dashboards — same library, same data.
- API access for integrations — same API surface, just hitting your local servers.
What differs: where the database lives, where the application servers run, who has admin access at the OS level. The factory's IT team plus AION's deployment support, not just AION.
What you need for on-premise
For an SMB F&B factory (annual revenue SAR 5M–100M, 20–100 employees, 50–200 SKUs, 100–500 customers), typical infrastructure:
- 2-4 Linux servers running modern Ubuntu or RHEL. One for application compute, one for the database (PostgreSQL), optionally one for background jobs, optionally one for file storage. Mid-range hardware — 16-32 GB RAM each, SSD storage, no exotic requirements.
- PostgreSQL 14+ as the database engine. Standard open-source PostgreSQL — no proprietary licence required.
- Internal LAN for user access. Most factories run AION on the same network as their other internal systems.
- Optional internet egress for e-invoicing clearance (ZATCA portal, ETA portal), email sending, and product updates. The egress is read-mostly — your data isn't being uploaded to anyone, just specific clearance payloads going out.
- Backup infrastructure per your factory's policy. We recommend daily database backups with at least 30-day retention; some factories run hourly. The backup target is your choice — internal NAS, external service, or both.
- An IT contact on the factory side. We don't need full-time IT staffing; a part-time contact who can manage Linux server admin, network configuration, and basic database operations is sufficient.
For factories without internal IT capability, we partner with local IT services in Saudi, Egypt, and the broader GCC who can host the AION on-premise installation as a managed service. The data still stays within the factory's preferred region; the operational management is outsourced.
How deployment actually works
A typical on-premise deployment takes 6-10 weeks from kickoff to go-live:
- Week 1: Infrastructure planning. Confirm server specs, network topology, internet egress configuration, backup strategy. Procure hardware if needed.
- Week 2-3: Initial installation. AION deployment team provisions the application servers, sets up the database, configures the BG (country profile, COA template, certificates). The system is operational but empty.
- Week 3-5: Data migration. Master data (customers, suppliers, items, GL chart), opening balances, optionally historical transactions. Same migration path as cloud — we just upload to your servers instead of ours.
- Week 5-7: Training and parallel. Users trained on AION. Parallel operations against existing system (if migrating from QuickBooks, SAP, or whatever).
- Week 7-10: Cutover and stabilisation. AION becomes system of record. Monitoring for the first month. Issue resolution.
Once live, the on-premise factory operates independently. We provide product updates monthly, support via remote access (with your permission, audit-logged), and assistance for any country additions or major configuration changes.
Common questions
Why would a factory want on-premise instead of cloud?
Three common reasons: (1) data sovereignty — financial and customer data stays within the factory's legal jurisdiction; (2) network reliability — some factories have intermittent connectivity that breaks cloud-only workflows; (3) governance preference — family-owned businesses often prefer their data physically present rather than on a vendor's cloud.
Is the on-premise product different from the cloud product?
No. Same codebase, same modules, same updates. On-premise just runs on your servers instead of ours. We support both deployment modes from the same product line; you don't buy a "lite" version when you choose on-premise.
What infrastructure does on-premise AION require?
For an SMB F&B factory: 2-4 mid-range Linux servers (compute, database, file storage), a PostgreSQL database, network access for users on your internal LAN, optional internet egress for e-invoicing clearance and email. The exact specs depend on transaction volume and user count. We provision the deployment together with your IT team.
How do updates work for on-premise deployments?
Scheduled in coordination with you. We release product updates monthly; on-premise customers get a maintenance window to apply the update. The update process is automated — we don't need on-site access. Some factories apply every update; some batch quarterly. Both patterns work.
Discuss on-premise deployment for your factory
Send us a note with your context — country, factory size, current systems, infrastructure preferences. We'll respond within a business day with the discovery questions and rough timeline.