Information security for software delivery

ISO/IEC 27001
ISO/IEC 27001 certified
The operational bill
What owning a Magento store commits you to every month
None of these is a defect; each is the standing price of the flexibility. A merchant should read this list before the licence conversation, because the platform is only ever as good as the operation behind it.
| Variable | Effect on price | Why |
|---|---|---|
| Infrastructure you answer for | Hosting, scaling and uptime move from a subscription to a responsibility | A Magento store runs on servers someone provisions, monitors and scales for the sale season. Whether that someone is your team or a managed provider, it is a contract and a budget line a hosted platform never shows you. |
| Patching on the platform’s calendar | Security releases arrive on their schedule, not yours | Security patches and version upgrades are recurring engineering work: applied in a test environment, checked against your customisations and third-party extensions, then released. A store that skips this quietly accumulates the risk the platform already fixed. |
| Performance as a discipline | Speed is engineered and defended, never installed | Magento rewards proper caching, indexing and front-end restraint, and punishes their absence on every page view. No extension makes a badly engineered store fast; the section below treats this as the standing discipline it is. |
| Specialist depth, retained | The store depends on skills the general market is short of | Magento expertise is deeper and scarcer than general web development, and a store customised by whoever was available becomes expensive for whoever comes next. Continuity of the people who know your codebase is part of the total cost. |
Ask any supplier quoting this
- Which of our catalogue requirements can you show Magento expressing that a hosted platform will not — specifically, not in principle?
- Who applies next quarter’s security patches, in what environment are they proven, and what does that cost per year?
The case for it
The catalogues that only an owned commerce platform will express
The honest case for Magento is specific, and it is mostly a B2B case. Company accounts with buyers, approvers and spending limits; price lists negotiated per customer and per volume; quotes that turn into orders; catalogues where a product is a configuration space rather than a SKU — thousands of variants, regional availability, units of measure that differ by customer. Hosted platforms express fragments of this through apps; Magento expresses it in the data model, which is where it has to live if the ERP is to agree with the storefront.
Read that paragraph against your own catalogue before reading any further. If your products are straightforward retail SKUs with standard pricing, the flexibility above is capacity you would pay for monthly and never use, and a hosted platform serves you better — a conclusion we give merchants even when it costs us the larger project. The total cost comparison with SaaS resists a single number, but its shape is consistent: the hosted platform charges more as you grow and less to exist; Magento charges to exist — infrastructure, patching, specialists — and that standing cost only converts into value when the catalogue is using the depth.
Performance engineering
The conditions under which a Magento store stays fast
Magento performance is not a plugin you install; it is a set of conditions you keep true. When a store is slow, one of these has usually stopped being true.
The cache serves most page views
Full-page caching treated as architecture: pages designed to be cacheable, private content isolated, and customisations reviewed for the cache they silently punch holes in.
What it protects: A catalogue page that does not recompute itself per visitor.
Indexes and scheduled jobs stay healthy
Indexing runs on schedule rather than on save, the job queue is monitored, and a stuck reindex is an alert — not a discovery made when prices stop updating.
What it protects: Search, pricing and stock that reflect reality without slowing it.
Search is carried by a search engine
Catalogue search and layered navigation run on the dedicated search service, tuned for Arabic and English queries, rather than leaning on the database.
What it protects: A search box that answers in Arabic as quickly as in English.
The front end carries a weight budget
Theme, media and extension scripts are held to a budget, because the platform’s back-end tuning is wasted if the storefront ships megabytes to a phone.
What it protects: The speed the servers earn actually reaching the buyer.
Our role
What we engineer on Magento and the operation we leave staffed
- 01
The data model before the theme
We design the catalogue, pricing and account structures first, because they are what you chose Magento for — a beautiful storefront on a wrong data model is a repaint of the wrong house.
- 02
Customisation that survives upgrades
Custom logic is built the way the platform intends — extensions and declared interfaces, never core edits — so next year’s upgrade is a scheduled task rather than an archaeology project.
- 03
The operating rhythm, installed
Patching calendar, monitoring, test environment and the performance conditions above are set up and handed to a named owner — yours or ours under a support arrangement — because a Magento store without an operator is an incident with a date it has not told you.
Whether the catalogue justifies the platform is a decision we help you make honestly, including against our own interest; once made, we build the store to use the depth you are paying for and leave the operation staffed to keep it.
Common questions
What buyers ask
Is Magento too much platform for a straightforward retail catalogue?+
Usually, yes. If your products are standard SKUs with list pricing and your buyers are consumers, the flexibility Magento charges for — in infrastructure, patching and specialist time — is capacity you will not use, and a hosted platform gets you selling sooner for less standing cost. The test is concrete: write down the three catalogue or pricing behaviours you need that a hosted platform refused to express. If the page is blank, that is your answer. If it lists negotiated B2B price lists, company account structures or configuration-heavy products, Magento starts earning its keep.
What does keeping a Magento store patched actually involve, month to month?+
A standing cycle, not an occasional favour. Security releases and quality patches arrive on the platform’s calendar; each is applied first in a test environment, checked against your customisations and third-party extensions — the usual source of surprises — and then promoted with a rollback ready. Between releases, the extensions themselves need the same scrutiny, because an abandoned extension is an unpatched door regardless of how current the core is. A merchant should budget this as recurring engineering with a named owner; the stores that get breached are rarely missing a patch nobody had heard of — they are missing an owner.
How should we compare Magento’s total cost against a SaaS platform if there is no single number?+
Compare the shapes, then your position on them. A hosted platform’s cost tracks your revenue: subscription tiers, transaction fees and app charges rise as you sell more, while existing costs almost nothing to maintain. Magento’s cost tracks your ambition: infrastructure, patching and specialist retention are owed whether you sold well this month or not, while growth adds relatively little. The comparison collapses to two questions — does your catalogue need what only the owned platform expresses, and can your organisation genuinely staff the standing operation. Two yeses and Magento is cheaper than the workaround economy it replaces; one no, and the SaaS platform wins regardless of any spreadsheet.
In this cluster
Talk through your store
A platform assessment that reads your catalogue and B2B model against what Magento alone expresses, and prices the operational commitment honestly before you make it.
Start the conversation