Why choose Nilex for secure, custom business software SOFTWARE YOU
CAN TRUST.
Custom software built around the way your company works, secured from the first line of code, and designed so no record can be changed without a trace.
FOUR PROMISES IN
EVERY SYSTEM.
A business system holds your money, your customers and your daily operations. It should fit you exactly, keep outsiders out and keep everyone inside honest.
- 01
Built around you
A system designed for your workflow, your approvals and your documents. You don’t reshape your company to fit the software.
How we do it - 02
Secure by design
Security is part of the first line of code: encryption, strict permissions and protection against break-in attempts.
How we do it - 03
Protected from manipulation
Every action is recorded and financial records can’t be quietly edited or deleted. Nothing changes without a trace.
How we do it - 04
Easy to run
Clear screens, professional reports and a team that trains you and stays with you after launch.
How we do it
BUILT AROUND
YOUR BUSINESS.
Generic software forces every company into the same mould. We start from how you already work (your branches, approvals, documents and reports) and build the system around it. You get exactly what you need, connected to the tools you already use.
SEE WHAT WE BUILD →SECURE BY
DESIGN.
Security isn’t a feature we add at the end. It’s the baseline every new Nilex system is built on, explained here in plain language.
Encrypted connections
HTTPS on every page, with certificates that renew themselves, so data can’t be read on the way.
SSL certificates →Passwords nobody can read
Never stored as text: hashed with a unique salt, so even we can’t read them and a stolen database is worthless.
Encryption with salting →Break-in protection
Sign-in and sensitive pages are rate-limited and accounts lock after repeated wrong passwords, so guessing stops early.
Rate limiting →Sessions scripts can’t steal
Logins live in HttpOnly cookies with short, signed tokens that rotate. A stolen session is detected and shut.
HttpOnly cookies →Permissions checked on the server
Every request proves who is asking and is checked against that user’s role, not just hidden buttons on the screen.
JWT →Strict input checks
Every value sent to the server is checked against a strict rule before it goes anywhere near your database.
Zod →Hardened responses
Security headers tell the browser exactly what your site may do, and only the sites you name may call your API.
Helmet.js →Safe file uploads
Every upload is checked for what it really is and how large it is, then stored where it can never be run.
Multer →Controlled database changes
Every change to the database structure is described, reviewed and reversible. Nothing is edited by hand in production.
Sequelize →
Every page and API endpoint is tested against the OWASP Top 10, the industry list of the most common web attacks. Each finding is logged with its severity and tracked until the fix is verified.
NO SILENT
CHANGES.
The biggest risk to a business is often inside it: an edited invoice, a deleted payment, a stock count that quietly changes. Our systems make that impossible to hide.
Every action is logged
Who did what, when, and on which record, for every account and every feature, written down and searchable.
Pino →The log can’t be edited
Activity logs are append-only at the database level: edits and deletes are rejected, even from inside.
Money is never overwritten
A received payment can’t be changed or deleted. It can only be voided with a reason, and the original stays visible.
Roles decide who changes what
Sensitive actions such as approvals, refunds and price changes are limited to the people you choose.
Deleted doesn’t mean gone
Removed records are kept in the history, so reports always reconcile and nothing disappears.
Nothing half-saved
Money and stock movements are saved completely or not at all, in the database banks and governments trust.
PostgreSQL →
- Recorded payment RCPT-0412Mona · Accountant25,000 EGP · Bank transfer
- Edited order ORD-1187Karim · SalesQuantity 40 → 45
- Tried to edit payment RCPT-0412Karim · SalesBlocked · not allowed for this role
- Voided payment RCPT-0398Mona · AccountantReason: recorded twice · original kept
Append-only: entries can’t be edited or deleted.
SIMPLE TO USE.
PROFESSIONAL TO SHOW.
Powerful doesn’t have to mean complicated. Your team sees what they need, managers get clear numbers, and clients get documents that look the part.
Dashboards at a glance
Today’s sales, orders, stock and cash on one screen.
Professional reports
Financial and operational reports you can export and share.
An AI assistant inside
Ask what is happening, get a summary, or let it do the task for you.
On any device
The same system on desktop, tablet and phone.
Training & handover
We train your team on their own screens with their own data.
Ongoing support
We stay with you after launch: fixes, updates and new features.
FROM FIRST MEETING
TO LIVE SYSTEM.
- 01
Discover
We learn how your company works today: people, documents, approvals and pain points.
- 02
Design
We map the system around that workflow and agree on scope, timeline and price.
- 03
Build & test
We build in stages you can see, run automated tests before every release, and test every page against the OWASP Top 10.
- 04
Launch & train
We move your data, go live and train your team.
- 05
Support & grow
We keep it running and add what your business needs next.
SYSTEMS RUNNING
IN REAL BUSINESSES.
- PhysioTechCLINIC
- AlHasswaLAW FIRM
- Dar El AhramPUBLISHING
- Coffee FactoryERP
- Egypt Agri-IntelAGRICULTURE
- Egypt Economic RiseBUSINESS
Why custom software instead of a ready-made system?
Ready-made systems make your team work their way. A custom system is built around how your company already works, includes only what you need, and can connect to the tools you already use. You also control how it changes as you grow.
Can anyone change or delete old financial records?
No. Financial records are append-only. A received payment can’t be edited or deleted; it can only be voided with a written reason, and both the original and the void stay in the history. Every action is recorded in an activity log that can’t be edited.
How do you keep our data safe?
All traffic is encrypted over HTTPS, passwords are hashed with a unique salt, sign-in is rate-limited and accounts lock after repeated failures, sessions live in HttpOnly cookies and rotate, every request is checked against the user’s role, and every input is validated. Before launch, we test the system against the OWASP Top 10.
Can the system connect to our online store, payment gateway or e-invoicing?
Yes. We connect it to your online store, shipping companies and payments through Paymob, Fawry, Stripe or PayPal, and build to the Egyptian Tax Authority e-invoicing requirements where they apply. Everything speaks a documented REST API, so a mobile app or branch POS can be added later without rebuilding.
What happens when an employee leaves?
You disable their account in one step. They lose access immediately, and everything they did stays in the activity log.
Who owns the system?
You do. Every change is recorded in Git and the whole codebase is backed up on GitHub, away from the server, and owned by you, not held by us.
Do you support the system after launch?
Yes. We train your team, stay available for support, and keep improving the system with updates and new features as your business grows.
YOUR VISION.
OUR TECHNOLOGY.
Tell us what your business needs. We'll build the system around it.
START A CONVERSATION →or email us at info@nilexdigitalsystems.com