Cloud is a tool, not a destination. Some of your systems should stay where they are.
Microsoft 365, Azure, private and hybrid cloud: migrated with a plan, secured properly and costed honestly, including the parts that are cheaper to keep on your own hardware.
Engineering offices in Egypt, delivering on site across Egypt and Saudi Arabia, and supporting clients remotely across the Gulf, Africa, Europe and the United States.
Most people call. It is faster, and you speak to an engineer, not a form.
What a free cloud review looks at
Where cloud projects disappoint
We are often called in after a migration rather than before one. The same four things come up, and none of them are the cloud platform’s fault.
Lift and shift, and the bill triples
Servers moved as-is, sized as they were on hardware bought five years ago, running 24/7 in a model that charges by the hour. The invoice arrives and nobody can explain it.
The internet link was never sized for it
Everything now depends on one connection that was fine when it only carried email. There is no second line, and a link outage becomes a total outage.
Security assumed, not configured
The tenant is created with defaults: no multi-factor, global admin handed out freely, no conditional access, sharing wide open. It works, right up until it does not.
Nobody owns it afterwards
The migration partner leaves, licences renew on autopilot, unused resources keep billing and no one reviews any of it. Cloud rewards attention and punishes neglect.
How we run a cloud project
Assessment first, and a real answer about what should not move. We would rather size the job honestly than win it and disappoint you six months later.
Assessment and the honest business case
The phase that decides whether the project is worth doing, and which parts of it are not.
- Inventory of what you run, how it is used and what it depends on
- Workload-by-workload: cloud, on premises or hybrid
- Real cost model: compute, storage, egress, licensing, backup
- Compliance and data-residency constraints identified early
- Bandwidth and resilience requirements for the sites involved
- A recommendation that includes what to leave where it is
If the honest answer is that a system should stay on your hardware, we will say so.
Microsoft 365 and identity
For most businesses this is the cloud project, and identity is the part that decides its security.
- Migration of mail, files and collaboration with a tested cutover
- Entra ID, single sign-on and multi-factor enforced properly
- Conditional access and privileged-account separation
- Sharing, retention and data-loss policies configured, not defaulted
- Licence mix reviewed. Most estates are paying for unused tiers
- Third-party backup for 365 data, which Microsoft does not provide
See Email Services for mail-specific work.
Azure, private and hybrid infrastructure
Cloud, your own hardware, or both. Connected so they behave like one estate.
- Landing zone, network design, naming and tagging done once, properly
- Site-to-site VPN or dedicated connectivity between office and cloud
- Right-sizing, reserved capacity and shutdown schedules that hold
- Virtualisation on your own hardware where that is cheaper
- High availability designed to the RTO you actually agreed
- Infrastructure documented, so the next engineer is not guessing
Underlying hardware and data-centre work sits in Infrastructure Solutions.
Migration, with a rollback
Cutovers are rehearsed, scheduled around the business, and reversible until they are proven.
- Pilot group first, then waves. Never the whole company at once
- A written cutover plan with timings and a named decision-maker
- Rollback defined before the window opens, not improvised during it
- Data validated after each wave rather than assumed
- Hypercare period with engineers available while people adjust
- User guidance in plain language, in English or Arabic
We schedule cutovers for when your business is quiet, including weekends.
Running it afterwards
Cloud is an operating model, not a delivery. The savings come from the review that happens monthly.
- Monthly cost review with unused and oversized resources flagged
- Licence true-up so you stop paying for people who left
- Patching, backup and monitoring of cloud workloads
- Security posture reviewed as Microsoft changes the defaults
- A named engineer who knows your environment
- Reporting you can put in front of a board
This can sit inside Managed IT as one agreement.
Cloud and hybrid work we have delivered
Real Stark projects. Client identifiers are withheld under confidentiality. Sector and scope only.
Microsoft 365 migration
Mail, files and collaboration moved in waves with a tested rollback, and identity hardened with multi-factor and conditional access as part of the same project.
Private cloud on owned hardware
Where data residency and control rule out public cloud, we build and operate the platform on the client’s own infrastructure.
Hybrid platform, monitored around the clock
Public-facing services in cloud, regulated data kept where it has to stay, connected and monitored as a single estate.
Hybrid, deliberately
Email and collaboration in cloud, file and line-of-business servers kept on site where that was measurably cheaper and faster.
References can be provided directly, on request, with the client’s agreement.
Three things we will tell you not to do
The questions we get asked most
Is cloud cheaper than what we have now?
Sometimes, and we will tell you when it is not. It is usually cheaper for variable or seasonal workloads, for anything you would otherwise buy hardware for, and for email and collaboration. It is often more expensive for steady, predictable, always-on servers you already own.
Can our data stay inside Egypt?
Yes. Where residency or contractual terms require it, we build private cloud on your own hardware or in a facility you control, and connect it to public cloud only for the parts that are allowed to be there. That is a normal design for us, not an exception.
How long does a Microsoft 365 migration take?
It depends on mailbox count, data volume and how much cleanup the current estate needs, which is why we scope it at the assessment rather than quoting a number here. The pattern is consistent though: pilot group, then waves, with a rollback available until each wave is proven.
What happens if the internet goes down?
That risk is real and it is one of the first things we size. Depending on what you move, that means a second connection from a different provider, automatic failover, and keeping the systems that must survive a link outage on site. See Network Solutions.
Do you support us after the migration, or is that the end?
We would rather stay. Cloud environments drift: licences renew, resources sit unused, Microsoft changes the defaults, and the value shows up in the monthly review. That can be a managed agreement or ad-hoc support; we do not insist on a retainer by default.
Tell us what you are thinking of moving.
Ten minutes on the phone is usually enough to tell you what should move, what should not, and roughly what the bill will look like.
Sunday to Thursday, 9am to 6pm · Egypt, and remote worldwide
Our other IT services
Every service below is delivered by the same team, under the same agreement.