Magento, from server to module.
We host Magento on our own hardware, keep the shop up to date, make it faster and build the modules and integrations it needs.
One party for the whole stack.
With a Magento shop, the host, the agency and the module vendor often point at each other when the checkout is slow or an update goes wrong. With us it sits with the same two people: the server, the Magento installation, the modules and the integrations.
Ask us why a category page loads slowly, and we follow the whole path. From the page cache through PHP and the modules to the query in the database. Nobody has to pass a ticket on to another party.
What we do for your Magento shop
-
Magento hosting
Magento on our own hardware, with Varnish, OpenSearch, Valkey and RabbitMQ set up and kept up to date.
-
Support and maintenance
Security patches, updates, monitoring and backups. You email us, we find out what is wrong.
-
Setup
Setting up a new shop or reorganising an existing one: stores, VAT, payments, shipping, B2B.
-
Speed and optimisation
We measure where the time goes, from server to browser, fix it and show you what it changed.
-
Custom modules
Modules that do what no existing module does well, built so the next upgrade is not a project.
-
Integrations
Magento connected to your ERP, accounting, stock, shipping, marketplaces or a second shop.
Support and maintenance.
A Magento shop that is not kept up to date gets a little more vulnerable and a little harder to update every quarter. We keep it up to date, for a fixed monthly price.
- Security patches
- Adobe releases security updates for Magento regularly. We put them on staging first, test search, basket and checkout, and then put them live.
- Updates
- Magento, PHP, the modules and the theme. We keep track of what is getting outdated, so a major upgrade never becomes a jump of three versions.
- Measuring what matters
- We measure whether the homepage, a category, a product and the checkout can be reached, and whether the cron jobs and indexers run. Otherwise you only notice a stuck cron when the stock is wrong.
- Backups
- Database and media to separate storage, kept for a period we agree. We test restoring, because a backup nobody has ever restored is a gamble.
- Picking up errors
- Errors in the logs, payments that hang, emails that never arrive. Your contact person emails us and we find out where it sits, even if it is in someone else’s module.
- Availability
- We are there Monday to Friday, 09:00 to 17:00. If your shop runs at full speed outside office hours too, you can agree on-call as a paid extra.
Setup.
Magento can do a lot, and that is exactly why setup often goes wrong. A store view or VAT rule set up wrongly only shows when a customer calls or the accountant starts asking questions.
Stores and languages
- Websites, stores and store views for each country or brand
- Translations, currencies and the right URL per language
- Canonical and hreflang settings, so Google keeps the languages apart
Selling and checkout
- VAT rules per country and customer group
- Payment and shipping methods, with the right conditions
- Transactional emails in your own house style
Catalogue
- Attribute sets, filters and categories that match your range
- Configurable products and bundles
- Redirects for a new structure, so old links keep working
Selling to businesses
- Customer groups with their own prices and terms
- Roles and permissions in the admin
- Ordering on account, with the checks that go with it
Our own warehouse module.
Order picking with a handheld scanner on a tablet, directly in Magento. Every product is scanned, and an order is only done when everything adds up.
It is the first module we are building ourselves, for a problem we keep running into at online shops. What it does and how it works is on the custom modules page.
About the warehouse moduleSound familiar
- The shop is slow and the host says it is Magento’s fault
- An update has been put off for months, because nobody knows what will break
- The agency that built the shop no longer replies
- Orders are retyped into the ERP by hand
- A third-party module breaks with every upgrade
Look first, change later.
You do not tinker with a Magento shop that brings in revenue. Every job, large or small, goes in the same order.
-
Review
We go through the server, the Magento installation, the modules, the logs and the speed.
-
Plan
You get on paper what we see, what comes first and what it costs.
-
Staging
Everything happens on a copy of your shop first. You test along before anything goes live.
-
Live
At an agreed, quiet moment. If it does not work as intended, we roll it back.
-
Management
After that we keep the shop up to date: updates, patches, backups and measuring the important pages.
Who it is for
For shops on Magento 2, Open Source or Adobe Commerce, looking for a party that knows the whole shop instead of one layer of it. For shops that have lost their agency, or have a host that looks no further than the server.
And for web agencies that build Magento but would rather outsource the hosting and server management. We host, you keep the client.
Questions
What does Magento hosting and management cost at Jevana?
That depends on your shop, so you get a proposal up front with a fixed monthly price. What counts: the number of products and store views, the traffic, the modules and how much maintenance is needed. We price development work such as a module or integration separately: a fixed price up front, or an hourly basis if that fits better. A first introduction costs nothing.
Can you take over our Magento shop from another agency?
Yes. We start with a review: how the shop is put together, which modules it has, what has been changed in the code and whether updates are overdue. Then we move the hosting, or leave it where it is if that fits better. You do not have to start over, not even if nobody remembers how the shop was built.
Is Magento Open Source enough, or do we need Adobe Commerce?
For most small and medium-sized shops, Magento Open Source is enough. Adobe Commerce is the paid version with extra features such as more extensive B2B options and scheduled content changes, and a licence you buy from Adobe. We look with you at what you actually use. A module for that one feature is often cheaper than switching.
What do you do when Adobe releases a security update?
We put the update on your shop’s staging environment first and test the important steps: search, adding a product to the basket, checkout. If that works, the update goes live at an agreed moment. If a vulnerability is serious and already being exploited, we discuss a faster route with you.
Our shop still runs on Magento 1. Can you help?
Yes. Magento 1 has had no official security updates from Adobe since June 2020, so moving on is sensible. An upgrade to Magento 2 is in practice a new shop: the theme and modules are rebuilt, and the data comes along. We first look honestly at whether Magento 2 fits, or whether another platform such as WooCommerce suits your size better.
Do you build new Magento shops too?
Yes. We set up Magento, choose a theme with you, build what is needed and connect the shop to your other systems. We do say so when Magento is too heavy for what you sell. For a smaller range, WooCommerce is often cheaper to run, and then that is what we advise.
Do you work for web agencies?
Yes. An agency can move the hosting and server management of its Magento shops to us and keep the client contact and development itself. We set up a staging environment per shop and access for the developers. The agency emails us when something breaks; we fix it.
Tell us what you run.
An introduction costs nothing. You talk straight away to one of the two people who will actually do the work.
or email [email protected]