About
Network engineering · Cybersecurity Tier 3 · Philippines
MWX Systems builds the software Philippine businesses run on and engineers the networks underneath it. The company exists because those two jobs are usually sold by different vendors who then blame each other — and the business in the middle is the one that loses a day of trading.
History
Years of running production infrastructure taught the same lesson over and over: the outage is rarely where the vendor said it would be. An HR system goes down and the software provider blames the network. The network provider says the server is fine. The business waits while two companies argue.
Meanwhile the things that actually save you — a backup somebody has restored, a second internet line that fails over on its own, a network where the guest wifi genuinely cannot reach the accounting server — are the things nobody sells, because they are invisible when they work.
MWX Systems was built to deliver exactly those, with one team accountable for the application and the infrastructure it sits on.
How we work
These are not slogans. Each one comes from a specific incident that cost somebody a day, and each one changed how we work afterwards.
Scheduled backups pass their own checks right up until the day you need one. We restore on a schedule, from the actual archive, and treat a failed restore as an outage in itself — because that is when it is cheap to find out.
We name a client only when they have agreed to it, and we never publish topology, addressing or equipment inventory for anyone. A portfolio that tells an attacker where to start is worth less than the work it advertises.
Most networks do not need replacing, and most businesses do not need all eight systems on day one. We look first, then quote for what actually earns its cost — including telling you when the answer is "nothing yet".
Software fails for network reasons and networks get blamed for software problems. When the same team owns the application and the infrastructure beneath it, that argument never happens and the fix starts immediately.
Tech stack
Not a list of everything we have heard of — these are the tools currently carrying production workloads, chosen because they suit the job rather than because they are new.
Where a business needs a real desktop application on the floor, not a browser tab.
The backbone of the business platforms — HR, records, accounting and inventory.
For public sites and content-managed front ends that have to be fast on mobile data.
One codebase, both platforms — which is why mobile ships with the system instead of after it.
Chosen per workload, pooled and cached so the database is not the thing that falls over first.
Where the workloads live, with snapshots and a standby copy as standard rather than as an upsell.
Single sign-on, controlled access, and one place to disable an account when someone leaves.
The multi-site layer: failover, segmentation and encrypted links between branches.
How it gets deployed, published and kept reachable without exposing the origin.
Credentials
Formal certification in the platforms we actually deploy — so the design decisions on your network were learned somewhere other than your network.
Enterprise routing, switching and campus network design — the backbone standard most business networks are measured against.
Routing, firewalling, VPN and traffic management on RouterOS, the platform behind most of the multi-site work we run.
Vendor-neutral networking and systems fundamentals — the part that stays true no matter whose box is in the rack.
Hardening, segmentation, monitoring, incident handling and response — applied to every network we design rather than added afterwards.
What that adds up to
SOFTWARE
HRIS with a native mobile app, parking and access control, Philippine-compliant accounting, a 201 records vault, bot and system automation, and managed hosting — built for local operations, not translated into them.
INFRASTRUCTURE
Multi-site routing with failover, segmentation and secure remote access across distribution, logistics, property and hospitality — designed, documented, and still run by us.
Philippines · remote and on-site
There is no account manager in between. The first reply comes from whoever will be responsible for the build.